Overview | ||
---|---|---|
Definition (Hover Text) | measures progress of automation of regression test suite in terms of percentage automated out of total regression testcases | |
Source Tools |
| |
Graph type | Line | |
Filters | - | |
Hover Format on KPI | Sprint Name: <<Percentage Value>> Regression test cases automated: <<Value>> Total Regression test cases: <<Value>> | |
Fields on Overlay | Sprint Name Test case ID Automated | |
Business Logic | ||
Calculation Formula | No. of regression test cases automated till the end of iteration/Total no. of regression test cases available till the end of iteration | |
Trend | Higher the percentage, better is the ‘Quality’ | |
Maturity Levels | M1 - <20% M2 - 20-40% M3 - 40-60% M4 - 60% - 80% , M5 - > 80% | |
Instance level thresholds | - | |
Configurations | ||
Processor Fields | NA | |
KPI Specific Mandatory fields |
| NA |
How to Validate KPI | ||
Suggested ways of working | ||
Sample JQLs | ||
Benefits of KPI | ||
How does the KPI help | The Regression Automation KPI helps teams reduce manual effort and improve efficiency by automating repetitive regression testing tasks, leading to faster time-to-market, improved product quality, and reduced costs associated with testing. |
Page Comparison
General
Content
Integrations