Test models are used to automatically create a library of test procedures that are then sub-divided into test cases. At execution time, the test procedures stored in the library are automatically executed based on test case order. All logging is automatically saved to a SANS. All reports are automatically

sent to the test manager and the development team, while summary test reports are sent to upper management. Most tests use either the GUI or the feature-rich API provided by the SUT, but some involve use of ad hoc database queries.

Creation of test cases and test conditions is semi-automated, based on a manually created test design.
Test procedures and test data are automatically created. The test library is automatically created, but subject to manual review and revision. Tests are automatically executed with the latest successful build at 8 p.m. each day. All logging is automatically saved to a SANS for examination and use by both developers and managers. All tests use either the GUI or the feature-rich API provided by the SUT.

Creation of test cases is fully automated, based on a set of specially developed models of the SUT and the test library is then updated automatically. Tests are automatically executed with the latest successful build at 8 p.m. each day. All logging is automatically saved to a SANS. All reports are automatically sent to the test manager and the development team, while summary test reports are sent to upper management.

Creation of test cases and test conditions is semi-automated, based on a manually created test design.
Test procedures and test data are automatically created. The test library is automatically created, but subject to manual review and revision. Tests are automatically executed with the latest successful build at 8 p.m. each day. All logging is automatically saved to a SANS. All reports are automatically sent to the test manager and the development team.