Versions Compared

Old Version 4

changes.mady.by.user Roopa P

Saved on

compared with

New Version Current

changes.mady.by.user Roopa P

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
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

Overview

Definition (Hover Text)

This KPI measures the progress of automation of automating the regression test suite in terms of percentage , expressed as the percentage of test cases that have been automated out of the total regression testcasestest cases.

Source Tools

  • Zephyr

  • Jira Test

  • Data Upload

Graph type

Line Chart

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
Example

Trend

Higher the percentage, better is the ‘Quality’Let’s say your team has the following data at the end of an iteration:

  • Total number of regression test cases available: 200

  • Number of regression test cases automated: 150

Using the formula, the Regression Automation Coverage would be calculated as follows:

Regression Automation Coverage =150 / 200 ​=0.75 or 75%

Trend

A higher percentage indicates better quality, as more regression tests are automated, leading to more efficient and reliable testing.

Maturity Levels

M1 - <20%

M2 - 20-40%

M3 - 40-60%

M4 - 60% - 80% , 

M5 - > 80%

Instance level thresholds

-Target KPI Value denotes the bare minimum a project should maintain for a KPI.

Configurations

Processor Fields

NA

Mandatory fields

NA

How to Validate KPI

Suggested ways of working

Sample JQLs

Best Practice

Prioritize Test Cases

Focus on automating test cases that cover critical functionalities and high-impact areas first.

Automate test cases for areas of the application that undergo frequent changes.

Maintain Test Scripts

Regularly update and maintain test scripts to ensure they remain effective and relevant.

Refactor test scripts to improve readability and maintainability.

Monitor and Review

Regularly monitor the progress of automation and review the effectiveness of automated tests.

Establish a feedback loop to continuously improve the automation process based on test results and team feedback.

Benefits of KPI

How does the KPI help

Efficiency

Automated tests can be run repeatedly with the same accuracy, ensuring consistent results

Cost Savings

Automation reduces the need for manual testing, saving time and resources. Automated tests can catch defects early in the development cycle, reducing the cost of fixing them later

Improved Quality

Automation allows for more extensive testing, covering more scenarios and edge cases. Automated tests are less prone to human error, ensuring more reliable test results

Continuous Integration

Automated tests can be integrated into the CI/CD pipeline, enabling continuous testing and faster feedback.

C