2008
DOI: 10.1007/978-3-540-87603-8_13
|View full text |Cite
|
Sign up to set email alerts
|

Combining Scenario- and Model-Based Testing to Ensure POSIX Compliance

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2011
2011
2015
2015

Publication Types

Select...
4
2

Relationship

1
5

Authors

Journals

citations
Cited by 8 publications
(3 citation statements)
references
References 13 publications
0
3
0
Order By: Relevance
“…This work is an extension of a previous combination of scenario-and model-based testing approaches, initially designed for B machines [8], [9] and now adapted to the objectoriented paradigm. Nevertheless, contrary to these approaches, our underlying technology is not a symbolic animation that would make it possible to abstract operation parameter values, but a fully-instantiated model animator that requires operation parameters to be instantiated before animation.…”
Section: Related Workmentioning
confidence: 98%
“…This work is an extension of a previous combination of scenario-and model-based testing approaches, initially designed for B machines [8], [9] and now adapted to the objectoriented paradigm. Nevertheless, contrary to these approaches, our underlying technology is not a symbolic animation that would make it possible to abstract operation parameter values, but a fully-instantiated model animator that requires operation parameters to be instantiated before animation.…”
Section: Related Workmentioning
confidence: 98%
“…Model-based test and oracle generation [50], [78] can aid conformance, and has been applied to POSIX file systems [25] and to other POSIX aspects [32]. This work generates tests to validate library behavior and is complementary to CheckAPI, which finds violations at runtime.…”
Section: Static Analysismentioning
confidence: 99%
“…Another experimentation has been conducted on a model of the POSIX standard for filesystems . The model, designed in a single B machine of 1500 lines of B code, contains 16 operations that make it possible to manage a filesystem, such as create files/directories, change working directory, write into/read from files, and so on.…”
Section: Case Study Evaluationmentioning
confidence: 99%