Coverage Specification for Test Case Intent Preservation in Regression Suites

Shaccour, Elie M.; Zaraket, Fadi A.; Masri, Wes

doi:10.1109/icstw.2013.50

Cited by 6 publications

(14 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This method has high execution cost. Shaccour E et al [5] presented a coverage specification language and a methodology to preserve the intent of test cases in a regression test suite. The drawback of this method is the specification language which has some weaknesses.…”

Section: Problem Statementmentioning

confidence: 99%

“…This section discusses a numerical example of the greedy GreedyEIrreplaceability algorithm [5] and proposed GTAP algorithm. Table 1 shows running example of a GreedyEIrreplaceability algorithm.…”

Section: Running Example and Comparisonmentioning

confidence: 99%

“…Generally, a test suite minimization problem [1][2][3][4][5] can be simplified as a minimum set cover problem, which Karp has asserted as an NPcomplete problem. Numerous techniques have been reported in the literature.…”

Section: Introductionmentioning

confidence: 99%

“…A thorough description of the coverage specifications and the likewise test suite reduction schemes were presented in [4] and [5]. In [8], modelling-based test suite minimization problem is covered.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

A Cost-Aware Test Suite Minimization Approach Using TAP Measure and Greedy Search Algorithm

Sugave¹,

Patil²,

Reddy³

2017

IJIES

View full text Add to dashboard Cite

Software testing is required to detect the faults and to ensure the quality of the software under development. Usually, test suites are used to evaluate the software system during the software development cycle. But often test suites contain more redundant test cases due to overlapped test objectives. So, the test-suite reduction is an important step to reduce the number of test cases so as to satisfy the entire objectives with less computational cost. Literature presents different methods to select the suitable test suites of optimal subsets for regression testing. Accordingly, this research aims to develop an effective test suite reduction approach for regression testing. The proposed algorithm (GTAP) is newly designed using TAP measure and greedy search algorithm. This algorithm uses TAP-measure which is specially developed for measuring the importance of test cases. The performance of the GTAP algorithm is evaluated using four different evaluation metrics with eleven subject programs available in SIR repository. From the experimentation, the average performance of the proposed GTAP algorithm in all the programs is 93.07% which is higher than the DIV-GA which obtained the value of 90.27%.

show abstract

Section: Problem Statementmentioning

confidence: 99%

Section: Running Example and Comparisonmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

A Cost-Aware Test Suite Minimization Approach Using TAP Measure and Greedy Search Algorithm

Sugave¹,

Patil²,

Reddy³

2017

IJIES

View full text Add to dashboard Cite

show abstract

“…The test case can be prioritized by the failure rates or we can prioritize the test case by increasing the cost-per-coverage in the requirement features (Shaccour et al, 2013). In this approach the possibility of revealing the faults have to be increased at an earlier stage.…”

Section: Prioritizing the Fault Detection Ratementioning

confidence: 99%

A Novel Approach for Test Suite Prioritization

Jacob¹,

Ravi²

2014

Journal of Computer Science

View full text Add to dashboard Cite

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.

show abstract

UCov: a user‐defined coverage criterion for test case intent verification

Assi

Masri

Zaraket

2016

Software Testing Verif & Rel

Self Cite

View full text Add to dashboard Cite

The goal of regression testing is to ensure that the behavior of existing code, believed correct by previous testing, is not altered by new program changes. We argue that the primary focus of regression testing should be on code associated with: a) earlier bug fixes; and b) particular application scenarios considered to be important by the tester. Existing coverage criteria do not enable such focus, e.g., 100% branch coverage does not guarantee that a given bug fix is exercised or a given application scenario is tested. Therefore, there is a need for a new and complementary coverage criterion in which the user can define a test requirement characterizing a given behavior to be covered as opposed to choosing from a pool of pre-defined and generic program elements. We propose this new methodology and call it UCov, a user-defined coverage criterion wherein a test requirement is an execution pattern of program elements and predicates. Our proposed criterion is not meant to replace existing criteria, but to complement them as it focuses the testing on important code patterns that could go untested otherwise. UCov supports test case intent verification. For example, following a bug fix, the testing team may augment the regression suite with the test case that revealed the bug. However, this test case might become obsolete due to code modifications not related to the bug. But if an execution pattern characterizing the bug was defined by the user, UCov would determine that test case intent verification failed. It is also worth mentioning that our methodology paves the way for test case intent preservation, e.g., a failed verification could be followed by automated test case generation, the subject of future work. We implemented our methodology for the Java platform and applied it onto two real life case studies. Our implementation comprises the following: 1) an Eclipse plugin allowing the user to easily specify non-trivial test requirements; 2) the ability of cross referencing test requirements across subsequent versions of a given program; and 3) the ability of checking whether userdefined test requirements were satisfied, i.e., test case intent verification.

show abstract

Coverage Specification for Test Case Intent Preservation in Regression Suites

Cited by 6 publications

References 18 publications

A Cost-Aware Test Suite Minimization Approach Using TAP Measure and Greedy Search Algorithm

A Cost-Aware Test Suite Minimization Approach Using TAP Measure and Greedy Search Algorithm

A Novel Approach for Test Suite Prioritization

UCov: a user‐defined coverage criterion for test case intent verification

Contact Info

Product

Resources

About