Agile test composition

  • Authors:
  • Rick Mugridge;Ward Cunningham

  • Affiliations:
  • University of Auckland, New Zealand;Cunningham & Cunningham Inc, and Microsoft Corporation

  • Venue:
  • XP'05 Proceedings of the 6th international conference on Extreme Programming and Agile Processes in Software Engineering
  • Year:
  • 2005

Quantified Score

Hi-index 0.00

Visualization

Abstract

Storytests in storytest driven development serve two interrelated goals. On the one hand, they are used to formulate and communicate business rules. On the other, they are used to verify that a story has been completed and that it hasn't been subsequently broken. There is a small conflict between these views. For their communicative role, storytests are better to be concise and independent. For automated testing, speed is important in providing fast feedback, and so it makes sense to combine storytests. We show how this conflict can be avoided by automatically combining storytests. Hence the value of storytests for defining the needs of the system is not diminished when it comes to automated testing.