Defect reports
Defect reports provide information about defects that are related to a test plan, the status of those defects, and trends in those defects over time.
Purpose
- What defects are associated with this test plan and what is the status of those defects?
- How are we doing on finding and fixing defects?
When you run a defect report, test plan is a required parameter. Within the application, however, defects do not link directly to a test plan. Therefore, it is important to understand which artifact relationships must be in place before a defect is included in these reports.
Defect reports are run for one or more test plans and include only defects that are associated (through a test case result) with a test case execution record (TCER) in which the test plan attribute is set to one of the selected test plans. You can associate a defect with a test case result while running a test (by adding a defect to the test step) or outside of a test run (by editing the test case result). The test case result is automatically linked to its corresponding TCER. For defect reports, the defect’s associated test case and test plan artifacts are irrelevant.
Consider the following example in which two defects are associated with various test artifacts. Identify which defects are included in a defects report run for each test plan.
- Running a defect report for Test Plan A returns no defects. Even though Defect 400 is linked (indirectly) to Test Plan A, Defect 400 is NOT included because TCER 91 specifies Test Plan M.
- Running a defect report for Test Plan B returns no defects. Even though Defect 401 is linked (indirectly) to Test Plan B, Defect 401 is NOT included because TCER 92 specifies Test Plan M.
- Running a defect report for Test Plan M returns both Defect 400 and Defect 401. Both Defect 400 and Defect 401 are linked to a TCER that specifies Test Plan M.
You can select optional parameter values to narrow the results included in defects reports.
| Report Name | Description |
|---|---|
| Defect list | For one or more selected test plans, this report lists all defects that are
associated (through a test case result) with a TCER in which the test plan attribute is one of the
selected test plans. The owner, state, severity, priority, creation date, resolution date, and test
plan are also identified for each defect. This report answers the question, “What defects are associated with this test plan and what is the status of those defects?” You can
narrow the results included in the report by selecting values for the following optional parameters:
This report pulls data from the data warehouse. Make sure that the data collection jobs have been run successfully. Tip: For each defect:
Also, if many defects have the same owner, you can follow up with the development team to consider reassigning some defects for faster resolution. |
| Defect arrival and resolution | For the selected test plan, this report displays a line chart that shows the
number of defects that are open, in progress, and closed over time. The lines reflect only defects
that are associated (through a test case result) with a TCER in which the test plan attribute is the
selected test plan. The time period reflected in the line chart runs from the earliest creation date
to the latest creation date among the defects included in the report. This report answers the question, “How are we doing on finding and fixing defects?” You can narrow the results included in the report by selecting values for the optional Test Milestone parameter. This report pulls data from the data warehouse. Make sure that the data collection jobs have been run successfully. Tip: If you are nearing the end
of an iteration or release, you typically expect that as the number of closed defects increases, the
number of open defects approaches zero. If the number of open defects and the number of closed
defects are rising at the same time, then the defect submission rate exceeds the defect resolution
rate, suggesting that testing is not nearing completion yet.
|