File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Agile and Other Processes and the fly likes The Art of Agile Development-automated acceptance test Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Agile and Other Processes
Bookmark "The Art of Agile Development-automated acceptance test" Watch "The Art of Agile Development-automated acceptance test" New topic

The Art of Agile Development-automated acceptance test

Joshua Antony
Ranch Hand

Joined: Jun 05, 2006
Posts: 254
Does this book cover concept of "automated acceptance test" and "estimation of release duration" ?


James Shore
Ranch Hand

Joined: Sep 21, 2007
Posts: 46
Hi Joshua,

We do cover automated acceptance tests quite thoroughly, but perhaps not from the perspective you would expect. I'm the project coordinator for Fit, a popular acceptance testing tool, and working with teams that use Fit has given me a lot of experience with automated acceptance tests.

As I worked with these teams, I consistently noticed several things:

  • The acceptance tests were a maintenance burden, leading to slow and frequently-broken builds.
  • The tests were difficult to read and understand.
  • Customers weren't participating deeply (or at all) in the creation of acceptance tests

  • For the last four years, I've been experimenting with alternatives to acceptance tests, and I've settled on the following combination of practices as an alternative to traditional acceptance tests:

  • Test-driven development (for its comprehensive regression suite)
  • Customer tests with Fit (for examples/tests of business logic)
  • On-site customer reviews (for communicating details and "done done")
  • Exploratory testing (for verifying that the process is working correctly)

  • The "customer tests" practice is most similar to traditional automated acceptance tests, but we've intentionally constrained it in order to increase rigor and reduce maintenance costs.

    James Shore, coauthor of <a href="" target="_blank" rel="nofollow">The Art of Agile Development</a>. Website and blog at <a href="" target="_blank" rel="nofollow"></A> .
    I agree. Here's the link:
    subject: The Art of Agile Development-automated acceptance test