Proc. of the European symposium on programming on ESOP 86
Systematic software development using VDM (2nd ed.)
Systematic software development using VDM (2nd ed.)
Specification-based test oracles for reactive systems
ICSE '92 Proceedings of the 14th international conference on Software engineering
Branching time and abstraction in bisimulation semantics
Journal of the ACM (JACM)
The B-book: assigning programs to meanings
The B-book: assigning programs to meanings
Software unit test coverage and adequacy
ACM Computing Surveys (CSUR)
Model-based testing in practice
Proceedings of the 21st international conference on Software engineering
Automating the Generation and Sequencing of Test Cases from Model-Based Specifications
FME '93 Proceedings of the First International Symposium of Formal Methods Europe on Industrial-Strength Formal Methods
Generation of test sequences from formal specifications: GSM 11-11 standard case study
Software—Practice & Experience
ProTest: An Automatic Test Environment for B Specifications
Electronic Notes in Theoretical Computer Science (ENTCS)
Introducing backward refinement into B
ZB'03 Proceedings of the 3rd international conference on Formal specification and development in Z and B
Automatic refinement checking for b
ICFEM'05 Proceedings of the 7th international conference on Formal Methods and Software Engineering
Test case generation from formal models through abstraction refinement and model checking
Proceedings of the 3rd international workshop on Advances in model-based testing
Generating Tests from B Specifications and Test Purposes
ABZ '08 Proceedings of the 1st international conference on Abstract State Machines, B and Z
Combining Scenario- and Model-Based Testing to Ensure POSIX Compliance
ABZ '08 Proceedings of the 1st international conference on Abstract State Machines, B and Z
Model-Based Testing Using Scenarios and Event-B Refinements
Methods, Models and Tools for Fault Tolerance
| Hi-index | 0.00 |
When models are formal, model based testing approaches usually construct a coverage graph through symbolic execution and derive test cases in the form of paths in the coverage graph. Thereafter consistency between the model and the implementation is verified in relation to the test cases. Existing approaches, especially when dealing with model oriented languages like B, partition the input space of each operation in the model to create operation instances, and then animate the model in relation to these instances. The paths or the test cases are now a sequence of operation instances. However, in this approach, there is no guarantee that we test the user scenarios. In this paper, we first define scenario based test cases in relation to the initial specification. When this specification passes through a succession of refinements, we derive scenario based test cases for each refinement and show that all these test cases are equivalent to the test cases of the original specification.