Trend report types
Trend reports include information about work performed on issues, requirements, requirement documents, test cases, or manual test runs over time. Use these reports to evaluate the efficiency of a project and identify patterns that occur over time. Add a chart to display data in a timeline.
Following are the content options available on the Report On tab in the Add and Edit Trend Report dialog boxes. The available options depend on the item type you are reporting on.
Items included in the report depend on the filter selected in the report.
Actual vs. Note: This report is not available for requirement documents. It is most useful for reporting on issues and manual test runs.
Displays actual hours versus estimated hours for items in closed workflow states during a specified time period. Uses the sum of field values selected in the Actual Hours fields and Estimated Hours fields in the Time Tracking project options for the item type.
For example, this report can help you answer questions such as:
- Were issues fixed and verified within the original estimated time?
- Are manual test runs performed within the estimated time frame each week? Are QA analysts underestimating or overestimating time to complete manual test runs?
Report content
- The X axis displays a column for estimated hours and a column for actual hours.
- The Y axis displays rows for the specified time period (days, weeks, or months).
- Each cell displays the actual or estimated hours for items during the period in the row.
Open age during period
Displays the number of open items during a specified time period to show how long they have been open. Items are grouped in the following periods: less than 15 days, 15 days, 30 days, 45 days, 60 days, 75 days, and 90 or more days.
Tip: This report is most useful for reporting on issues and manual test runs.
For example, this report can help you answer questions such as:
- Are customer-reported issues resolved and closed within 90 days?
- Are manual test runs performed within 14 days after they are generated from test cases?
Report content
- The X axis displays columns for the periods that items were open (e.g., 15 days, 30 Days, 45 Days).
- The Y axis displays rows for the specified time period (days, weeks, or months).
- Each cell displays the number of items open for the number of days defined in the column during the period in the row.
Open vs. closed
Displays the total number of items in open workflow states versus closed states during a specified time period.
Tip: This report is most useful for reporting on issues and manual test runs.
For example, this report can help you answer questions such as:
- Is the total number of open issues decreasing at an acceptable rate?
- Are manual test runs generated and performed at an acceptable rate?
Report content
- The X axis displays a column for open items and a column for closed items.
- The Y axis displays rows for the specified time period (days, weeks, or months).
- Each cell displays the number of items in open or closed states during the period in the row.
Open or closed by field
Note: This report is only available for requirements and requirement documents.
Displays the total number of items in open workflow states or closed states during a specified time period grouped by field.
For example, this report can help you answer questions such as:
- How many requirements marked as suspect have been made obsolete?
- Are tasks tracked as requirements completed in order of importance?
Report content
- The X axis displays columns for each value in the selected field.
- The Y axis displays rows for the specified time period (days, weeks, or months).
- Each cell displays the number of open or closed items with the field value defined in the column during the period in the row.
Items moved to different workflow states during the period
Displays the number of transitions, or times items moved to each workflow state, during a specified time period.
For example, this report can help you answer questions such as:
- Are requirements implemented at an expected rate? Is there a bottleneck in reviewing and approving requirements? Is the number of requirements needing changes increasing?
- Is the number of requirement documents needing changes increasing? Are requirements included in documents captured accurately or requiring a lot of changes?
- Are more issues found than fixed each week? Is the number of issues fixed each week comparable to the number verified or is there a bottleneck in verifying fixes? Is the number of issues found each week decreasing as the release approaches?
- How many test cases change each week? Is the number of obsolete test cases increasing?
- Is the number of failed manual test runs increasing? Is the number of manual test runs waiting or in progress decreasing each day?
Report content
- The X axis displays columns for states that items moved to during the specified date range.
- The Y axis displays rows for the specified time period (days, weeks, or months).
- Each cell displays the number of items that moved to the state defined in the column during the period in the row.
Additional options
Select any of the following options to include additional information in the report.
- Count duplicate state changes increments the value each time an item moved to the state during the period in the row. If this option is not selected, each move is counted only once.
- Include column with total number of items open when the period started includes an Open at Start column that displays the total number of items in an open state at the start of the period in the row.
Items in each workflow state during the period
Displays the total number of items in each workflow state during a specified time period. This option is not available for requirement documents.
For example, this report can help you answer questions such as:
- Are new issues fixed as quickly as they are found? Is there a bottleneck in fixing and verifying new issues?
- Are requirements written at an acceptable rate? Is the number of requirements requiring changes increasing? Is the rate at which draft requirements are decreasing, and approved and implemented requirements are increasing acceptable?
- Are test cases written at an acceptable rate? Is there a bottleneck in writing or reviewing new test cases?
- As the total of manual test runs increases, what is the rate they are performed and the ratio of passed versus failed?
Report content
- The X axis displays columns for states that items were in during the specified date range.
- The Y axis displays rows for the specified time period (days, weeks, or months).
- Each cell displays the total number of items in the state defined in the column at any point during the period in the row. If an item moved to the same state multiple times during the period, the number only increments once for each state.
Items in each workflow state when the period ended
Displays the total number of items in each workflow state at the end of a specified time period.
For example, this report can help you answer questions such as:
- Is the issue backlog growing? Is the team finding more issues than it can fix?
- What is the net quality for the release when comparing open versus closed issues?
- How many test cases are written each week?
- How many manual test runs are passed, failed, or blocked over time? How many manual test runs are completed each week?
Report content
- The X axis displays columns for states that items were in at the end of the specified date range.
- The Y axis displays rows for the specified time period (days, weeks, or months).
- Each cell displays the number of items in the state defined in the column at the end of the period in the row.
Workflow state by field
Displays the total number of times items moved to a specific workflow state during a specified time period grouped by field.
For example, this report can help you answer questions such as:
- How many documents are assigned to reviewers each week? Are documents reviewed and approved at an acceptable rate?
- How many issues are found by the Support, QA, and Development teams each week? How many issues are fixed in each product component each week?
- How many requirements are marked as suspect each week, indicating that requirement churn is high?
- How many test cases are written for each operating system each week?
- How many manual test runs are passed or failed by each tester each week?
Report content
- The X axis displays all values for the selected field. To only include specific values for the field, select a filter that only includes items with values set in the selected field and hide the empty columns
- The Y axis displays rows for the specified time period (days, weeks, or months).
- Each cell displays the number of items with the field value defined in the column in the selected workflow state during the period in the row.
Requirements — Project volatility
Displays the total number of requirements, new requirements, requirements with workflow state changes, and closed requirements during a specified time period. This report is helpful for monitoring requirement churn. The more requirements are added, change states, or closed, the more risk that the requirements capture process is not nearing completion, which may put implementation at risk.
For example, this report can help you answer questions such as:
- Are new requirements still being added for the upcoming release?
- Are requirements still being reviewed, approved, or changed? Is the number going down to indicate that churn is decreasing?
Report content
- The X axis displays the following columns: Total Requirements, Submitted, State Changed, Closed, Totals.
- The Y axis displays rows for the specified time period (days, weeks, or months).
- Each cell displays the number of requirements in each category defined in the column during the period in the row.
| Value | Description |
|---|---|
| Total Requirements | Total number of requirements in the project during the period. |
| Submitted | Number of new requirements added. |
| State Changed | Number of requirements with state changes. |
| Closed | Number of requirements closed. |
Test runs — Completion status
Displays the number of Waiting, In Progress, and Completed manual test runs during a specified period, including the total estimated run time, actual run time, and estimated remaining time.
For example, this report can help you identity a bottleneck in performing and completing new manual test runs.
Report content
- The X axis displays the following columns: Total, Waiting, In Progress, Completed, % Completed, Estimated Run Time, Actual Run Time, and Estimated Remaining Time.
- The Y axis displays rows for the specified time period (days, weeks, or months).
- Each cell displays the number of manual test runs in each status or time defined in the column during the period in the row.
| Value | Description |
|---|---|
| Total | Total number of manual test runs. |
| Waiting | Number of manual test runs not yet started. Manual test runs are Waiting if they are open and in the initial workflow state for new manual test runs. |
| In Progress | Number of manual test runs started, but not completed. Manual test runs are In Progress if they are open and not in the initial workflow state for new manual test runs. |
| Completed | Number of manual test runs completed. Manual test runs are Completed if they are in a closed workflow state. |
| % Completed | Percentage of manual test runs completed. Calculated by dividing the number of manual test runs with a Completed status by the total number of manual test runs. |
| Estimated Run Time | Total estimated time to perform manual test runs. Calculated by adding the values in the manual test run Estimated run time field for all manual test runs in the row. |
| Actual Run Time | Total actual time to perform manual test runs. Calculated by adding the Actual Hours field values for all manual test runs in the row. |
| Estimated Remaining Time | Total estimated remaining time to perform manual test runs. Calculated by subtracting the Actual Run Time from the Estimated Run Time. |
Test runs — Run result status
Displays the total number and percentage of Waiting, In Progress, Passed, and Failed manual test runs during a specified time period.
For example, this report can help you identify how many manual test runs in a manual test run set passed each week and if the percentage of passed tests is acceptable.
Report content
- The X axis displays the following columns: Total Manual Test Runs, Waiting, % Waiting, In Progress, % In Progress, Passed, % Passed, Failed, % Failed, Undetermined, and % Undetermined.
- The Y axis displays rows for the specified time period (days, weeks, or months).
- Each cell displays the number or percentage of manual test runs in each status defined in the column during the period in the row.
| Value | Description |
|---|---|
| Total Manual Test Runs | Total number of manual test runs. |
| Waiting | Number of manual test runs not yet started. Manual test runs are Waiting if they are open and in the initial workflow state for new manual test runs. |
| % Waiting | Percentage of manual test runs waiting. Calculated by dividing the number of manual test runs with a Waiting status by the total number of manual test runs. |
| In Progress | Number of manual test runs started, but not completed. Manual test runs are In Progress if they are open and not in the initial workflow state for new manual test runs. |
| % In Progress | Percentage of manual test runs in progress. Calculated by dividing the number of manual test runs with a Waiting status by the total number of manual test runs. |
| Passed | Number of manual test runs completed and passed. |
| % Passed | Percentage of passed manual test runs. Calculated by dividing the number of passed manual test runs by the total number of manual test runs. |
| Failed | Number of manual test runs completed and failed. |
| % Failed | Percentage of failed manual test runs. Calculated by dividing the number of failed manual test runs by the total number of manual test runs. |
| Undetermined | Number of closed manual test runs that were not in a passed or failed state, such as Undetermined. |
| % Undetermined | Percentage of manual test runs that were not in a passed or failed state. Calculated by dividing the number of other manual test runs by the total number of manual test runs. |
Test runs — Completion status by field
Displays the total number of, percentage of, or time for manual test runs in a specified status filtered by a selected field during a specified time period. The completion statuses are Total, Waiting, In Progress, Completed, % Completed, Estimated Run Time, Actual Run Time, and Estimated Run Time.
For example, this report can help you answer questions such as:
- How many manual test runs passed this week?
- How long is each tester taking to complete their assigned manual test runs?
- What is the estimated remaining time to complete the manual test runs assigned to each user?
Report content
- The X axis displays columns for each value in the selected field.
- The Y axis displays rows for the specified time period (days, weeks, or months).
- Each cell displays the number, percentage, or time for manual test runs for the field value defined in the column during the period in the row.
Test runs — Run status by field
Displays the total number or percentage of manual test runs in a Waiting, In Progress, Completed, Passed, Failed, or Undetermined status during or at the end of a specified time period grouped by field. The statuses are Waiting, % Waiting, In Progress, % In Progress, Passed, % Passed, Failed, % Failed, Undetermined, and % Undetermined.
For example, this report can help you answer questions such as:
- What percentage of manual test runs were passed by each tester each week?
- Are there any testers failing more manual test runs than other testers?
- What percentage of manual test runs failed based on the web browser used for testing?
Report content
- The X axis displays columns for each value in the selected field.
- The Y axis displays rows for the specified time period (days, weeks, or months).
- Each cell displays the number or percentage of manual test runs for the field value defined in the column during the period in the row.
