Automated Generation of Test Cases Using Model-Driven Architecture
AST '07 Proceedings of the Second International Workshop on Automation of Software Test
Towards traceability of model-based testing artifacts
Proceedings of the 3rd international workshop on Advances in model-based testing
Using traceability to support model-based regression testing
Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering
Agent-based unit testing environment for extreme programming
Journal of Computational Methods in Sciences and Engineering - Selected papers from the International Conference on Computer Science, Software Engineering, Information Technology, e-Business, and Applications, 2004
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
jSynoPSys -- A Scenario-Based Testing Tool based on the Symbolic Animation of B Machines
Electronic Notes in Theoretical Computer Science (ENTCS)
UCM-Driven testing of web applications
SDL'05 Proceedings of the 12th international conference on Model Driven
A taxonomy of model-based testing approaches
Software Testing, Verification & Reliability
Scenario-based testing using symbolic animation of B models
Software Testing, Verification & Reliability
| Hi-index | 0.00 |
E-business software is often developed on a tight schedule, and testing needs to keep pace. Advice from proponents of approaches like Extreme Programming is that by testing continuously, it is actually possible to compress development cycles. In this paper we discuss a testing approach that supports developers with their task of creating automated functional test drivers for e-business applications. The main goal for the approach is to reduce the time and effort required to automate scenario tests for e-business applications. After motivating the approach, we give an abstract view of a tool designed and implemented to support the approach. Next, we give an example of its use, and finally proceed to a discussion of the architecture of the tool itself.