background image
<< Overview | Overview - Getting started >>
Overview - The automated testing process
<< Overview | Overview - Getting started >>
18
User's Guide
1 O
VERVIEW
The automated testing process
2
Recording a test frame
3
Creating testcases
4
Running testcases and interpreting their results
Creating a testplan
If you are using QA Organizer, you begin the automated testing process by
creating a testplan. A basic testplan is structured as a hierarchical outline and
contains:
·
Descriptions of individual tests and groups of tests. You can use as many
levels of description as you want.
·
Statements that link the test descriptions in the plan to the 4Test routines,
called testcases, that accomplish the actual work of testing.
The following figure shows a sample testplan for a search feature. The
testplan uses two levels of description: the top level indicates that all the tests
are for the Find dialog, and the next level describes eight individual tests.
Recording a test frame
Next, you record a test frame, which contains descriptions, called window
declarations
, of each of the GUI objects in your application. A window
declaration specifies a logical, cross-platform name for a GUI object, called
the identifier, and maps the identifier to the object's actual name, called the
tag. In addition, the declaration indicates the type of the object, called its
class.
Creating testcases
The 4Test commands in a testcase collectively perform three distinct actions:
1
Drive the application to the state to be tested.
2
Verify the state (this is the heart of the testcase).
3
Return the application to its original state.
Group description
Test descriptions
QA Organizer
statements