background image
<< Large Testplans - expanded testplan | Large Testplans - Dividing a testplan into a master plan and subplans >>
Large Testplans - Measuring testplan completion
<< Large Testplans - expanded testplan | Large Testplans - Dividing a testplan into a master plan and subplans >>
256
User's Guide
12 W
ORKING
W
ITH
L
ARGE
T
ESTPLANS
Measuring testplan completion
Measuring testplan completion
Definition of
completion
To measure your QA department's progress in implementing a large testplan,
you can generate a Completion report. The Completion report considers a test
complete if the test description is linked to a testcase, with two exceptions:
If the testcase statement invokes a data-driven testcase and a symbol
being passed to the data-driven testcase is assigned the value ?
(undefined), the test will be considered incomplete.
If the testcase is manual and marked as Incomplete in the Update Manual
Tests dialog (available under Windows only), the test will be considered
incomplete. (A manual testcase is indicated with the
testcase:manual
syntax; for more information, see "Documenting manual tests in the
testplan" on page 67.)
How to generate a
testplan Completion
report
Procedure To generate a testplan Completion report:
1
Open the testplan you want to report on.
2
Select Testplan/Completion Report:
The Testplan Completion Report dialog appears:
3
In the Report Scope group box, indicate whether the report is for the
entire plan or only for those tests that are marked
4
To subtotal the report by a given attribute, select an attribute from the
Subtotal by Attribute field.
For example, suppose you have an attribute named Developer and have
specified the values that Developer can take. If each test has been
assigned a Developer value, you can generate a Completion report that
shows how many of the tests for each developer are complete.