background image
<< Test Plans - Using a template of the GUI hierarchy as an outline | Test Plans - How to link using the Testplan Detail dialog >>
Test Plans - Linking the testplan to scripts and testcases
<< Test Plans - Using a template of the GUI hierarchy as an outline | Test Plans - How to link using the Testplan Detail dialog >>
User's Guide
61
2 C
REATING
T
ESTPLANS
Linking the testplan to scripts and testcases
For example, here is the template QA Organizer inserts for the Find
dialog of the Text Editor application:
Tests for DialogBox Find
Tests for StaticText FindWhatText
(Insert tests here)
Tests for TextField FindWhat
(Insert tests here)
Tests for CheckBox CaseSensitive
(Insert tests here)
Tests for StaticText DirectionText
(Insert tests here)
Tests for PushButton FindNext
(Insert tests here)
Tests for PushButton Cancel
(Insert tests here)
Tests for RadioList Direction
(Insert tests here)
Linking the testplan to scripts and testcases
Once you have a descriptive outline of the test requirements, you can
associate the outline with the 4Test scripts and testcases that implement the
requirements. You create this association by inserting script and testcase
statements in the appropriate locations in the outline.
Where to insert script
and testcase
statements
You can insert a script and testcase statement for each test description,
although placing a statement at the group level when possible eliminates
redundancy in the testplan.
For example, since it is usually good practice to place all the testcases for a
given application feature into a single script file, you can reduce the
redundancy in the testplan by specifying the script statement at the group
level that describes that feature.
The following testplan illustrates this, specifying the script find.t once for the
entire group of tests of the Find dialog (the script statement is highlighted for
emphasis):