Skip to main content

Ensure Effective Regression Testing in 5 Ways!

Regression testing is essential as it aims to find failures in the product after code changes, support of new environment or product release.

By regression testing you also ensure user confidence assessing if the product’s new version is better than the previous one. Although many companies still ignore its necessity and fail to run product tests after the release, this testing stage should not be overlooked.

Below are 5 accepted ways to perform regression testing of your product.

1. Run all existing tests
This means that all the tests written and run before should be rerun after the release. However, especially if they all are manual, testers are going to have a huge pile of work. Probably you don’t have that much time and resources to be wasted. The fact that it’s impossible to perform 100% overall testing of the product also adds to this.
2. Run tests with high risk
In this method you should take into consideration the tests presenting the most value to your business users. Mostly such tests are those having to do with functionality and the most frequent activities of the business users. It’s not excessive to also note that with product changes the key processes may vary as well. Allot 30-40% of total regression time for tests with high risk depending on other things that need testing.
3. Testing high-defect features
You can as well tests high defect areas of the product, often highly complex areas. Usually complex is the feature that includes sophisticated calculations or integrates with other applications. The functionalities having many past defects also come within this set.
4. Exploratory testing
It is about building test case design along with its execution. In the course of building and execution of these tests you can discover problems within the application that will drive your following tests.
5. Automation testing
You may cut the test number to be run manually by automating them. For quick execution, use automation tools which reduce time for test running greatly. However, be sure that you’ve put aside some time for developing automation scripts. Also note that in case of environment changes they will need respective updates.
You can use these methods to run regression testing and ensure the high quality of your products.


Popular posts from this blog

My Testbash Brighton 2017 Notes

This was my second Testbash... if you ever get the chance in the future these conferences are a must!
I took copious amounts of notes from the 9 talks and tried to highlight my key takeaways here... hope they make sense but please comment if you have any questions :-)
Amy Phillips - Continuous Delivery
A survival guide to joining a fast paced environment/project…
Where does testing fit within Continuous delivery:

As highlighted, basically from start to finish…
There are lots of things we can do when joining a project that is using Continuous Delivery but one of the main points from this talk was to do your research! There should be an element of "Continuous" in every aspect of the project.
·Learning the ling, what's the difference Continuous Delivery, Continuous Deployment, Continuous Integration, Continuous design, Continuous Improvements etc.? ·Understand what your role in the project is going to be ·Understand the teams values, What's going well and maybe what the team p…

The way we work shouldn’t be ‘Alien’ anymore, Should it!?!?

It’s been a good while since I have written anything (Mainly because I’m not that good a writer) but given my 16 months in the public sector I thought it was time… 
For a good number of years now the DevOps trend has given rise of buzzwords and methods aiming to speed delivery and it’s now an assumption of mine that most organisations are au fait with the term ‘Continuous Delivery’.
I was wrong…
Within the organisation that I am currently placed I believe I have a high-functioning collaborative team who work flexibly and in continuous cycle. We also involve the users which is a huge benefit to the development teams, but that’s not saying we get everything right 100% of the time! Teams must continue to learn and evolve to remain productive.
Our team work in one of several delivery groups and with this comes multiple challenges; Silos No single environment strategy lack of communicationsVaried ways of working.  And thats just to name a few, which is interesting when all delivery groups …

Leeds Testing Atelier - April 2018