Abstract
The techniques of test case prioritization schedule the execution order of test cases to attain respective target, such as enhanced level of forecasting the fault. The requirement of the prioritization can be viewed as the en-route for deriving an order of relation on a given set of test cases which results from regression testing. Alteration of programs between the versions can cause more test cases which may respond differently to following versions of software. In this, a fixed approach to prioritizing test cases avoids the preceding drawbacks. The JUnit test case prioritization techniques operating in the absence of coverage information, differs from existing dynamic coverage-based test case prioritization techniques. Further, the prioritization test cases relying on coverage information were projected from fixed structures relatively other than gathered instrumentation and execution.
Highlights
Regression testing concentrates on finding defects after a major code change has occurred
Java programs tested in the JUnit framework, which is widely used in developing Java software
A JUnit test case is a piece of executable source code containing testing content, we are using a sample Java application which contains a large number of test suites, we execute the test cases in different testing criteria (TMC, AMC, TSC, ASC, TCC) are useful for identifying prioritized test cases
Summary
Regression testing concentrates on finding defects after a major code change has occurred. It exposes software regressions or old bugs that have reappeared. To improve the regression testing process, test case prioritization techniques organizes the execution level of test cases. It gives an improved rate of fault identification, when test suites cannot run to completion (Figure 1). As stated earlier, it provides an effective evaluation of previous coverage data accuracy, and creates an impact to the precision of prioritization. It prioritizes test cases based on coverage information estimated from static structures rather than gathered instrumentation and performance
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
