Use case maps for object-oriented systems
Use case maps for object-oriented systems
Testing object-oriented systems: models, patterns, and tools
Testing object-oriented systems: models, patterns, and tools
Java and XSLT
Test Driven Development: By Example
Test Driven Development: By Example
Going Faster: Testing The Web Application
IEEE Software
Designing and Evaluating E-Business Models
IEEE Intelligent Systems
An Object-Oriented Web Test Model for Testing Web Applications
COMPSAC '00 24th International Computer Software and Applications Conference
WWM: A Practical Methodology for Web Application Modeling
COMPSAC '02 Proceedings of the 26th International Computer Software and Applications Conference on Prolonging Software Life: Development and Redevelopment
SCENTOR: Scenario-Based Testing of E-Business Applications
WETICE '01 Proceedings of the 10th IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises
Introduction to the user requirements notation: learning by example
Computer Networks: The International Journal of Computer and Telecommunications Networking - ITU-T system design languages (SDL)
ICSM '02 Proceedings of the International Conference on Software Maintenance (ICSM'02)
Generating Scenarios from Use Case Map Specifications
QSIC '03 Proceedings of the Third International Conference on Quality Software
Generation of test purposes from Use Case Maps
Computer Networks: The International Journal of Computer and Telecommunications Networking - Telecommunications and UML languages
Test aspect of requirement specification
Computer Standards & Interfaces
Visualizing early aspects with use case maps
Transactions on aspect-oriented software development III
| Hi-index | 0.00 |
Despite their apparent simplicity, Web applications are surprisingly difficult to develop, if our aim is to build applications that behave correctly under regular conditions as well as adverse circumstances like out-of-order requests and race conditions. In this paper, we describe our experiences deriving customer-oriented acceptance tests for Web applications by modeling the essential capabilities of such applications with Use Case Maps (UCMs). Abstract test purposes are generated from a UCM model using scenario definitions and scenario extraction tools. These test purposes are then converted interactively to test cases in the FitNesse acceptance testing framework, which is popular in the Extreme Programming (XP) community. The test cases are used to validate a Web application where several typical but non-trivial bugs were planted. Challenges in the automation of the process are also discussed.