Multiple Perspectives on Executable Acceptance Test-Driven Development
This descriptive case study is about the dynamics of a software engineering team using executable acceptance test-driven development in a real world project. The experiences of a customer, a developer, and a tester were discussed. The observed consensus among multiple stakeholders speaks of the effectiveness of the practice in the given context.
Unable to display preview. Download preview PDF.
- Bach, J.: Exploratory Testing Explained. Online: http://www.satisfice.com/articles/et-article.pdf
- Fit: Framework for Integrated Test. Online: http://fit.c2.com/
- McDermott, P.: Zen and the Art of Systems Analysis: Meditations on Computer Systems Development, 2/e, vol. 3. Writers Club Press, Lincoln, NE (2003)Google Scholar
- Reppert, T.: Don’t Just Break Software, Make Software: How Story-Test-Driven-Development is Changing the Way QA, Customers, and Developers Work. Better Software 6(6), 18–23 (2004)Google Scholar
- Sepulveda, C.: XP and Customer Tests: Is It Fair? Online: http://christiansepulveda.com/blog/archives/cat_software_development.html