A Study on Coverage Criteria Based Test Case Reduction Techniques

2018 ◽  
Vol 7 (1) ◽  
pp. 38-44
Author(s):  
Prema P ◽  
Author(s):  
Sudhir Kumar Mohapatra ◽  
Srinivas Prasad

Software testing is one in all the vital stages of system development. In software development, developers continually depend upon testing to reveal bugs. Within the maintenance stage test suite size grow due to integration of new functionalities. Addition of latest technique force to make new test case which increase the cost of test suite. In regression testing new test case could also be added to the test suite throughout the entire testing process. These additions of test cases produce risk of presence of redundant test cases. Because of limitation of time and resource, reduction techniques should be accustomed determine and take away. Analysis shows that a set of the test case in a suit should satisfy all the test objectives that is named as representative set. Redundant test case increase the execution price of the test suite, in spite of NP-completeness of the problem there are few sensible reduction techniques are available. During this paper the previous GA primarily based technique proposed is improved to search out cost optimum representative set using ant colony optimization.


2012 ◽  
Vol 55 (12) ◽  
pp. 2826-2840 ◽  
Author(s):  
ChunRong Fang ◽  
ZhenYu Chen ◽  
BaoWen Xu

Author(s):  
Marwah Alian ◽  
Dima Suleiman ◽  
Adnan Shaout

2017 ◽  
Author(s):  
Yasir Dawood Salman ◽  
Nor Laily Hashim ◽  
Mawarny Md Rejab ◽  
Rohaida Romli ◽  
Haslina Mohd

Author(s):  
ZHONGSHENG QIAN

The specification-based testing can be employed to evaluate software functionalities without knowing program code. Decisions are the primary form of the pre- and post-conditions in formal specifications. This work expatiates on logic coverage criteria for specification-based testing at great length. It proposes and then expounds mask logic coverage criteria to solve the problems which existing determinant logic coverage criteria cannot solve. A feasible test case generation algorithm based on mask logic coverage criteria is developed. The test cases satisfying mask logic coverage criteria can detect those errors caused by the mask property of conditions. An experiment is conducted to compare MC/DC, RC/DC and two mask logic coverage criteria (RMCC and GMCC) on their test effectiveness and fault detection ability. It also elaborates on the constraint among conditions, how to decompose and compose a complicated decision, and the relationship among decisions. All these can respectively clarify the coupling problem among conditions, the multiple occurrences of a condition in a decision, and the location of a decision in a specification or program. Additionally, coverage criteria including full true decision coverage, full false decision coverage, all sub-decisions coverage, unique condition true coverage and unique condition false coverage are proposed. The test sets satisfying these criteria can detect respectively different types of errors. Finally, the hierarchical subsumption relation is established among these presented coverage criteria and some existing ones, and various applicable scenarios for different coverage criteria are suggested.


Author(s):  
Keslley Lima Silva ◽  
Érika Cota

Testing is an indispensable part of the software development process and is a continuous process during the development life cycle. In this context, examining the behavior of software systems to reveal potential problems is a crucial task. To this end, the test suites usually are utilized to examine the software quality. However, test suite quality control is hard for the tester, especially in an evolving system. Such control is needed to assure and improve the test suite's quality and the application as a consequence. Currently, test coverage criteria are used as a mechanism to assist the tester in analyzing the test suite (e.g., find the weaknesses, and add a new test case or test inputs). However, more strong coverage criteria (potentially showing less glaring weaknesses) are challenging to assess. In this work, we propose a different approach to support the developer in evaluating the test suite quality based on more powerful test coverage criteria. We will follow the Knowledge Discovery in Database process using machine learning algorithms to estimate the prime path coverage at the method and class level. For this purpose, we will create two large datasets consisting of source code metrics and test case metrics from 12 open-source Java projects, and these datasets will be used in the training process to build the predictive models. Using the built models, we expected to predict the prime path coverage at the method and class level with a reliable prediction performance.


Author(s):  
DIANXIANG XU ◽  
WEIFENG XU ◽  
W. ERIC WONG

The new constructs in aspect-oriented programming bring new types of programming faults with respect to crosscutting concerns, such as incorrect pointcuts and advice. This paper presents a UML-based approach to testing whether or not an aspect-oriented program conforms to its expected crosscutting behavior. We explore aspect-oriented UML design models to derive tests for exercising interactions between aspects and classes. Each aspect-oriented model consists of class diagrams, aspect diagrams, and sequence diagrams. For a method under test, we weave the sequence diagrams of the advice on the method into the method's sequence diagram. Based on the woven sequence diagram and class/aspect diagrams, we then generate an AOF (Aspect-Object Flow) tree by applying coverage criteria such as condition coverage, polymorphic coverage, and loop coverage to woven sequence diagrams. In the AOF tree, each path from the root to a leaf is an abstract message sequence, indicating a template of test cases. A concrete test case is obtained by creating objects that satisfy the collective constraints in the template. Our empirical study shows that the model-based testing approach is capable of revealing several types of aspect-specific faults, including incorrect advice type, incorrect (weaker or stronger) pointcut strengths, and incorrect aspect precedence.


Sign in / Sign up

Export Citation Format

Share Document