Specification directed module testing
IEEE Transactions on Software Engineering
The RAISE specification language
The RAISE specification language
Design for testability in object-oriented systems
Communications of the ACM
A Framework for Specification-Based Testing
IEEE Transactions on Software Engineering
Korat: automated testing based on Java predicates
ISSTA '02 Proceedings of the 2002 ACM SIGSOFT international symposium on Software testing and analysis
Compilation of Z Specifications into C for Automatic Test Result Evaluation
ZUM '95 Proceedings of the 9th International Conference of Z Usres on The Z Formal Specification Notation
Improving Software Tests Using Z Specifications
ZUM '95 Proceedings of the 9th International Conference of Z Usres on The Z Formal Specification Notation
Automating Test Case Generation from Z Specifications with Isabelle
ZUM '97 Proceedings of the 10th International Conference of Z Users on The Z Formal Specification Notation
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
Automated Boundary Testing from Z and B
FME '02 Proceedings of the International Symposium of Formal Methods Europe on Formal Methods - Getting IT Right
Uniform Descriptions for Model Based Testing
ASWEC '04 Proceedings of the 2004 Australian Software Engineering Conference
Model-Based Testing of Reactive Systems: Advanced Lectures (Lecture Notes in Computer Science)
Model-Based Testing of Reactive Systems: Advanced Lectures (Lecture Notes in Computer Science)
Practical Model-Based Testing: A Tools Approach
Practical Model-Based Testing: A Tools Approach
Hi-index | 0.00 |
The success of model-based testing, in automating the testing of an implementation given its state-based (or model-based) specification, raises the question of how best the specification can be tweaked in order to facilitate that process. This paper discusses several answers. Motivated by an example from web-based systems, and taking account of the restriction imposed by the testing interface, it considers both functional and non-functional properties. The former include laws, implicit system invariants and other consistency conditions whilst the latter include security leaks. It concludes that because of the importance of the link between specification and implementation in the testing process, there is a trade-off between genuinely useful testing information and the incorporation of some degree of information about the link, not normally regarded as part of the specification.