Select Page

Change-Related Testing – Software Testing

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?

About The Author

Rogerio da Silva is a Brazilian who lives in the UK for a little over two decades. He is the owner of a test consulting and outsources services for software development. He likes to blog, write and create content that teaches others how to live a better life. Rogerio has two princesses and one powerful wife that help him with his work. He loves reading biographies of successful authors and dream builders because they inspire him to keep creating!

Leave a reply


Now available on amazon prime

eBook (Amazon)

The Testers Book - An Unconventional Way to Software Testing - Revised Edition

Paperback (