Fabio Zadrozny <[EMAIL PROTECTED]> writes:
> I think that the best approach I saw to this was in the Eclipse java
> ide... You can basically go on the declaration of
>
> self.obj = player.Player('Fred the Adventurer')
>
> press Ctrl+1 and it adds a suggestion to create the class Player.
>
> Then g
Peter Maas <[EMAIL PROTECTED]> writes:
> I think this is too difficult, because there are many ways to write
> code (even skeletons) for a use case. An easier approach would
> be to write the skeleton manually, embed the test cases in the doc
> strings and generate the test code from the doc strin
I think that the best approach I saw to this was in the Eclipse java
ide... You can basically go on the declaration of
self.obj = player.Player('Fred the Adventurer')
press Ctrl+1 and it adds a suggestion to create the class Player.
Then go to
assert self.obj.name == 'Fred the Adventurer'
press C
Edvard Majakari schrieb:
Greetings, fellow Pythonistas!
I'm about to create three modules. As an avid TDD fan I'd like to create
typical 'use-cases' for each of these modules. One of them is rather large,
and I wondered if it would be easy enough to create a code skeleton out of
unit test module.
I
Greetings, fellow Pythonistas!
I'm about to create three modules. As an avid TDD fan I'd like to create
typical 'use-cases' for each of these modules. One of them is rather large,
and I wondered if it would be easy enough to create a code skeleton out of
unit test module.
Consider the following,
