Monitor Testing Progress
You can monitor regression testing progress using standard Agility reports and custom analytics. Test set data rolls up into common project metrics, and you can filter views to focus specifically on regression testing activities.
Permission requirement: Viewing testing reports requires read access to projects, sprints, and test items included in the report scope. Creating custom Analytics reports requires Ultimate Edition and appropriate Analytics permissions.
Who Monitors Testing Progress
Testing progress tracking supports quality oversight:
- QA Managers use Test Trend reports to track regression testing results over time and identify systemic quality issues or bottlenecks.
- Scrum Masters monitor sprint burndown including test set To Do values to ensure testing doesn't delay sprint completion.
- Product Owners review test completion rates and pass rates to assess increment quality and make release go/no-go decisions.
- Portfolio Managers create custom Analytics reports with Ultimate Edition to track testing efficiency, defect discovery, and coverage across teams.
Test Trend Report
The Test Trend report is your primary tool for tracking regression testing results:
To view regression testing trends:
- Navigate to the Test Trend report.
- Apply the Test Sets filter to focus on regression testing data.
- View the progression of test results over time:
- Tests passed
- Tests failed
- Tests blocked
- Tests not run
The report shows testing velocity and helps identify bottlenecks or quality issues.
Regression Data in Standard Reports
Test set data automatically rolls up into these common reports:
Project Burndown
- Estimate values from test sets contribute to total project scope
- Track testing effort alongside development work
- View remaining test execution capacity
Sprint Burndown
- To Do values from test sets show remaining test execution work
- Monitor daily test completion progress
- Identify testing delays that might impact sprint goals
Velocity Graph
- Completed estimates from test sets contribute to team velocity
- Compare testing velocity across sprints
- Plan testing capacity for future sprints
Filter for Regression Testing
To focus reports specifically on regression testing:
- Open any backlog view or report.
- Apply the Workitem filter.
- Select Test Sets to show only regression testing data.
- View metrics and trends specific to regression testing activities.
This filtering works across all views and reports in Agility.
Custom Analytics Reporting
With Ultimate Edition, you can create custom regression testing reports using Analytics:
Custom report examples:
- Test execution rate by team or environment
- Defect discovery rate during regression testing
- Test coverage by functional area
- Testing cycle time and efficiency metrics
- Pass/fail trends by test suite or plan
Analytics provides flexible data exploration and custom visualizations for regression testing insights.
Track Key Metrics
Monitor these key metrics to assess regression testing effectiveness:
- Test completion rate: Percentage of scheduled tests executed
- Pass rate: Percentage of tests passing vs. failing
- Defect discovery: Number of defects found during regression testing
- Cycle time: Time from test set generation to completion
- Coverage: Percentage of suites tested per environment
Troubleshooting
Why don't test sets appear in my sprint burndown chart?
Test sets must be scheduled to a sprint to appear in sprint burndown. If test sets show To Do hours but don't appear in burndown, verify they're assigned to the sprint you're viewing. Use the Workitem filter to confirm test sets are included in your burndown scope settings.
Why does the Test Trend report show no data even though I've executed tests?
The Test Trend report requires acceptance tests (generated from regression suites) or test items with status updates. If you've only created regression tests without generating test sets, no execution data exists yet. Generate test sets from your regression suites and execute the acceptance tests to populate Test Trend data.
How do I track testing progress across multiple projects or teams?
Create a custom Analytics report (requires Ultimate Edition) with filters for specific projects, teams, or test plans. Standard reports show single-project data. For multi-project tracking without Ultimate Edition, export test completion data from each project and consolidate externally, or use portfolio-level rollup views if test sets are tagged appropriately.
Why do my velocity calculations seem incorrect when test sets are included?
Velocity includes completed estimate values from all work items, including test sets. If test sets have large estimates relative to story points, they can skew velocity. Verify your estimation approach is consistent: use similar scales for test sets and development stories (e.g., both in story points or both in hours), or exclude test sets from velocity calculations using workitem type filters.