Requirements reports

Requirements reports provide information about requirements coverage, execution status in relation to requirements, and the impact of defects on requirements.

Purpose

Requirements reports answer the following questions:

  • How are we doing on requirements coverage?
  • Which plan requirements still need test case coverage?
  • Which plan requirements are affected by defects and what is the status of those defects?
  • Which test cases and test suites cover the requirements that are affected by defects?
  • Which test cases are not associated with a plan requirement?
  • What is the status of requirements testing for this test plan?
  • What is the status of requirements validation for this test plan?

These reports include only requirements in the Requirements Management application that is configured to provide requirements to the quality management project and only if the Requirements Management application uses the same Jazz® Team server as the quality management project.

All of these reports rely on data pulled from the data warehouse, so make sure that the data collection jobs have been run successfully.

In many of these reports, you can select optional parameter values to narrow the results included in the report.

Reports will not include requirements added to a test case from a module view. If a requirement needs to be added to a test case from the module view, the module must first be added to the collection. Then the requirements coverage report (e.g. Requirements Coverage by Test Case) will include the requirements.

Important: The term plan requirement refers to a requirement in the requirement collection that is associated with the test plan. If a requirement is not in the requirement collection that is associated with the test plan, or the requirement collection is not associated with the test plan, then that requirement is not a plan requirement and is not included in these plan requirement reports.
Requirements Plan relationships

In the preceding image, note that:

  1. Requirement 21 is not a plan requirement because its Requirement Collection A is not associated with Test Plan Z.
  2. Requirement 22 is not a plan requirement because it is not in Requirement Collection A (the requirement collection that is associated with the Test Plan Z).
  3. Requirement 23 is a plan requirement because it is in Requirement Collection A, which is associated with Test Plan Z.
Table 1. Requirements report descriptions
Report Name Description
Plan Requirements Coverage Detail

This report lists, for the selected test plan, all of the plan requirements and the test case that each requirement is covered by (associated with) if the test case is in the selected test plan.

It answers the question, “Which plan requirements are covered by which test cases?”

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

Tip: For each requirement that is not covered:
  1. If the requirement is not yet associated with the test case that covers it, add the requirement to the test case.
  2. If a test case to cover the requirement has not been created yet, create the test case within the test plan and then add the requirement to the test case.
Plan Requirements Coverage by Test Case

This report displays, for the selected test plan, a pie chart with two portions: Covered, representing plan requirements that are associated with a test case in the test plan and Not Covered, representing plan requirements that are not associated with a test case in the selected test plan.

It answers the question, “How are we doing on requirements coverage?”

Click a portion of the pie chart to see which plan requirements are represented by that portion.

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

Tip: For each plan requirement that is not covered:
  1. If the requirement is not yet associated with the test case that covers it, add the requirement to the test case.
  2. If a test case to cover the requirement has not been created yet, create the test case within the test plan and then add the requirement to the test case.
  3. Reports do not included requirements added to a test case from a module view
Plan Requirements Defect Impact

For one or more selected test plans, this report contains three lists:

  • The Requirements impacted by defects list shows, for each plan requirement, each associated test case that has a defect related to it (through a test case execution record (TCER) and its test case result), and the name and state of each defect related to each test case. It answers the question, “Which plan requirements are affected by defects and what is the status of those defects?”
  • The Test cases impacted by blocked requirements list shows, for each test case that (1) is associated with a plan requirement and (2) has a blocking defect related to it (through a TCER its test case result), the associated plan requirements. It answers the question, “Which plan requirements are affected by blocking defects, which prevent successful completion of one or more TCERs associated with the test case that is associated with the plan requirement?”
  • The Test suites impacted by blocked requirements list shows the same test cases and plan requirements that are included in the Test cases impacted by blocked requirements list grouped by the test suite that the test case is in. It answers the question, “Within each test suite that contains a test case with a blocked TCER, which plan requirements are affected by blocking defects, which prevent successful completion of one or more TCERs associated with the test case that is associated with the plan requirement?”
You can narrow the results included in the report by selecting values for these optional parameters:
  • Requirement
  • Test Milestone
  • TCER Owner
  • TCER State
Note: This report includes only plan requirements associated with test cases (in a selected test plan) that have at least one TCER. This report does not include test case results associated with TCERs that are not associated with one of the selected test plans.

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

Tip: For each plan requirement that has one or more related defects, the associated test case or test suite should be run again after the defects are fixed.
Plan Requirements Execution using TCER Count

This report displays a bar chart that shows, for one or more selected test plans, each plan requirement, the number of TCERs associated with the test case that is associated with the requirement, and the state of the most recent test case result associated with each TCER, provided that the TCER is associated with one of the selected test plans.

Note: This report includes only plan requirements associated with test cases (in a selected test plan) that have at least one TCER.

It answers these questions about the status and results of testing activities:

  • “How are we doing on testing the requirements for this test plan?”
  • “How are we doing on validating the requirements for this test plan?”

You can narrow the results included in the report by selecting values for these optional parameters:

  • Test Milestone
  • TCER Owner
  • TCER State

Click a bar in the bar chart to see which plan requirements are represented by that bar.

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

Tip: For each plan requirement that has a test case result in a state other than Passed, testing is not complete.
Plan Requirements Execution using Weight

This report displays a bar chart that shows, for one or more selected test plans, each plan requirement and the number of TCER weight points in each state (based on the most recent test case result associated with each TCER) provided that the TCER is associated with one of the selected test plans.

Note: This report includes only plan requirements associated with test cases (in a selected test plan) that have at least one TCER.

It answers these questions about the status and results of testing activities:

  • “How are we doing on testing the requirements for this test plan?”
  • “How are we doing on validating the requirements for this test plan?”

You can narrow the results included in the report by selecting values for these optional parameters:

  • Test Milestone
  • TCER Owner
  • TCER State

Click a bar in the bar chart to see which plan requirements are represented by that bar.

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

Tip: For each plan requirement that has TCER points in a state other than Passed, testing is not complete.
Plan Requirements Not Covered Detail

This report lists, for the selected test plan, all of the plan requirements that are not covered by (associated with) at least one test case in the selected test plan.

It answers the question, “Which plan requirements still need test case coverage?”

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

Tip: For each plan requirement that is not covered:
  1. If the requirement is not yet associated with the test case that covers it, add the requirement to the test case.
  2. If a test case to cover the requirement has not been created yet, create the test case within the test plan and then add the requirement to the test case.
Plan Test Cases Not Covering Requirements

This report lists, for each selected test plan, all test cases that are not associated with a plan requirement.

It answers the question, “Which test cases are not associated with a plan requirement?”

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

Tip: For each test case that is not covering a plan requirement:
  • If the test case is no longer needed, remove it from the test plan. (Perhaps the test case covers a feature that was postponed to a future release defined by another test plan. Or maybe the test case is associated with a requirement that was removed from the requirement collection that is associated with the test plan.)
  • If the test case is intended to cover a plan requirement, add the requirement to the test case.
Requirements Traceability

This report lists, for the selected requirements projects, each requirement, its coverage status (cover or no cover), and the test plan that is associated with the requirement collection that contains the requirement. Alternatively, you can show the test case that is associated with the requirement by selecting Show Test Case in the optional Test Case or Test Plan parameter.

It answers the question, “Which test plans (or test cases) cover the requirements in this requirements project?”

You can narrow the results included in the report by selecting values for the optional Requirement Type parameter.

Make sure to link all test plans with a requirement collection that contains a requirement.

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

Tip: For each requirement that is not covered:
  1. If the requirement collection that contains the requirement is not associated with a test plan, add the requirement collection to a test plan.
  2. If the requirement is not included in any requirement collections, it is not a plan requirement and will not be included in any of the plan requirement reports. Investigate further to determine whether the requirement should be included in a requirement collection.
  3. If the requirement is not yet associated with the test case that covers it, add the requirement to the test case.
  4. If a test case to cover the requirement has not been created yet, create the test case within the test plan and then add the requirement to the test case.