Model-Based Testing in Practice
By Alexander Pretschner. World Congress on Formal Methods, 2005
380 citations recorded by the source corpus.
Subfields: Information Systems, Software
View Paper: https://www.semanticscholar.org/paper/98c376ec2dcd586dccb452a5442995a0212e2cd7
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Information Systems
- Charles J. Colbourn
- Myra B. Cohen
- Cemal Yilmaz
- Adam A. Porter
- Mark Utting
- Bruno Legeard
- A. C. Dias Neto
- Guilherme Horta Travassos
In Software
- Charles J. Colbourn
- Myra B. Cohen
- Mark Utting
- Bruno Legeard
- Adam A. Porter
- Cemal Yilmaz
- A. C. Dias Neto
- Guilherme Horta Travassos
Citations in the corpus
- A survey on model-based testing approaches: a systematic review (2007, methodology): “From a review of the main characteristics of MBT approaches, [1], [2], etc. and academic and industry experience reports, fourteen fields (Table 2) were identified for extracting information from the selected papers.”
- Combinatorial aspects of covering arrays (2006, background): “present empirical results to argue that the testing of all pairwise interactions in a software system finds a large percentage of the existing faults [45].”
- A taxonomy of model‐based testing approaches (2012, methodology): “Moreover, while the paper contains an overview of the process of MBT (see Section 2), it deliberately does not discuss the empirical evidence for the effectiveness of MBT or its limitations, since this has been done elsewhere [ 6, Chapter 2 ] ; see also References [ 7–14 ] .”
- Software fault interactions and implications for software testing (2004, background): “This study was extremely limited in that only one screen of a subsystem with two known faults was involved, but pairwise testing was sufficient to detect both faults.”
- Covering arrays for efficient fault characterization in complex configuration spaces (2004, methodology): “[8] argue that the testing of all pairwise interactions in a software system finds a large percentage of the existing faults.”
- Robustness Testing of Autonomy Software (2017, background): “Statefulness has been introduced using model-based testing [10, 39], which attempts to generate tests based on a model of the functional requirements.”