A systematic mapping study of software product lines testing

Neto, Paulo Anselmo da Mota Silveira; Machado, Ivan; McGregor, John D.; Almeida, Eduardo Santana de; Meira, Sílvio Romero de Lemos

doi:10.1016/j.infsof.2010.12.003

Cited by 196 publications

(89 citation statements)

References 58 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In addition, knowledge body from several studies in different areas, such as Barney et al (2012;Neto et al, 2011;Mohabbati et al, 2013;Novais et al, 2013), served as a basis to provide directions on how to conduct this SM.…”

Section: The Search Processmentioning

confidence: 99%

Defect Types and Software Inspection Techniques: A Systematic Mapping Study

OliveiraJr¹,

Geraldi²

2017

Journal of Computer Science

View full text Add to dashboard Cite

Software inspection has been used to guarantee and control the quality of products by detecting defects, which can be spread out throughout the entire software life cycle. Therefore, the main premise is to identify and reduce the number of defect types in software artifacts during inspections. This work focuses on providing an up to dated overview of existing defects in the context of software inspection techniques. A systematic mapping was carried out, from which 2096 primary studies were retrieved and 32 were final selected. From the analysis, classification and aggregation of the retrieved studies, important different defect types were identified. Most studies encompass defect types by means of experiments and proposed techniques and approaches. Thus, as a main result, the identification of several different studies with distinct proposals concerned on defect types is evident. Although researchers have conducted studies over time, a general pattern on the detection of defects could not be established. Therefore, the scenario in which this study was carried out provides researchers with the capability of conducting further research in a motivating and challenging research topic, as well as practitioners with the adoption of empirically evaluated inspection techniques and respective defect types.

show abstract

Section: The Search Processmentioning

confidence: 99%

Defect Types and Software Inspection Techniques: A Systematic Mapping Study

OliveiraJr¹,

Geraldi²

2017

Journal of Computer Science

View full text Add to dashboard Cite

show abstract

“…Various surveys deal with testing in SPLs; e.g., [16,30,25,8]. Delta tables leverage the idea of tabular notation to the specification of product lines.…”

Section: Related Workmentioning

confidence: 99%

A novel model-based testing approach for software product lines

et al. 2016

View full text Add to dashboard Cite

A novel model-based testing approach for software product lines / Damiani, Ferruccio; Faitelson, David; Gladisch, Christoph; Tyszberowicz, Shmuel. -In: SOFTWARE AND SYSTEMS MODELING. -ISSN 1619-ISSN -1366-ISSN . -14:4(2017, pp. 1223-1251. Original Citation:A novel model-based testing approach for software product lines Abstract Model-based testing relies on a model of the system under test. FineFit is a framework for model-based testing of Java programs. In the FineFit approach, the model is expressed by a set of tables based on Parnas tables. A software product line is a family of programs (the products) with well-defined commonalities and variabilities that are developed by (re)using common artifacts. In this paper we address the issue of using the FineFit approach to support the development of correct software product lines. We specify a software product line as a specification product line where each product is a FineFit specification of the corresponding software product. The main challenge is to concisely specify the software product line while retaining the readability of the specification of a single system. To address this we used delta-oriented programming, a recently proposed flexible approach for implementing software product lines, and developed: (i) delta-tables as a means to apply the delta-oriented programming idea to the specification of software product lines; and (ii) DeltaFineFit as a novel model-based testing approach for software product lines.

show abstract

“…An earlier mapping study (Engstrom and Runeson, 2011) highlighted that one of the main challenge in SPL testing is the large number of tests. Reuse of test assets by considering commonalities perceived as one way to enable test effort reduction, but da Mota Silveira Neto et al (2011) highlighted that there was no general solution that deals with systematic reuse in SPL testing. Generally, based on current evidences, this review suggests that CIT is a plausible approach to minimize the redundancy of test assets.…”

Section: Related Workmentioning

confidence: 99%

Combinatorial Interaction Testing of Software Product Lines: A Mapping Study

Sahid¹,

Sultan²,

Ghani³

et al. 2016

Journal of Computer Science

View full text Add to dashboard Cite

Software Product Line (SPL) is a software engineering paradigm that is inspired by the concept of reusability of common features, formulated for different software product. Complete testing on entire SPL is known to be unfeasible, due to the very large number of possible products to be produced, configured using a subset or all possible features in the SPL. This paper reports a Systematic Mapping Study (SMS) of relevant primary studies as the evidence on the application of Combinatorial Interaction Testing (CIT) for SPL. In CIT, one has to construct a covering array, which is a set of configurations having valid feature combinations and every combination of t features appears at least once in the array. This is also known as t-wise testing. By following the systematic mapping study guidelines, we have selected and filtered 44 primary studies for review. The most prominent CIT techniques in aiding SPL testing are those based on greedy algorithms followed by meta-heuristics algorithms. The motivation of SPL testing is to anticipate the feature interaction problem, in which the majority of the works were reported to leverage test configuration selection approach, while some employed test configuration prioritization approach. Numerous works have been reported, but only few works managed to demonstrate their scalability, as most primary studies only deal with low strength (t is less than 4) of t-wise testing.

show abstract

A systematic mapping study of software product lines testing

Cited by 196 publications

References 58 publications

Defect Types and Software Inspection Techniques: A Systematic Mapping Study

Defect Types and Software Inspection Techniques: A Systematic Mapping Study

A novel model-based testing approach for software product lines

Combinatorial Interaction Testing of Software Product Lines: A Mapping Study

Contact Info

Product

Resources

About