The ScenTED Method for Testing Software Product Lines

Reuys, Andreas; Reis, Sacha; Kamsties, Erik; Pohl, Klaus

doi:10.1007/978-3-540-33253-4_13

Cited by 37 publications

(46 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…There is no single recommended approach available today for testing interactions between features in product lines efficiently [11], but there are many suggestions. Some of the more promising suggestions are combinatorial interaction testing [1], discussed below; a technique called ScenTED, where the idea is to express the commonalities and differences on the UML model of the product line and then derive concrete test cases by analyzing it [12]; and incremental testing, where the idea is to automatically adapt a test case from one product to the next using the specification of similarities and differences between the products [13]. Kim et al 2011 [14] presented a technique where they can identify irrelevant features for a test case using static analysis.…”

Section: Reusable Component Testingmentioning

confidence: 99%

A Technique for Agile and Automatic Interaction Testing for Product Lines

Johansen¹,

Haugen²,

Fleurey³

et al. 2012

Testing Software and Systems

View full text Add to dashboard Cite

Abstract. Product line developers must ensure that existing and new features work in all products. Adding to or changing a product line might break some of its features. In this paper, we present a technique for automatic and agile interaction testing for product lines. The technique enables developers to know if features work together with other features in a product line, and it blends well into a process of continuous integration. The technique is evaluated with two industrial applications, testing a product line of safety devices and the Eclipse IDEs. The first case shows how existing test suites are applied to the products of a 2-wise covering array to identify two interaction faults. The second case shows how over 400,000 test executions are performed on the products of a 2-wise covering array using over 40,000 existing automatic tests to identify potential interactions faults.

show abstract

Section: Reusable Component Testingmentioning

confidence: 99%

A Technique for Agile and Automatic Interaction Testing for Product Lines

Johansen¹,

Haugen²,

Fleurey³

et al. 2012

Testing Software and Systems

View full text Add to dashboard Cite

show abstract

“…In the area of product line engineering, models have been used to test application requirements derived from domain requirements [5]. The models have also been used to derive application test cases from reusable domain test cases, which have been created to verify and validate domain requirements [32].…”

Section: Human To Machine Communicationmentioning

confidence: 99%

Framework for Evaluating the Version Management Capabilities of a Class of UML Modeling Tools from the Viewpoint of Multi-Site, Multi-Partner Product Line Organizations

Koivulahti-Ojala

Käkölä

2010

2010 43rd Hawaii International Conference on System Sciences

View full text Add to dashboard Cite

UML models are widely used in software product line engineering for activities such as modeling the software product line reference architecture, detailed design, and automation of software code generation and testing. But in high-tech companies, modeling activities are typically distributed across multiple sites and involve multiple partners in different countries, thus complicating model management. Today's UML modeling tools support sophisticated version management for managing parallel and distributed modeling. However, the literature does not provide a comprehensive set of industrial-level criteria to evaluate the version management capabilities of UML tools. This article's contribution is a framework for evaluating the version management features of UML modeling tools for multi-site, multi-partner software product line organizations.

show abstract

“…As all of these notations are based on a defined formalism, they provide the possibility to inspect and analyze the use case descriptions automatically and to use these formal models in succeeding activities (e.g. test case design [Reuys06,Ryser00]). However the major drawback of using formal notations is rooted in their formality as well, since formal descriptions are difficult to understand by non-technical stakeholders.…”

Section: Related Workmentioning

confidence: 99%

Towards the Integration of UML- and textual Use Case Modeling.

Hoffmann¹,

Lichter²,

Nyßen³

2009

JOT

View full text Add to dashboard Cite

In this paper, we present a metamodel for textual use case descriptions, structurally conforming to the UML, to specify the behavior of use cases in a flow-oriented manner. While being primarily targeted at supporting requirements engineers in creating consistent use case models, the metamodel defines a textual representation of use case behavior that is easily understandable for readers, who are unaware of the underlying metamodel. Hence, the known benefits of natural language use case descriptions are preserved. Being formalized, consistency between UML-based use case representations and their textual descriptions can be automatically ensured. With NaUTiluS we present an extensible, Eclipse-based toolkit, which offers integrated UML use case modeling support, as well as editing capabilities for their textual descriptions.

show abstract

The ScenTED Method for Testing Software Product Lines

Cited by 37 publications

References 5 publications

A Technique for Agile and Automatic Interaction Testing for Product Lines

A Technique for Agile and Automatic Interaction Testing for Product Lines

Framework for Evaluating the Version Management Capabilities of a Class of UML Modeling Tools from the Viewpoint of Multi-Site, Multi-Partner Product Line Organizations

Towards the Integration of UML- and textual Use Case Modeling.

Contact Info

Product

Resources

About