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

Abstract

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.

Family-Based Model Checking with mCRL2

“…Then we define a partitioning procedure for μL f that allows us to apply our results from [20]. Next, we evaluate our approach by verifying a number of representative properties over an mCRL2 specification of the minepump SPL benchmark model [8,13,[23][24][25]. We verify typical lineartime and branching-time properties.…”

Perspectives on White-Box Testing: Coverage, Concurrency, and Concolic Execution

“…We implemented this approach in the testinput generator CPA/TIGER [16]. Recently, CPA/TIGER was extended to support software-product line testing [17].…”

PYFML - A Textual Language for Feature Modeling

“…A software product line (SPL) is considered as a set of products that all shared a lot of characteristics and vary in their particular configuration of variability, portfolios of very similar products are developed to get lower product cost, faster development cycles, and better quality [1], while Software product line engineering (SPLE) means to develop up a group of similar software products where commonality and variability among the family members (product variations) are explicitly determined by features where each feature is a visible characteristic of product in SPL related to product configuration [2]. Modeling variability is an essential in SPLE and a typical approach of the variability is called feature modeling and presents feature models as feature diagrams and the graphical notations is the most popular type of representation for feature diagrams [2], [3], particularly it encourages analysis to present a graphical language for these feature diagrams and associate it with formal representation considered as a base for building software engineering tool.…”