Regression Testing is the phase which ensures that your current services or product offering still works as they did prior to the code related change or configuration enhancements you are making. Also as software is fixed, the emergence of new or old defects is quite common. Sometimes reemergence occurs because a fix gets lost through poor release management (or simple human error in version control). Frequently, a fix for a problem in one area inadvertently causes a software bug in another area. It has often been the case that when a feature is redesigned, the same mistakes that were made in the original implementation of the feature were made in the redesign.

the problem..

Traditionally, regression testing has been performed by a software quality assurance team after the development team has completed work. It is important to note that defects found at this stage are the most costly to fix. Usually at the end of the project where funding is drying up.

the solution..

We address the risk by introducing regression sets (manual or automated) throughout the test phases and also tightening the entry criteria gate by introducing critical regression tests early to reduce the risk of major bugs close to your completion date.

the method..

DX will baseline your environment and solution when it exits build to ensure your current functionality has not regressed, this can be done manual or in an automated manor. This will also act as a shakeout of your solution, then run a drop regression plan across common modules which change from drop to drop; ensuring defects are detected early and to give you the ability to roll back change if required.