Extreme programming explained: embrace change
Extreme programming explained: embrace change
Test Driven Development: By Example
Test Driven Development: By Example
Domain-Driven Design: Tacking Complexity In the Heart of Software
Domain-Driven Design: Tacking Complexity In the Heart of Software
Fit for Developing Software: Framework for Integrated Tests (Robert C. Martin)
Fit for Developing Software: Framework for Integrated Tests (Robert C. Martin)
ADC '05 Proceedings of the Agile Development Conference
The role of blogging in generating a software product vision
CHASE '09 Proceedings of the 2009 ICSE Workshop on Cooperative and Human Aspects on Software Engineering
UI-driven test-first development of interactive systems
Proceedings of the 3rd ACM SIGCHI symposium on Engineering interactive computing systems
Proceedings of the 2013 International Workshop on Joining AcadeMiA and Industry Contributions to testing Automation
| Hi-index | 0.00 |
An explanation of test-driven development often begins by describing the red-green-refactor cycle. This slogan is so catchy and the description so simple that practitioners and tool developers tend to focus only on this localized cycle. Experience has shown that a successful functional test-driven development strategy must span the entire application life cycle and must be supported by effective tools. This article is a call to improve the state of the art of functional test-driven development by reflecting on the state of the art, describing processes and phases in the full application life cycle, and painting a vision for the next generation of functional testing tools.This article is part of a special issue on test-driven development.