In the previous lesson, you logged in as the test architect
and began the approval process by adding Mary as an approver. This
action assigned to Mary a work item that is listed in the My Tasks viewlet of her dashboard. In this lesson, you
log in as the test manager to review the test plan.
- Log in as the test manager (Userid: mary, Password: mary) when prompted with the login dialog box. Mary's
dashboard opens.
- Notice that the work item to review or approve the test
plan is listed in Mary's My Tasks viewlet, located
under the Welcome viewlet.
- Go directly to the test plan by clicking Review
TestPlan: Classics Java Test Plan. The test plan opens
to the Formal Review section.
- Review the different sections of the test plan.
- You can add information to the test plan. Create a quality
objective:
- Click the Quality Objectives section.
- Add an objective by clicking the Manage Quality
Objectives (
) icon.
- Next, click the Add Row icon
(
).
- In Name, type Requirements
Coverage; in Description, type Must have 100% requirements coverage.
- In Condition, choose =, and in Target, type 100.
- Click Save.
- To add the new quality objective to the test plan, click
the Add Row icon (
), select the Requirements Coverage objective, and click OK.
- Save the test plan.
- Now that you added a new quality objective of 100% requirements
coverage, check to see the status of requirements coverage for the
Classics Java™ Test Plan:
- Point to Reports (
), and click All
Reports.
- To scroll to the next page, click Next at the top of the reports page.
- Under the Requirements reports, click Plan
Requirements Coverage by Test Case.
- In the Test Plan section of the report, select Classics Java Test Plan, and click Run.
The results show that one requirement is uncovered by a test
case:
Note: Because
this is a simple test plan with only two requirements, the results
seem insignificant. A test plan with several requirements will have
more informative data.
- You can run more detailed reports by clicking the green
section (Plan Requirements Coverage Detail report) or the pink section
(Plan Requirements Not Covered Detail report). Click the pink section,
and then click OK to open the report. A list
of the requirements that are not covered by test cases are displayed.
Note: Expand the Parameters section, and make sure
that Classics Java Test Plan is selected. If
you make any changes, click Run.
You can
see that the requirement not covered is the new one that the test
architect added, called New Customer Order Requirement.
- Return to the Classics Java Test Plan page, and click the Requirements section.
- Create a work item to instruct the test lead to cover the
new requirement with a test case:
- Click Create in the upper, right
corner of the Requirements section.
- In Summary, replace the default
text with Ensure that all requirements are covered by test
cases.
- In Owned By, select Carmen, Test Lead.
- Click the Calendar icon (
) next to the Due field, and select a future date.
- Click OK.
- Because the test plan does not meet its quality objective,
you reject it:
- Click the Formal Review section.
- In the Status column, change the status to Rejected.
- Type the comment Not all requirements are
covered by test cases.
- In the Action field under the
test plan name, select Reject.
- Save the test plan.
- Log out as test manager.
The responses of each reviewer and approver are displayed
in the Formal Review section.
In the next lesson, you log in as the test lead and cover
the requirement with a test case.