Testing a Software Product Line

McGregor, John D.

doi:10.21236/ada401736

Cited by 103 publications

(133 citation statements)

References 0 publications

Supporting

Mentioning

128

Contrasting

Unclassified

Order By: Relevance

“…For SPLs to obtain full acceptance in practice, established quality-assurance techniques have to be lifted to become variability-aware as well, to also benefit from reuse principles [24,26,27]. Various promising attempts have been proposed, enhancing respective model-checking and software-testing techniques to efficiently verify entire families of software products instead of every single variant [4,12,14,16].…”

Section: Introductionmentioning

confidence: 99%

“…This is even worse when generating test inputs for covering entire product-line implementations. To avoid product-by-product (re-)generation of test cases with many redundant generation runs, a family-based test-generation approach must enhance test-suite-derivation techniques to be likewise applicable to product-line implementations [12,24].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Facilitating Reuse in Multi-goal Test-Suite Generation for Software Product Lines

Bürdek

Lochau

Bauregger

et al. 2015

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Abstract. Software testing is still the most established and scalable quality-assurance technique in practice. However, generating effective test suites remains computationally expensive, consisting of repetitive reachability analyses for multiple test goals according to a coverage criterion. This situation is even worse when testing entire software product lines, i.e., families of similar program variants, requiring a sufficient coverage of all derivable program variants. Instead of considering every product variant one-by-one, family-based approaches are variabilityaware analysis techniques in that they systematically explore similarities among the different variants. Based on this principle, we present a novel approach for automated product-line test-suite generation incorporating extensive reuse of reachability information among test cases derived for different test goals and/or program variants. We present a tool implementation on top of CPA/tiger which is based on CPAchecker, and provide evaluation results obtained from various experiments, revealing a considerable increase in efficiency compared to existing techniques.

show abstract

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Facilitating Reuse in Multi-goal Test-Suite Generation for Software Product Lines

Bürdek

Lochau

Bauregger

et al. 2015

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

show abstract

“…A large body of research on SPL engineering has focused on reuse of core program assets [4,15,17], refined feature modeling [8,9,23], and code generation techniques [2,7]. There has also been research on testing software product lines [3,6,10,24].…”

Section: Introductionmentioning

confidence: 99%

Improving the Testing and Testability of Software Product Lines

Cabral

Cohen

Rothermel

2010

Software Product Lines: Going Beyond

View full text Add to dashboard Cite

Abstract. Software Product Line (SPL) engineering offers several advantages in the development of families of software products. There is still a need, however, for better understanding of testability issues and for testing techniques that can operate cost-effectively on SPLs. In this paper we consider these testability issues and highlight some differences between optional versus alternative features. We then provide a graph based testing approach called the FIG Basis Path method that selects products and features for testing based on a feature dependency graph. We conduct a case study on several non-trivial SPLs and show that for these subjects, the FIG Basis Path method is as effective as testing all products, but tests no more than 24% of the products in the SPL.

show abstract

“…Representatives are approaches by Bertolino and Gnesi [4][15], Geppert et al [10], McGregor et al [17][18], and Nebut et al [20]. These approaches focus on unit and system testing only.…”

Section: Related Workmentioning

confidence: 99%

“…In our previous work, we have developed the ScenTED technique for system testing [24][15] and performance testing [23]. McGregor focused on unit [18] and system testing [17], but furthermore he pointed out that all common artifacts can already be tested in domain engineering by integration tests. However, he did not present a concrete technique for that.…”

Section: Related Workmentioning

confidence: 99%

Integration Testing in Software Product Line Engineering: A Model-Based Technique

Reis

Metzger

Pohl

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. The development process in software product line engineering is divided into domain engineering and application engineering. As a consequence of this division, tests should be performed in both processes. However, existing testing techniques for single systems cannot be applied during domain engineering, because of the variability in the domain artifacts. Existing software product line test techniques only cover unit and system tests. Our contribution is a model-based, automated integration test technique that can be applied during domain engineering. For generating integration test case scenarios, the technique abstracts from variability and assumes that placeholders are created for variability. The generated scenarios cover all interactions between the integrated components, which are specified in a test model. Additionally, the technique reduces the effort for creating placeholders by minimizing the number of placeholders needed to execute the integration test case scenarios. We have experimentally measured the performance of the technique and the potential reduction of placeholders. MotivationSoftware product line engineering (SPLE) is a proven approach for deriving a set of similar applications at low costs and at short time to market [8] [21]. SPLE is based on the planned, systematic, and pro-active reuse of development artifacts (including requirements, components, and test cases). There are two key differences between SPLE and the development of single systems [21]:1. The development process of a software product line (SPL) is divided into two sub processes: domain engineering and application engineering. In domain engineering, the commonalities and the variability of the SPL are defined and reusable artifacts, which comprise the SPL platform, are created. In application engineering, customer-specific applications are realized by binding the variability and reusing the domain artifacts. Because of the division of the development process into domain and application engineering, there are two major kinds of development artifacts that have to be tested. In domain engineering, the SPL platform has to be tested, in application engineering the derived applications have to be tested.The SPL platform contains variability. This variability prevents the use of existing testing techniques for single systems, because the domain artifacts do not define a single application but a set of applications. With existing techniques from single system testing, each of these applications would have to be individually tested in domain engineering, resulting in an enormous test effort.In the literature, several approaches for SPL testing have been proposed (e.g.,). However, these approaches cover unit and system testing only.This paper presents a model-based, automated technique for integration testing in domain engineering. Our technique generates integration test case scenarios (ITCSs), which support the test of the interactions between the components of an integrated sub-system. An ITCS describes the order and the t...

show abstract

Testing a Software Product Line

Cited by 103 publications

References 0 publications

Facilitating Reuse in Multi-goal Test-Suite Generation for Software Product Lines

Facilitating Reuse in Multi-goal Test-Suite Generation for Software Product Lines

Improving the Testing and Testability of Software Product Lines

Integration Testing in Software Product Line Engineering: A Model-Based Technique

Contact Info

Product

Resources

About