Fitting agile acceptance testing into the development process

It seems a comon problem. One of the first steps in implementing an agile process (such as scrum) is to put in place a fixed iteration cycle in development, but but then find difficulties fitting post-development testing (a.k.a “system testing” or “integration”) into the mix.

The main problem with testing after development is that any fixes to problems identified in the follow-on testing have a tendency to become tangled in upcoming work for the next iteration. This in turn can lead to no iteration ever being “clean” enough to actually release.

One possibility for a solution is to reconsider the development-led nature of an iteration, and instead lead it from a set of acceptance tests which are estimated, developed and executed alongside the scheduling and implementation of code changes.

Gojko Adzic, one of my current favourite bloggers on the subject of testing, has attempted to map out an iteration structure which incorporates this approach:

Gojko Adzic ยป Fitting agile acceptance testing into the development process

Comments (1) left to “Fitting agile acceptance testing into the development process”

  1. The Punch Barrel / Automated story-based acceptance tests lead to unmaintainable systems wrote:

    [...] A fascinating counterpoint to Gojko Adzic’s writings on acceptance testing in an agile process. [...]

Post a Comment

*Required
*Required (Never published)