How to implement an effective regression testing process
Published on
1. Have a plan.
A regression testing plan. Regression testing process is a team collaborative effort, you’d need collaboration from stakeholders, backend, devops to achieve this success.
People often forget so verbally communicating your testplan wouldn’t cut it. If you already have a software testplan updating it to include your regression testing strategy is very important.
Your regression test-plan will include tools, environment, key features of focus, testing types, strategy etc
Haven documented the test plan and tailored it to our quality need, it’s important to follow it and induce it to our team process regularly because we do not want to go back to square one.An effective regression workflow is one that is automated.
Regression testing involves retesting, continuous testing and continuous verification and validation.
This can only be achieved when we start with automations. To have an auto effective regression testing workflow therefore
We have 2 options
⁃ Develop our regression scripts immediately after completing manual testing, this way, it’s a core part of the test before moving to prod
⁃ Start writing the regression scripts after completing manual testing and moving to prod
But firstly let me describe a scenario. You are the only QA on your team but only brought in after the main features has been completed. Now even though you are part of the team and additional features and updates are coming, you have to maintain the current state of the system and also setup regression testing. This is NOT FOR YOU!
We have agreed during the course of this conversation that regression is a big deal hence it might be really challenging to achieve an effective regression testing workflow with just a single QA member.
