background image
<< Large Testplans - Subplans inherit Information | Large Testplans - Releasing a lock >>
Large Testplans - Editing a master plan in a multi-user environment
<< Large Testplans - Subplans inherit Information | Large Testplans - Releasing a lock >>
260
User's Guide
12 W
ORKING
W
ITH
L
ARGE
T
ESTPLANS
Editing a master plan in a multi-user environment
Creating the subplan
You create a subplan in the same way you create any testplan: by opening a
new testplan file and entering the group descriptions, test descriptions, and
QA Organizer statements that comprise the subplan, either manually or using
the Testplan Detail dialog.
Adding the include
statement to the
master plan
To connect the master plan to a subplan file, you enter an include statement
in the master plan at the point where the subplan logically fits. The include
statement cannot be entered through the Testplan Detail dialog, so it must be
entered manually. The include statement uses this syntax:
include:
myinclude.pln
where myinclude is the name of the testplan file that contains the subplan.
If you enter the include statement correctly, it appears in red, the default
color used for QA Organizer statements. Otherwise, the statement appears in
blue or black, indicating you've made a syntax error (the compiler is
interpreting the line as a description, not a statement).
Sharing a testplan
initialization file
All QA engineers working on a large testplan that is broken up into a master
plan and subplans must use the same testplan initialization file. To do this, all
engineers should specify the same file name in the Data File for Attributes
and Queries field in the General Options dialog (invoked by selecting
Options/General).
Editing a master plan in a multi-user environment
Opening the subplan
You should open the subplan from within the master plan. To do this, you can
either double-click in the margin to the left of the include statement or
highlight the include statement and select Include/Open. (Compiling a script
also automatically opens all subplans.)
Note If a subplan does not inherit anything (that is, statements,
attributes, symbols, or data) from the master plan, you can open the
subplan directly from the File Open dialog.
Acquiring a lock
When first opened, a master plan and its related subplans are read-only. This
allows many users to open, read, run, and generate reports on the plan.
When you need to actually edit the master plan or a subplan, you must first
acquire a lock, which prevents others from making changes that conflict with
your changes.