Change-Related Testing – Software Testing

Watch This Video

Testing a system following modifications or corrections; includes re-testing and regression testing. This is testing following a change or fix to the software or environment. This should involve two types of test:

Re-testing or confirmation testing, that reruns test cases that previously failed in order to verify the success of corrective actions.

Regression testing of a previously tested program following modification to ensure that defects have not been introduced or uncovered in unchanged areas of the software as a result of the changes made. An estimated 20% to 50% of changes introduce new defects.

It may be performed at all test levels and types, including functional, non-functional and structural testing. Regression should take place at all stages of testing after a functional improvement or repair.


Automation testing, this is an advanced level for new be testers, make sure you follow my blog for other courses specifically on automation.

Retesting and regression should be repeatable, so they can re-run every time there is a change or fix.

Its essential to automate both re-testing and regression tests.

Automation is not a full substitute to manual testing as not 100% automation testing can be achieved and it shouldn’t.

What’s Next?

User Review
5 (2 votes)

Rogerio da Silva

Rogerio Da Silva has a passion for technology and above all, a passion to work with people building technology, going about talking to all the parts involved to understand and help to connect the dots by talking his way through testing and validating the product under development. In summary... Business & Test Analyst | Website Consulting | Email Consulting | Microsoft Dynamics 365 CRM | QA | Agile | Manual | Integration & Automation | DevOps | API | Cloud | AI | IoT | CRM | Social Media Marketing | Looking for Scalable Services? InShore, OffShore or Hybrid
 Interested? Ask me how we can help. Grab my Book here!.

%d bloggers like this: