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

Defect reports answer the following questions:
  • 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 Quality Management 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.

Defect relationships
  1. 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.
  2. 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.
  3. 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.

Remember: Defects reports rely on data pulled from the data warehouse, so make sure that the data collection jobs have been run successfully.
Table 1. Defect report descriptions
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:
  • Test Milestone
  • TCER Owner
  • TCER State

This report pulls data from the data warehouse. Make sure that the data collection jobs have been run successfully.

Tip: For each defect:
  • If the defect is resolved, you can rerun the associated test case.
  • If the defect is unresolved, you can follow up with the defect owner to determine when the defect will be resolved and ready to retest.
  • Check the defect severity and priority. Many high severity defects might indicate a problem area that warrants more focused testing.
  • If the defect was created a long time ago and is still in the New state with the owner Unassigned, you can follow up with the development team to have the defect addressed.

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.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki