Test case reports

Test case reports provide information about the status of test cases, test suites, or test scripts for a given scope.

Purpose

Test case reports answer the following questions:

  • What is the development status of test cases, test suites, or test scripts?
  • What are the counts of test cases, test scripts, and test suites by their states?
  • What are the TCER or test script coverage details of select test cases?
  • Which test cases fit selected categories by team area or test environment?
  • Which test cases have associated work items or are affected by defects?
Table 1. Test case report descriptions
Report Name Description
Test artifact States (Live)

For one or more selected test plans, this report displays counts of test cases, test scripts, and test suites in the selected plans by their development state. The results are presented in a bar graph for each artifact type that is broken down by development states (Approved, Draft, Retired, or Under Review) for artifacts associated with each selected test plan.

You can further drill down on artifacts in a specific state by clicking a section of a bar. This action opens a report, <Artifact type> by Development State (Live), that displays a list of the test cases, test suites, or test scripts in the selected state.

This report answers these questions:
  • What is the status of test artifact development for the test plan?
  • Which test artifacts are ready for review, and which are still being completed?
You can narrow the results that are included in the report by selecting values for these optional parameters:
  • Test Case State
  • Test Script State
  • Test Suite State
Tip: Check these items for each test plan:
  1. Depending on the time frame, having several test artifacts in Draft status might indicate that you are falling behind in artifact development within a specific iteration or overall.
  2. Having several Under Review test artifacts might indicate that reviews are not being completed in a timely manner.
Test Case Coverage by TCER (Live)

For one or more selected test plans, this report displays a chart that shows the counts of test case execution records and their states by test case.

The bar graph shows, for each test case, bars that represent the number of TCERs for each test result status (passed, failed, blocked, and so on). The bar graph is followed by a table representation of the same information.

Move the cursor over a segment of a bar graph to see how many TCERs are included in that segment. Click a segment of the bar graph to see a list of the TCERs that are represented by that segment.

The report displays test case coverage by TCER result. Counts of the TCER results for the given test cases are shown in the bar chart.

This report answers these questions:
  • What are the results of each test case’s execution?
  • Which test cases have a large number of TCERs in Failed, Not Run, Blocked, or other states that indicate lack of progress?
  • Which test cases have no TCER results or TCER results that are not passing?
Tip: Check these items for each test case:
  1. Depending on the time frame, having several TCERs that are not started might indicate that a tester is blocked in some way (for example, by other work priorities, technical difficulties, or an unavailable or unstable test environment).
  2. Many failed or blocked TCERs might point to an area that warrants more focused testing.
Test Case Coverage by Test Script (Live)

For one or more selected test plans, this report displays test script coverage for each test case.

A bar graph shows, for each test case, a bar that represents the test script count for the test case. The bar graph is followed by a table representation of the same information and includes the ID of both the test case owner and test script owner.

Move the cursor over a bar segment to see how many test scripts are represented by that segment. Click a segment of the bar graph to see a list of the test scripts, or link directly to individual scripts that are represented by that segment.

This report answers this question:
  • What is the test coverage in a test plan?
Tip: Test cases that do not have test scripts might indicate that scripts still need to be developed.
Test case Review

For one or more selected test plans, this report displays a range of test case details.

The first table shows test case state details. The second table shows requirements associated with the test cases, and the third table shows other work items associated with the test cases.

This report pulls data from the data warehouse. Ensure that the data collection jobs ran successfully.

This report answers these questions:
  • What is the status of test cases in a test plan?
  • Which requirements are associated with the test cases?
  • Which work items are associated with the test cases?
Tip: For each test case, watch for high numbers of test cases that are waiting for approval.
Test cases (Live)

For one or more selected test plans, this report displays all the test cases in the selected plans and their categories. It also lists test cases that are not contained in any test plan.

The first table shows the test cases that are associated with the selected plans. The second table shows test cases that are not associated with any plans.

This report answers these questions:
  • Which test cases are in plan?
  • Which test cases are not in any plan?
Tip: Watch for test cases that are not in any plan. Those test cases are likely not being used in your testing effort.
Test cases by Development State (Live)

For one or more selected test plans, this report displays all the test cases and their development state.

This report answers this question:
  • What is the development status of test cases in the test plan?
Tip: Watch for too many test cases that are still in a Draft or Under Review state. This situation could indicate a resource constraint in test artifact development.
Test cases by Team (Live)

For one or more selected test plans, this report displays test cases and their categories, grouped by team name.

A table shows the team names, test case names, category types, category names, and test case weights. From the results, you can open a test case by clicking the test case name.

This report answers these questions:
  • Which test cases are not assigned to a team area?
  • Which test cases are assigned to specific team areas?
Tip:
  1. The report design is based on a test-case-to-team-area association. In the project properties, the Enable team areas and support for multiple timelines check box must be selected.
  2. If you define a parameter for Test Team, test cases that are not directly associated with the selected team areas are not displayed. Leave the Test Team parameter cleared to show test cases that currently have a team area unassigned.
Test cases by Test Environment (Live) For one or more selected test plans, this report displays test cases and their categories, grouped by their test environment.

A table shows the test environment, test plan names, test case names, category types, and category names. From the results, you can open a configuration or test case by clicking the links.

This report answers this question:
  • Which test environments are assigned to test cases?
Test Cases Impacted by Defects

For one or more selected test plans, this report displays test cases that are associated with defects. Before you run this report, ensure that you add iterations to your test plans and generate execution records against these iterations.

A table shows test suites and test cases that are associated with defects. The defects that appear in the report are associated with the execution of TCERs or test suites. From the results, you can open the test cases and defects by clicking the links.

This report pulls data from the data warehouse. Ensure that the data collection jobs ran successfully.

This report answers this question:
  • Which test suites and test cases are associated with defects?
Tip: Watch for multiple defects associated with a test suite or test case. This situation might indicate an area that requires more testing attention.
Test scripts by Development State (Live)

For one or more selected test plans, this report displays all the test scripts, their parent test cases, and their development states. You can use this report to find test scripts that are in a specific state, such as Under Review.

This report answers this question:
  • What is the development status of test cases and test scripts in the test plan?
Tip: Watch for test scripts that are in an Approved state before their parent test case has been approved. This situation might indicate that changes are required to associated test scripts if parent test cases are changed during review.
Test suites by Development State (Live)

For one or more selected test plans, this report displays all the test suites, their child test cases, and their development states, such as Draft and Approved. You can use this report to find test suites that are in a specific state, such as Under Review.

This report answers this question:
  • What is the development status of test cases and test suites in the test plan?