Home
Groups
Lists
Search
|
Using English, write down some stories. Suggest some scenarios to fully illustrate the stories. Split the scenarios into sequences of contexts, events and outcomes. Reuse them to describe and illustrate the different behaviours of your system. Run the stories. If you need some code to make the system behave as it should, write down the behaviour of the code. Run the behaviours. If the code isn’t doing what it should, change it so that it behaves. It’s like testing, but without the tests.
2.0 able administrators also assignee author automatically behaviour bug build cheers class classes code components contact core could created currently d dan date description diff elizabeth etc extends feature fix generated get given hi incorrectly information issue jbehave jira jira.codehaus.org junit keogh key know like liz ll log m make mauro message method methods might much name need new north one original paths priority project public rather really reporter revision run scenario scenarios see sent something steps still story summary sure talevi test things think time type updated url use using ve visit void want way well work would wrote
|
|||||||||||||||||||||||||||||||||||||||||||
