Software testing is an expensive, time consuming, important activity that controls the quality of the software and important part of the software development and the maintenance. In testing the time is spent mainly for generating test cases and to test them. Whenever the software product gets modified, a group of the test cases has to be re-executed and the new output has to be compared with old one for avoiding the unwanted changes. If there is a match then the modifications that are made in the software will not affect other parts of the software. It is not practically possible to re execute all the test case in the program if any change has occurred. This problem of selection of those test case in regression testing can be re-solved by prioritizing the test case. This technique will reduce the testing effort. Different techniques were proposed in the past decades and still require further improvement. Here we propose a clustering based prioritization of the test case. The results achieved shows that prioritizing the test case has enhanced effectiveness of the test case.

Regression testing is testing the software in order to make sure that the modification made on the program lines does not affect the other parts of the software, it is in maintenance phase and accounts for 80% of the maintenance cost and thus optimizing regression testing is one of the prime motives of software testers. Here we take the advantage of selecting test case information available in regression testing and prioritize them based on the number of modified lines covered by the test case, the test case which covers the most number of modified lines has the highest priority and is executed first and the one with the least coverage of modified lines has the lowest priority and is executed last provided deadline time is not reached, thus even if the testing is not finished we will have covered maximum modified lines, the prioritization of the test cases are done using the genetic algorithm, the genetic algorithm takes test case information from regression testing as input and produces a sequence of test case to be executed such that the maximum number of modified code is covered.

No abstract