Requirement Based System Test Case Prioritization of New and Regression Test Cases

Abstract

Test case prioritization schedules the test cases in an order that increases the effectiveness in achieving some performance goals. One of the most important performance goals is the rate of fault detection. Test cases should run in an order that increases the possibility of fault detection and also detects the most severe faults at the earliest in its testing life cycle. Test case prioritization techniques have proved to be beneficial for improving regression testing activities. While code coverage based prioritization techniques are found to be studied by most scholars, test case prioritization based on requirements in a cost effective manner has not been used for studies so far. Hence, in this paper, we propose to put forth a model for system level Test Case Prioritization (TCP) from software requirement specification to improve user satisfaction with quality software that can also be cost effective and to improve the rate of severe fault detection. The proposed model prioritizes the system test cases based on six factors: customer priority, changes in requirement, implementation complexity, usability, application flow and fault impact. The proposed prioritization technique is experimented in three phases with student projects and two sets of industrial projects and the results show convincingly that the proposed prioritization technique improves the rate of severe fault detection.

Model-based test case prioritization using cluster analysis: a soft-computing approach

“…It is therefore important to decide which part of the software should be tested first. For this purpose, test case selection, test suite reduction, and test case prioritization methods are suggested in the literature [26][27][28][29][30][31][32][33][34][35].…”

“…Srikanth et al suggested a value-driven approach to system-level test case prioritization, called the prioritization of requirements for test, based upon four factors: requirements volatility, customer priority, implementation complexity, and fault proneness of the requirements [31]. Krishnamorthi et al proposed a prioritization technique at the system level for both new and regression test cases [32]. Srivastava and Thiagarajan built Echelon, a test prioritization system, which prioritizes a given set of tests based on what changes have been made to the software before [33].…”

A Systematic Literature Review on Regression Test Case Prioritization

“…Besides code-based, other TCP approaches have also been developed. According to a study [11], since a system is built from many requirements, the use of information from the requirements can increase error discovery. For this reason, some researchers argue it is essential to develop requirementsbased TCP, while the studies in this area are still limited.…”

Test scenario prioritization for object-oriented systems using UML diagram

“…The test case generation process is still manual, though many research work have been made to make it an automated process (Samuel and Joseph 2008). In this paper, we have used an MBT technique for test case generation and prioritization (Yoo and Harman 2007;Krishnamoorthi and Mary 2009).…”