Test Framework

Test framework outlines:

- overall structure of automated test environment
- defines common function
- standard tests
- provides templates for test structure.
- spells ground rules for how tests are named, documented and managed.
- leading to maintainable and transferable test library.

By adopting common framework, you can enjoy the efficiency that comes from sharing common functions, and effectiveness that standard tests and templates provide.

Common functions:

These functions are usually be described as subroutines, which means they can be called from any point and return to next step after the one which called them.

 

SETUP function:

- Prepares test environment for execution.

- Verifies:

- Proper configuration is present

- Correct application version is installed

- All necessary files are available

- All temporary or work files are deleted.

- It performs setup of test environment.

- Designed to start and end at known point such as command prompt.

SIGNON:

- loads the application and assures it is available for execution

- It may provide for prompting of username and password to access application from point at which SETUP routine ends.

- SIGNON should be executed after SETUP at beginning of each test execution cycle.

DRIVER:

- DRIVER function is one which calls series of tests together as suite or cycle.

MONITOR:

- called after each transaction is submitted, or at regular intervals to check status of the system.

RECOVER:

- most often called by the LOGERROR function.

- RECOVER routine may also call the SIGNON script to reload the application.

SIGNOFF:

- Terminate the application and returns the system to known input, such as program manager or command prompt.

- Used at the end of the last test suite, before other shared routines such as CLEANUP is executed.

LOGTEST:

- called at the end of each test case or script in order to log results for component just executed.

LOGERROR:

- called by any test that fails.

- Secondary purpose may be to call RECOVER function, so that context can be restored for next test.

CLEANUP:

- Cleans up the test environment.

- Properly designed CLEANUP routine will keep your test environment organized and efficient.

Standard Tests:

- common function is shared among tests.

- standard test is shared among test suites, cycles or even applications.

-                                                  

WALKTHRU:

- This test navigates through the application, assuring that each menu item, window and control is present and in the expected default state.

- This type of test could be executed by development group after the system build, before application is delivered for testing, or by production support group after the application has been promoted to production environment.

STANDARDS:

- It is the one which verifies the application design standards are met for given component.

- It verifies that previously agreed up on standard have been satisfied.

- It may be design criteria that every window have:

maximize and minimize button

vertical and horizontal scroll bars

both OK and CANCEL push button

- It might also verify standard key behaviors such as using an ESC key to cancel.

TESTHELP:

- Is the one which might be useful on every screen or window.

- Assures that help function is available at all points in the application.