Multiple Perspectives on Executable Acceptance Test-Driven Development

  • Grigori Melnik
  • Frank Maurer
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4536)

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.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Bach, J.: Exploratory Testing Explained. Online: http://www.satisfice.com/articles/et-article.pdf
  2. Fit: Framework for Integrated Test. Online: http://fit.c2.com/
  3. 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
  4. 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
  5. Sepulveda, C.: XP and Customer Tests: Is It Fair? Online: http://christiansepulveda.com/blog/archives/cat_software_development.html

Copyright information

© Springer Berlin Heidelberg 2007

Authors and Affiliations

  • Grigori Melnik
    • 1
  • Frank Maurer
    • 1
  1. 1.Department of Computer Science, University of CalgaryCanada

Personalised recommendations