A technique for the selective revalidation of OO software

Hsia, Pei; Li, Xin; Kung, David Chenho; Hsu, Chih-Tung; Li, Liang; Toyoshima, Y.; Chen, Cris

doi:10.1002/(sici)1096-908x(199707/08)9:4<217::aid-smr152>3.0.co;2-2

Cited by 39 publications

(24 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The second loop of Algorithm 1 (lines [13][14][15][16][17][18][19][20][21][22][23][24][25] iterates through the class and activity diagram differences. In the worst case, (1) every statement is represented as a separate action node, in the activity diagram, (2) all original nodes are modified/deleted, (3) all transition flows between all nodes are modified/deleted, (4) all constructors are modified/deleted, and (5) all fields in the class diagram are modified/deleted.…”

Section: Time Complexity For the Extended Martsmentioning

confidence: 99%

See 1 more Smart Citation

Supporting inheritance hierarchy changes in model-based regression test selection

2017

View full text Add to dashboard Cite

Models can be used to ease and manage the development, evolution, and runtime adaptation of a software system. When models are adapted, the resulting models must be rigorously tested. Apart from adding new test cases, it is also important to perform regression testing to ensure that the evolution or adaptation did not break existing functionality. Since regression testing is performed with limited resources and under time constraints, regression test selection (RTS) techniques are needed to reduce the cost of regression testing. Applying modellevel RTS for model-based evolution and adaptation is more convenient than using code-level RTS because the test selection process happens at the same level of abstraction as that of evolution and adaptation.In earlier work, we proposed a model-based RTS approach called MaRTS to be used with a fine-grained model-based adaptation framework that targets applications implemented in Java. MaRTS uses UML models consisting of class and activity diagrams. It classifies test cases as obsolete, reusable, or retestable based on changes made to UML class and activity diagrams of the system being adapted. However, MaRTS did not take into account the changes made to the inheritance hierarchy in the class diagram and the impact of these changes on the selection of test cases. This paper extends MaRTS to support such changes, and demonstrates that the extended approach performs as well as or better than code-based RTS approaches in safely selecting regression test cases. While MaRTS can generally be used during any model-driven development or model-based evolution activity, we have developed it in the context of runtime adaptation. We evaluated the extended MaRTS on a set of applications, and compared the results with code-based RTS approaches that also support changes to the inheritance hierarchy. The results showed that the extended MaRTS selected all the test cases relevant to the inheritance hierarchy changes, and that the fault detection ability of the selected test cases was never lower than that of the baseline test cases. The extended MaRTS achieved comparable results to a graph-walk code-based RTS approach (DejaVu), and showed a higher reduction in the number of selected test cases when compared with a static analysis code-based RTS approach (ChEOPSJ).

show abstract

Section: Time Complexity For the Extended Martsmentioning

confidence: 99%

“…Firewall approaches [22,24,35] are based on the concept of defining the entities of the system that need to be retested, i.e., drawing a conceptual firewall around these entities. These approaches select all the test cases that exercise at least one entity from the firewall.…”

Section: Code-based Approachesmentioning

confidence: 99%

Supporting inheritance hierarchy changes in model-based regression test selection

2017

View full text Add to dashboard Cite

show abstract

“…This technique is proposed by Kung [5], Hsia [6], Abdullah and White [7] and Jang [16]. It was originally given by Leung and White [17].…”

Section: Rts Technique For Object Oriented Programs 31 Firewall Techmentioning

confidence: 99%

“…A safe-regressiontest selection selects all the test cases that contain faults in the modified software [1]. Various selection techniques have been described for procedural languages[2,3,4], object oriented languages [5,6,7] and aspect oriented languages [8,9,10]. Aspect oriented programming is a way of modularizing the crosscutting concerns and aspect-J is an implementation of aspect oriented programming as in the same way java is a way of modularizing common concerns for object oriented programming.…”

Section: Introductionmentioning

confidence: 99%

A Survey on Regression Test Selection Techniques on Aspect-Oriented Programming

Gupta¹,

Agrawal²,

Singhal³

2012

IJCA

View full text Add to dashboard Cite

An aspect oriented programming is gaining a lot of popularity these days, there is a growing interest because of crosscutting concerns in object oriented systems. When the aspect oriented features are added into object oriented features the new program needs to be regression tested, and, to reduce the cost, Selection technique is used which eliminates the redundant test cases and thus makes them cost effective. Unfortunately the already existing approaches of object oriented programming does not work out for aspect oriented programming because of the following new features of aspects such as join points ,crosscutting concerns ,aspect weaving, etc. Therefore, this paper proposes the techniques used for object oriented programs and for aspect oriented programming.

show abstract

“…Examples of these techniques are presented in [5][6][7][8][9]. Also, object oriented firewall techniques have been proposed in [10]. Extended firewalls are proposed for Object Oriented Regression Testing in [11].…”

Section: Introductionmentioning

confidence: 99%

Regression Test Selection for C# Programs

Mansour

Statieh

2009

Advances in Software Engineering

View full text Add to dashboard Cite

We present a regression test selection technique for C# programs. C# is fairly new and is often used within the Microsoft .Net framework to give programmers a solid base to develop a variety of applications. Regression testing is done after modifying a program. Regression test selection refers to selecting a suitable subset of test cases from the original test suite in order to be rerun. It aims to provide confidence that the modifications are correct and did not affect other unmodified parts of the program. The regression test selection technique presented in this paper accounts for C#.Net specific features. Our technique is based on three phases; the first phase builds an Affected Class Diagram consisting of classes that are affected by the change in the source code. The second phase builds a C# Interclass Graph (CIG) from the affected class diagram based on C# specific features. In this phase, we reduce the number of selected test cases. The third phase involves further reduction and a new metric for assigning weights to test cases for prioritizing the selected test cases. We have empirically validated the proposed technique by using case studies. The empirical results show the usefulness of the proposed regression testing technique for C#.Net programs.

show abstract

A technique for the selective revalidation of OO software

Cited by 39 publications

References 0 publications

Supporting inheritance hierarchy changes in model-based regression test selection

Supporting inheritance hierarchy changes in model-based regression test selection

A Survey on Regression Test Selection Techniques on Aspect-Oriented Programming

Regression Test Selection for C# Programs

Contact Info

Product

Resources

About