Specification Based Testing: Towards Practice
PSI '02 Revised Papers from the 4th International Andrei Ershov Memorial Conference on Perspectives of System Informatics: Akademgorodok, Novosibirsk, Russia
Open framework for conformance testing via scenarios
Companion to the 22nd ACM SIGPLAN conference on Object-oriented programming systems and applications companion
Automated instrumentation of contracts and scenarios for requirements validation in .net
Proceedings of the 3rd international workshop on Automation of software test
An overview on test generation from functional requirements
Journal of Systems and Software
Lightweight formal methods for scenario-based software engineering
SMTT'03 Proceedings of the 2003 international conference on Scenarios: models, Transformations and Tools
| Hi-index | 0.00 |
Scenarios/Use cases have attracted much attention and gained wide- spread use in requirements and software engineering over the last couple of years. In scenarios, the functionality and behavior of a (software) system is captured in a user-centered perspective. To date, scenarios are mainly used in the requirements elicitation and analysis phase of software development. However, the use of scenarios in other phases of software development is of much interest, as it could help to cut cost by reuse and improved validation and verification. As scenarios form a kind of abstract test cases for the system under development, the idea to use them to derive test cases for system test is quite intriguing. Yet in practice, scenarios from the analysis phase are seldom used to create concrete system test cases. In this report, we present a procedure to create scenarios during the analysis phase of system development, to structure them according to a given scenario template, and to use these scenarios in the system testing phase to systematically determine test cases. This is done by formalization of natural language scenarios in statecharts, annotation of statecharts with helpful information for test case creation/generation and by path traversal in the statecharts to determine concrete test cases. Furthermore, dependencies between scenarios are captured and modeled in so-called dependency charts, and test cases are derived from dependency charts to enhance the developed test suites. The approach has been applied to two projects in industry. In this report, we also report on some of the experiences made in applying the approach in practice.