scispace - formally typeset
Journal ArticleDOI

Practical Combinatorial Testing: Beyond Pairwise

Reads0
Chats0
TLDR
This review focuses on real-world problems and empirical results from applying freely available methods and tools for constructing large t-way combination test sets, converting covering arrays into executable tests, and automatically generating test oracles using model checking.
Abstract
With new algorithms and tools, developers can apply high-strength combinatorial testing to detect elusive failures that occur only when multiple components interact. In pairwise testing, all possible pairs of parameter values are covered by at least one test, and good tools are available to generate arrays with the value pairs. In the past few years, advances in covering-array algorithms, integrated with model checking or other testing approaches, have made it practical to extend combinatorial testing beyond pairwise tests. The US National Institute of Standards and Technology (NIST) and the University of Texas, Arlington, are now distributing freely available methods and tools for constructing large t-way combination test sets (known as covering arrays), converting covering arrays into executable tests, and automatically generating test oracles using model checking (http://csrc.nist.gov/acts). In this review, we focus on real-world problems and empirical results from applying these methods and tools.

read more

Citations
More filters
Journal ArticleDOI

Bypassing the Combinatorial Explosion: Using Similarity to Generate and Prioritize T-Wise Test Configurations for Software Product Lines

TL;DR: A search-based approach capable of generating product configurations for large SPLs, forming a scalable and flexible alternative to current techniques and a prioritization algorithms for any set of product configurations, which employ a similarity heuristic.
Journal ArticleDOI

A systematic mapping study of mobile application testing techniques

TL;DR: A systematic mapping study to categorize and to structure the research evidence that has been published in the area of mobile application testing techniques and challenges that they have reported and specific key testing issues for practitioners are identified.
Proceedings ArticleDOI

Cost-Efficient Sampling for Performance Prediction of Configurable Systems (T)

TL;DR: This paper adapt two widely-used sampling strategies for performance prediction to the domain of configurable systems and evaluate them in terms of sampling cost, which considers prediction accuracy and measurement effort simultaneously.
Journal ArticleDOI

Pairwise testing for software product lines: comparison of two approaches

TL;DR: This paper reports the experience on applying t-wise techniques for SPL with two independent toolsets developed by the authors, and derives useful insights for pairwise and t- Wise testing of product lines.
Book ChapterDOI

Graduate Theses and Dissertations

TL;DR: To establish a time line and to work on writing the thesis throughout the graduate program will relieve some pressure at the end of the program and to publish at least a part of the thesis, usually as a journal article.
References
More filters
Journal ArticleDOI

Software fault interactions and implications for software testing

TL;DR: It is shown that software failures in a variety of domains were caused by combinations of relatively few conditions, which has important implications for testing.
Book

Fuzzing: Brute Force Vulnerability Discovery

TL;DR: Piezoelectric crystalline films which consist essentially of a crystalline zinc oxide film with a c-axis perpendicular to a substrate surface, containing 0.01 to 20.0 atomic percent of bismuth.
Book ChapterDOI

JML: A Notation for Detailed Design

TL;DR: JML is a behavioral interface specification language tailored to Java that uses Eiffel-style syntax combined with model-based semantics, as in VDM and Larch, and supports quantifiers, specification-only variables, and other enhancements that make it more expressive for specification and easier to use.
Proceedings ArticleDOI

Pseudo-Exhaustive Testing for Software

TL;DR: Pseudo-exhaustive testing uses the empirical observation that, for broad classes of software, a fault is likely triggered by only a few variables interacting to take advantage of two relatively recent advances in software engineering.
Journal ArticleDOI

The density algorithm for pairwise interaction testing

TL;DR: A new algorithm is established that efficient, greedy, one‐test‐at‐a‐time methods can indeed produce a logarithmic worst‐case guarantee on the test suite size and can be done while still producing test suites that are of competitive size, and in a time that is comparable to the published methods.
Related Papers (5)