Reasoning About Software Architecture-Based Regression Testing Through a Case Study

Muccini, Henry; Dias, Marcio S.; Richardson, Debra J.

doi:10.1109/compsac.2005.127

Cited by 10 publications

(7 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…UML-based models also have been considered by Dent et al [107], Pilskalns et al [108] and Farooq et al [109] for RTS; Le Traon et al [110] and Wu and Offutt [111] considered the use of UML models in the wider context of regression testing in general. Muccini et al considered the RTS problem at the software architecture level, although they did not use UML for the representation [112,113].…”

Section: Design-based Approachmentioning

confidence: 99%

Regression testing minimization, selection and prioritization: a survey

Yoo¹,

Harman²

2012

Softw. Test. Verif. Reliab.

1,058

594

View full text Add to dashboard Cite

Regression testing is a testing activity that is performed to provide confidence that changes do not harm the existing behaviour of the software. Test suites tend to grow in size as software evolves, often making it too costly to execute entire test suites. A number of different approaches have been studied to maximize the value of the accrued test suite: minimization, selection and prioritization. Test suite minimization seeks to eliminate redundant test cases in order to reduce the number of tests to run. Test case selection seeks to identify the test cases that are relevant to some set of recent changes. Test case prioritization seeks to order test cases in such a way that early fault detection is maximized. This paper surveys each area of minimization, selection and prioritization technique and discusses open problems and potential directions for future research.This survey aims to collect and consider papers that deal with three regression testing techniques: test suite minimization, RTS and test case prioritization. Our intention is not to undertake a systematic review, but rather to provide a broad state-of-the-art view on these related fields. Many different approaches have been proposed to aid regression testing, which has resulted in a body of literature that is spread over a wide variety of domains and publication venues. The majority of surveyed literature has been published in the software engineering domain, and especially in the software testing and software maintenance literature. However, the regression testing literature also overlaps with those of programming language analysis, empirical software engineering and software metrics.Therefore, the paper selection criteria on which this survey is based are the problems considered in papers, while focusing on the specific topics of minimization, selection and prioritization. The formal definitions of these problems are presented in Section 2.2. The selected papers are listed in the Appendix. Fast abstracts and short papers have been excluded. BACKGROUNDThis section introduces the basic concepts and definitions that form a nomenclature of regression testing and minimization, selection and prioritization techniques. Definition 1 (Test Suite Minimization Problem)Given: A test suite, T , a set of test requirements {r 1 , . . .,r n }, that must be satisfied to provide the desired 'adequate' testing of the program, and subsets of T , T 1 , . . ., T n , one associated with each of the r i s such that any one of the test cases t j belonging to T i can be used to achieve requirement r i .Problem: Find a representative set, T , of test cases from T that satisfies all r i s.The testing criterion is satisfied when every test requirement in {r 1 , . . .,r n } is satisfied. A test requirement, r i , is satisfied by any test case, t j , that belongs to the T i , a subset of T . Therefore, the representative set of test cases is the hitting set of the T i s. Furthermore, in order to maximize the effect of minimization, T should be the minimal hitting set of the T i ...

show abstract

Section: Design-based Approachmentioning

confidence: 99%

Regression testing minimization, selection and prioritization: a survey

Yoo¹,

Harman²

2012

Softw. Test. Verif. Reliab.

1,058

594

View full text Add to dashboard Cite

show abstract

“…In other related work such as [10,17,33], no evaluation is reported. Only [22] in a recent study used a larger model: a labeled transition system with 80 states and 244 transitions. More experiments are definitely required to evaluate these different alternative model-based strategies.…”

Section: Case Studiesmentioning

confidence: 99%

“…In [10] a model (UML-like) based regression test selection strategy is also succinctly described and there are not enough details available for us to really compare it with our approach. In [22,23] the architecture of a software system, comprising structural (topological) and behavioral (labeled transition system) models (these are not UML models though), is used to perform regression test selection. The labeled transition systems are combined with structural information to build graphs (unfortunately, not much details are provided on that aspect) and existing code-based regression test selection algorithms are used.…”

Section: Further Related Workmentioning

confidence: 99%

Automating regression test selection based on UML designs

Briand

Labiche

2009

Information and Software Technology

100

View full text Add to dashboard Cite

“…All old test cases should be re-run to ensure that original functions are correct during this process. But there is the trade-off between the re-run time and the fault detection ability [15][16][17]. To resolve this issue we have developed the tool, TASTE (Tool for Automatic Software regression TEsting), to be complete in both respects.…”

Section: Tastementioning

confidence: 99%

A Study of Enhanced MC/DC Coverage Criterion for Software Testing

Chang

Huang

2007

31st Annual International Computer Software and Applications Conference - Vol. 1- (COMPSAC 2007)

View full text Add to dashboard Cite

The coverage criteria of verification techniques play an important role in software development and testing. The goal is to reduce the size of test suites to economize on time, and to ensure whether all statements (or conditions) are covered. We can use these criteria to track test progress, assess current situations, predict emerging events, and so on. Thus we can take the necessary actions upon early indications that testing activity is falling behind. Modified condition/decision coverage

show abstract

Reasoning About Software Architecture-Based Regression Testing Through a Case Study

Cited by 10 publications

References 18 publications

Regression testing minimization, selection and prioritization: a survey

Regression testing minimization, selection and prioritization: a survey

Automating regression test selection based on UML designs

A Study of Enhanced MC/DC Coverage Criterion for Software Testing

Contact Info

Product

Resources

About