Automated regression testing needs to be accessible by everyone, not just specialized test resources.
With QA personnel changes, or in fast-paced development environments, it is essential that automation can be manipulated without any impediments. These impediments normally revolve around the technical aspects of changing code to align with the new applications to be tested. Ease of baselining scripts is very important to allow regression to continue into the next test phase. If waterfall, this may be months away, but if dev/ops or agile, this may be much closer to hand.
The main reason automation efforts fail into disuse is the lack of people and time to correctly re-align the automation created to continue to justify the returns needed.
This is an extract from a whitepaper titled “Top Ten Factors for a Successful Regression Test” which takes you through the key factors that will ensure the best outcome – if all is as it should be and no defects have found their way through – then you have conducted a successful regression test.
Jonathan Pearson is a Customer Success Manager at Original Software.
