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 a work item to Mary 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 approve/review the test plan
is now listed in Mary's My Tasks viewlet, located
under the Welcome viewlet.
- To open the work item, from the My Tasks viewlet,
click Approve/Review Classics Java Test Plan.
The work item opens to the Approvals tab, which
shows the approval status of the work item. You can also see this
information in the Formal Review section of the test plan.
- Click the Overview tab to see the
details of the work item. Mary is instructed to review the test plan:
- Return to Mary's dashboard by clicking Back
to Home at the upper, left corner of the page.
- To open the test plan, click Classics Java Test
Plan in the Artifact column of the My Tasks viewlet.
- 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.
- Click the Add Row icon (
).
- In the text field, replace the text, Quality
Objectives Description, with Must have 100%
requirements coverage.
- 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:
- From the left sidebar, point to the Reports icon
(
), 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 Parameters 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 conclusive 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 added by the test
architect, called New Customer Order Requirement.
Tip: You can view the requirement by clicking the ID number.
- Return to the Classics Java Test
Plan tab, 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 the Summary field, replace
the default text with Ensure that all requirements are
covered by test cases.
- In the Owned By field, select Carmen,
Test Lead.
- Click the Calendar icon (
) next to the Due field,
and select a future date.
- Click OK, and then click Save.
- 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.
- Save the test plan.
The responses of each reviewer and approver are displayed
in the Formal Review section.
In the next lesson, you will log in as the test lead and
cover the requirement with a test case.