Extensional equivalence for transition systems
Acta Informatica
Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering
Component-based Software Testing With Uml
Component-based Software Testing With Uml
International Journal on Software Tools for Technology Transfer (STTT) - Special section on high-level test of complex systems
Testing software components for integration: a survey of issues and techniques: Research Articles
Software Testing, Verification & Reliability
A symbolic framework for model-based testing
FATES'06/RV'06 Proceedings of the First combined international conference on Formal Approaches to Software Testing and Runtime Verification
Audition of web services for testing conformance to open specified protocols
Proceedings of the 2004 international conference on Architecting Systems with Trustworthy Components
Model-Based Generation of Testbeds for Web Services
TestCom '08 / FATES '08 Proceedings of the 20th IFIP TC 6/WG 6.1 international conference on Testing of Software and Communicating Systems: 8th International Workshop
The PLASTIC Framework and Tools for Testing Service-Oriented Applications
Software Engineering
Model-Based Testing 2010: Short Abstracts
Electronic Notes in Theoretical Computer Science (ENTCS)
Towards quality of model-based testing in the ioco framework
Proceedings of the 2013 International Workshop on Joining AcadeMiA and Industry Contributions to testing Automation
Hi-index | 0.00 |
In component-based development, the correctness of a system depends on the correctness of the individual components and on their interactions. Model-based testing is a way of checking the correctness of a component by means of executing test cases that are systematically generated from a model of the component. This model should include the behaviour of how the component can be invoked, as well as how the component itself invokes other components. In many situations, however, only a model that specifies how others can use the component, is available. In this paper we present an approach for model-based testing of components where only these available models are used. Test cases for testing whether a component correctly reacts to invocations are generated from this model, whereas the test cases for testing whether a component correctly invokes other components, are generated from the models of these other components. A formal elaboration is given in the realm of labelled transition systems. This includes an implementation relation, called eco, which formally defines when a component is correct with respect to the components it uses, and a sound and exhaustive test generation algorithm for eco.