2011
DOI: 10.1007/s11219-011-9160-9
|View full text |Cite
|
Sign up to set email alerts
|

Pairwise testing for software product lines: comparison of two approaches

Abstract: Software Product Lines (SPL) are difficult to validate due to combinatorics induced by variability, which in turn leads to combinatorial explosion of the number of derivable products. Exhaustive testing in such a large products space is hardly feasible. Hence, one possible option is to test SPLs by generating test configurations that cover all possible t feature interactions (t-wise). It dramatically reduces the number of test products while ensuring reasonable SPL coverage. In this paper, we report our experi… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

2
88
0

Year Published

2011
2011
2022
2022

Publication Types

Select...
4
4

Relationship

0
8

Authors

Journals

citations
Cited by 95 publications
(90 citation statements)
references
References 48 publications
2
88
0
Order By: Relevance
“…Just to mention a few, there are works using multi-objective approaches [56,34,47,29,30] for test selection, while some others explore t-wise testing [24,49,50,48]. Although out of the scope of this work, FLAME could also be used to formalize these new operations.…”
Section: Related Workmentioning
confidence: 99%
“…Just to mention a few, there are works using multi-objective approaches [56,34,47,29,30] for test selection, while some others explore t-wise testing [24,49,50,48]. Although out of the scope of this work, FLAME could also be used to formalize these new operations.…”
Section: Related Workmentioning
confidence: 99%
“…Moreover, the tasks in the two invariants are not required to be different in the generated model, hence we obtain a model with two tasks instead of three. In the MDE community, pairwise testing is being successfully used for software product line testing [39,40], considering pairs of features in a feature model. In our case, there are additional challenges, because our specifications do not explicitly encode dependencies between their requirements, and the model generation procedure has to consider the constraints given by the input meta-model and preconditions as well.…”
Section: Coverage Criteria For Input Model Generationmentioning
confidence: 99%
“…In the MDE community, pairwise testing is being successfully used for software product line testing [19,20], considering pairs of features in a feature model. In our case there are additional challenges, because our specifications do not explicitly encode dependencies between their requirements, and the model generation procedure has to consider the constraints given by the input meta-model and preconditions.…”
Section: Input Model Generation For Different Coverage Criteriamentioning
confidence: 99%