• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

The Art of Agile Development-automated acceptance test

 
Ranch Hand
Posts: 254
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Does this book cover concept of "automated acceptance test" and "estimation of release duration" ?

Regards,
Joshua
 
author
Posts: 46
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
     
    Lasagna is spaghetti flvored cake. Just like this tiny ad:
    a bit of art, as a gift, that will fit in a stocking
    https://gardener-gift.com
    reply
      Bookmark Topic Watch Topic
    • New Topic