Fifty Quick Ideas to Improve Your Tests by Gojko Adzic David Evans and Tom Roden

Author:Gojko Adzic, David Evans and Tom Roden [Gojko Adzic, David Evans and Tom Roden]
Language: eng
Format: epub
Publisher: leanpub.com
Published: 2014-08-14T00:00:00+00:00

How to make it work

When teams capture details written on a whiteboard or similar media in a specification workshop, they typically have the key examples of cases and scenarios that were discussed to tease out the complexity of the business rules. The next step is to add enough context to these examples so that they will make sense to people who were not involved in the discussions that created them. In User Story Mapping Jeff Patton has described the artifacts we create in collaborative workshops as being like vacation photos, because they mean more to the people who were there when the photos were taken than to those who weren’t. For those who took part in the specification workshop, the key examples they wrote down and still have are like snapshots that trigger memories of all the other things that happened at the time – the discussions, questions and answers, revisions and corrections that the group went through together in the process of arriving at those examples. It is important to remember that we are trying to create items of long-term value. We need to build up the picture in a logical way, so that everyone can get the most value out of the specifications.

You will get the best results by thinking ahead to the longer term role of coherent documentation, rather than thinking only in terms of specifications or tests.

Here are some tips for doing this:

Always provide some introductory text for each set of examples

Show simple, illustrative examples before more complex ones

Group small sets of related or complementary examples together

Highlight your key examples and keep them prominent in your specifications, close to the descriptions of the business rules they illustrate

If you also have a more comprehensive set of tests that cover additional cases, keep these in separate tables or scenarios, or consider putting them in a separate feature file or page, and tag them accordingly.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.