Automated Testing is the single best way to handle time and resource problems in testing.

If you are not using automated testing, then you are either

•	Using too many resources to test,
•	Taking too long to test,
•	Limiting the scope of testing, or
•	Taking too many risks.

Automated testing is a necessity.

Unfortunately, studies have show that organizations cannot make automated testing work for them. Over 75% of automated testing efforts fail in the first year. Even some of our earliest efforts at automated testing failed.

We were determined to figure out why automated testing efforts fail, and fix the problem.

We believe that we have found the solution to failed automated testing efforts.

Our record speaks for itself. Automated testing efforts using Scenario Tester have longevity.

Type of institution		How long scripts used?
Financial institution		2 years
Insurance company		2 years
Commercial software developer		1 year

Scenario Tester and the Scenario Tester approach is the solution to automated testing problems.

The two problems that consistently accompany automated testing are:

•	Good testers want to tests and not become coders of automated scripts. Testers generally do not possess the skills to develop and maintain the code required for automating scripts
•	Scripts die if not written properly

We have solved both of these problems in the following ways:

•

Scenario TesterTM software is used by testers to enter their test designs. They only need to enter their inputs and expected results. Scenario Tester is simple, easy to use and powerful. Testers are up to speed in minutes, often with absolutely no training. It is that intuitive! There is no need that they code complex data entry, navigation or validation logic in a programmatic test script.

•

Testers enter tests scenarios. A developer will create background scripts, which will execute the scenarios. We demand coding standards and a logical structure to the scripts. The scripts are therefore, easy to build and extremely easy to maintain. The scripts are robust, modular and easy to understand. In most cases, only one developer is required on a part-time basis to maintain the execution script.

Because of the separation of test data from the creation of scripts, you can have multiple testers, business analysts and users creating test scenarios and only one developer creating the scripts.