Abstract
This article describes a group of developers and how they successfully use Fitness. The study is based on interviews with 4 consultants, and shows that automated acceptance testing was used in two steps every iteration: a specification step where it helped communicate requirements, and a verification step where it helped developers in the process of producing and maintaining software. The study indicates that automated acceptance testing may be a viable strategy, but that it must be used with care. Communicating requirements throughout the lifespan of the software is just as important as automating the tests, and AAT can help with both of these issues.
