Test Designs are a step-by-step description of how to test a specific requirement or set of requirements. Test Designs include

•	values that will be input into the application,
•	actions that need to be taken, such as keys or buttons to press, or links to click on,
•	the navigational flow through the application,
•	expected results.

In our experience, organizations generally approach test designs in two ways: They either
a) don't do them because it is too time consuming, or
b) enter them into Microsoft Word.

We have seen countless testing departments with shelves and shelves occupied by large binders containing test designs. These test designs often collect dust. Sometimes they are lost as testers borrow them to work on them further.

Another universal problem is that maintaining test designs can be even more difficult then creating them in the first place, especially if there are significant changes to often used screens or components in the application.

Scenario Tester solves these problems. It provides an interface which mimics the application under test. Testers enter their inputs, navigational flow and expected results right into Scenario Tester.

Entering test designs into Scenario Tester

Scenario Tester application has functionality to assist users in creating test designs:

•	copying previous scenarios and adjusting data speeds up the creation of test designs,
•	lookup lists allow testers to select correct values,
•	note fields at the scenario level and field level allow testers to annotate the test design,
•	screen shots can be stored for every step of the process,
•	changes in the application often involve small changes in Scenario Tester and all affected scenarios are automatically updated.

In most automated testing efforts, the writing of test designs is a separate activity from test automation; one group creates the test designs and another group does the automation. There is often a great deal of energy and effort expended going back and forth between the testers and the automation specialist(s). The test data needs to be re-created by the automation experts either in files, Microsoft Excel or other tools.

With Scenario Tester, the integration between test designs and automation is seamless. Once test designs are entered, the test data is ready for automation. If the test scripts are already developed, then the test designs can be executed immediately upon entry.

Test designs can be created even before the application is ready. They can then executed as soon as the automation scripts are ready. Many IT managers have told us that this is their dream and now it is a reality.

Finally, even if automation is not in the short term plan of the QA department, Scenario Tester is a great manager for Test Designs. If and when automation is considered, a large part of the work is already done.