Chapter 3. Hints and Tips

Table of Contents

3.1. Separate In-Progress Stories from the Backlog
3.2. Use a Story Page to Collect A Set of Scenario Tests
3.3. Organize Completed Stories by Component
3.4. Structure your test using Given/When/Then
3.5. Using the RunViewer fixture
3.6. Factor out common "Given"s
3.7. Use a Declarative Style for Page Names
3.8. Run against a real database
3.9. Set up Continuous Integration

This chapter contains a collection of hints, tips and suggestions for writing your own tests.

For further guidance, check out Gojko Adzic's book, Bridging the Communication Gap.

3.1. Separate In-Progress Stories from the Backlog

If you are using an agile methodology then you will be implementing a number of stories per iteration; the remainder will be in a backlog. When you select a story for implementation, create a new page for it in a "CurrentIteration" suite. The objective for the team is therefore to get the entire CurrentIteration suite green.

Other stories that you may have identified but not selected for the iteration can remain in a Backlog suite.