In software product family engineering reusable artifacts are produced during domain engineering and applications are built from these artifacts during application engineering. Modeling variability of current and future applications is the key for enabling reuse. The proactive reuse leads to a reduction in development costs and a shorter time to market. Up to now, these benefits have been realized for the constructive development phases, but not for testing. This paper presents the ScenTED technique (Scenario based TEst case Derivation), which aims at reducing effort in product family testing. ScenTED is a model-based, reuse-oriented technique for test case derivation in the system test of software product families. Reuse of test cases is ensured by preserving variability during test case derivation. Thus, concepts known from model-based testing in single system engineering, e.g., coverage metrics, must be adapted. Experiences with our technique gained from an industrial case study are discussed and prototypical tool support is illustrated.
No abstract
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...
Zusammenfassung In der Produktfamilienentwicklung werden durch zwei Entwicklungsprozesse, Domain und Application Engineering, zunächst wiederverwendbare Entwicklungsartefakte produziert, um diese anschließend zur Konstruktion von kundenspezifischen Applikationen einzusetzen. Die Wiederverwendbarkeit wird durch die explizite Definition der Variabilität der geplanten Applikationen einer Produktfamilie erzielt. Diese proaktive Wiederverwendung ist bisher in den konstruktiven Entwicklungsphasen realisiert, jedoch noch nicht im Test. Mit ScenTED (Scenario based TEst Case Derivation) wird in diesem Beitrag eine wiederverwendungsorientierte Technik zur Testfallerstellung für den Systemtest, dem Test eines ausführbaren Systems gegen spezifizierte Use-Cases, von Produktfamilien vorgestellt. ScenTED basiert auf zwei Kernideen: der Erhaltung der Variabilität in Testfällen und der Szenario-basierten Verfeinerung der Testfälle. Durch die Erhaltung der Variabilität wird die Wiederverwendbarkeit von Testfällen gesichert; die Szenario-basierte Verfeinerung ermöglicht Nachvollziehbarkeit durch die durchgängige Nutzung von Szenarien. In diesem Beitrag wird die ScenTED-Technik an einem Beispiel erläutert und Erfahrungen aus dem industriellen Einsatz diskutiert.Schlüsselwörter Produktfamilien · Testen · Wiederverwendung · Use-Case Abstract Product family engineering consists of two development processes: Domain engineering and application engineering. Reuseable artefacts are created in the domain engineering process. These artefacts are used for the creation Diese Arbeit wurde gefördert durch das BMBF Verbundprojekt CAFÉ "From Concept to Application in System Family Engineering" (För-derkennzeichen 01 IS 002 C) und dem Europäischen ITEA Projekt FAMILIES "FAct-based Maturity through Institutionalisation Lessonslearned and Involved Exploration of System-family engineering", Eureka ! 2023 Programme, ITEA Projekt ip02009. of customer specific applications during the application engineering process. Reusability is achieved with the explicit definition of variability that specifies the potential applications of the product family. The proactive reuse has been realized in the construnction phases of the development process, but not within the test phases. We propose ScenTED (Scenario based TEst Case Derivation) for the creation of reusable test cases for a use case based system testing in product family engineering. ScenTED has two key ideas: The first is the preservation of variability in test cases and the second idea is the scenario-based refinement of test cases. The preservation of variability ensures the reusability of test cases. The scenario-based refinement enables the traceability from requirements to test cases. We present the ScenTED technique in this article with an example and discuss an industrial case study.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.
hi@scite.ai
10624 S. Eastern Ave., Ste. A-614
Henderson, NV 89052, USA
Copyright © 2024 scite LLC. All rights reserved.
Made with 💙 for researchers
Part of the Research Solutions Family.