Test Prioritization or Test Case Prioritization

Testing a software or application is the most important phase of Software Development Life Cycle (SDLC). It plays a very essential role in deciding the quality and functionality of the software and ensures that the end product is as per client’s demand. The Testing of the software is done to detect faults and errors in its functionality, on the basis of which the performance and quality of the software is further improved. Test Prioritization is an extension of software testing, which is implemented to decide the priority of the test cases.

This priority of the test cases is decided through various factors that depend upon the need of the software, which are then assigned to the test cases for further processes. By prioritizing test cases, testers and developers are able to minimize the time and cost of software testing phase and make sure that the delivered product is of exceptional quality.

What is Test Prioritization?

The term "Test Prioritization" refers to the subjective and difficult part of testing that allows testers to manage risks, plan tests, consider cost value, and be analytical about which test to run in the context of the specific project. This process, is well known as Test Case Prioritization, which is a method of prioritizing and scheduling test cases. This techniques is used in order to run test cases of higher priority in order to minimize time, cost and efforts during software testing phase.

Furthermore, "Test Case Prioritization" provides assistance with regression testing and improves its performance. Through this method, testers can easily run test cases, which have the highest priority and provide earlier defect faults. Also, an improved rate of fault detection during the testing phase, allows faster feedback of the system that is under test. With test case prioritization software engineers can get assistance in correcting faults earlier than might otherwise be possible. Moreover, to decide the priority of test cases, various factors depending upon the need of the software are decided.

Aspects to Consider While Prioritizing Test Cases

Test case prioritization is an extremely important element of software testing. It allows testers to test highest priority test cases, which helps them resolve most critical issues earlier in the testing phase. However, it is essential for the testers to follow several factors while executing test case prioritization.

These factors ensures that proper testing is executed in appropriate order and also validates that all discrepancies are detected during the process of testing. The aspects that are required to be considered while prioritizing test cases are:

• The tester should consider the usage frequency of a function or the probability of failure in software use.
• Business value measure.
• Project change volatility.
• Development complexity.
• Fault proneness of requirement.

3. Prioritization in Case of Regression Testing: To achieve prioritization in the case of regression testing testers can choose from overall nine techniques. Each of these techniques various elements of the test cases are measured, which help in deciding their priority. These nine techniques are:

No prioritization: In this no techniques are implemented and is been used as an untreated test suit and it serves as a control.

• Random Prioritization: This is applied to have an additional control in studies where the test cases are ordered randomly in the test suite.
• Optimal Prioritization: Known faults are used so that its results can be used to measure the effects of other prioritization techniques that will be used.
• Total statement coverage prioritization: It instruments the program with any test cases and finds out which statements were covered by the test cases, which are then prioritized on the basis of the number of statements they covered.
• Additional statement coverage prioritization: Covers the shortcomings of Total Statement coverage prioritization and iteratively selects test cases that give highest statement coverage, then it adjusts the coverage information on rest of the test cases to find out the statements not yet covered.
• Total branch coverage prioritization: Mostly similar to additional statement coverage technique, it uses test coverage measured in form of program branches as there was the case of statements in other technique.
• Additional branch coverage prioritization: This technique is similar to additional statement coverage technique, with the only difference that it uses test coverage measured in terms of program branches and not statements.
• Total fault-exposing potential prioritization: As some test cases can expose faults more easily as compared to others, so it is called as fault-exposing potential of a test case.
• Additional fault-exposing potential Prioritization: As additions were made in total coverage and branch coverage prioritization, extensions were made in total fault-exposing potential prioritization and as a result this technique is created, where total fault exposing potential is extended to create additional fault exposing potential prioritization.

Challenges in Test Prioritization:

While executing test case prioritization, the team of testers can encounter several challenges that make the process of testing time consuming and difficult. Therefore, the team of testers are required to pay additional attention to the following mentioned challenges. By taking care of these factors, the testers can initiate safe and secure testing as well as get accurate result. These challenges are:

1. Detecting change and affected parts of the program.

2. Scalability to handle complex systems.

3. Integrating seamlessly into development process.

Conclusion:

Test case prioritization is best technique to ensure the effectiveness as well as the quality of a product, during its development and testing process. It is one such method that prioritizes and schedules test cases according their highest and lowest requirement. Through test case prioritization, testers can effectively make sure that the most important test cases are executed first.

This way important problems and defects can be found in the software or application as early as possible. Moreover, this testing provides assistance in regression testing and allows testers to order their test cases, so that test cases with highest priority are executed in the testing process, than the lower priority test cases.

Ref: 
https://www.sciencedirect.com/science/article/abs/pii/S0950584916304888
http://www.professionalqa.com