Scenario Tester is the tester’s tool. The testers control the automated testing process by entering test data, executing the tests and looking at the results.

To make this process work, someone still has to write scripts. These scripts are invisible to the testers but are an integral part of Scenario Tester.

To write the scripts you will need a person who can write code.

The process

In summary, the overall process is as follows:

•	A developer develops the background scripts that input data into screens and test screens for expected results. These are what we call input and output scripts.
•	A master script reads the data created by Scenario Tester and calls the appropriate input and output scripts.
•	These scripts are created using a specific standard format, making them easy to write and even easier to maintain.

The scripts are built generically. They follow a fixed set of standards, which makes them simple, logical and reusable. These scripts are easy to write and easy to maintain.

As part of our consulting services, we come with an assortment of pre-built code, including functions, DLL's and applications.

We also have:

•	templates and applications which automatically generate necessary code,
•	Screen scrapers which pull the necessary information right from the application under test,

This dramatically speeds up the time it takes to write and debug the scripts, assuring easy to maintain scripts, which are based on a coherent set of standards.