program selection system

Despite the advances in both developer and customer automated testing, there remains a great deal of anecdotal evidence and testing thought leadership that suggests degrees of manual testing is still required for software-intensive projects, especially at the traditional, higher test levels such as user acceptance testing. We have come to believe that this doesn’t mean agile techniques do not stay in the picture for the duration of manual testing.

Summary

There are two questions worth asking oneself over and over when creating automated acceptance tests.

• What is the purpose of this test?
• Does the test express this purpose as clearly as possible?

This clinic uses exercises and examples to reinforce the good habit of writing tests with a clear purpose. Our focus is on favoring “declarative-style” tests over “procedural-style” tests. (See Bill Wake’s explanation of the difference at http://xp123.com/xplor/xp0503/index.shtml)

FitNesse out of the box does not seem to work for teams! In this demo I’ll show how to set up FitNesse so that development teams can do the following:

• Organize their Stories, Acceptance Criteria and Acceptance Test better
• Create different levels of test suites to give feedback at different levels
• Version control the FitNesse wiki with their source code
• Inline editing of their FitNesse pages, with out having to worry about Wiki syntax
• Integrate FitNesse with their builds, so that they can run their acceptance tests as part of their Continuous Integration loops