Method to automatically/dynamically identify and lauch the test suites, that have code updates in the new build

Method to automatically/dynamically identify and lauch the test suites , that have code updates in the new build

         Authors
Sathis R Marudanayagam, Girish J Burli

Problem Solved by this solution:

During the testing activity, the test team gets numerous builds in periodical manner (daily, weekly etc.). The new build may have code updates in couple of classes,

jars or dlls and may not

be a whole new one than the earlier tested builds. In those cases, either the test team needs to manually identify the test suites, which got affected, and execute it or running all the test suites blindly. When the project happens to be a larger one, these would be a time consuming activity and complex too. Finally, it would end up in delaying the release or insufficient test coverage. So, some intelligent system is to be developed pick and run the test suites automatically, instead of running all the test suites or picking up the test suites manually.

Some of the known solutions

Run all the available suites

Only execute the relate test suites by identifying the affected components manually

Drawbacks of known solutions

Running all the available test suites would take more time to get to know the build's stability and if there is any regression
Identifying the affected components and execute the relates test suites is a cumbersome activity
This activity is not a single time and it should be done for every build

This idea is to overcome this manual process and ensure the stability of new build and running re...