Abstract
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.
This is a preview of subscription content, log in via an institution to check access.
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
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)
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)
Sepulveda, C.: XP and Customer Tests: Is It Fair? Online: http://christiansepulveda.com/blog/archives/cat_software_development.html
Author information
Authors and Affiliations
Editor information
Rights and permissions
Copyright information
© 2007 Springer Berlin Heidelberg
About this paper
Cite this paper
Melnik, G., Maurer, F. (2007). Multiple Perspectives on Executable Acceptance Test-Driven Development. In: Concas, G., Damiani, E., Scotto, M., Succi, G. (eds) Agile Processes in Software Engineering and Extreme Programming. XP 2007. Lecture Notes in Computer Science, vol 4536. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-73101-6_46
Download citation
DOI: https://doi.org/10.1007/978-3-540-73101-6_46
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-73100-9
Online ISBN: 978-3-540-73101-6
eBook Packages: Computer ScienceComputer Science (R0)