Humans to Test Early...Machines to Test Often

This is a platform where we share testing processes, practices and key concepts with the testing community to enable implementation of successful and efficient testing in projects. Our goal is to provide a distilled collection of techniques and discussions, based on ThoughtWorks' expertise in the testing sphere, which can be directly applied to improve the quality of software products.

Read more about us

Home

Submitted by satnair on Mon, 04/21/2008 - 10:10.

Acceptance Test Driven Planning

Author: 
Richard J. Watt, David Leigh-Fellows
The experience of writing and maintaining Acceptance Tests for many is not a successful one. Perhaps, like unit tests, their worth is misunderstood. When first introduced to acceptance testing many think of them merely as a form of black box testing and miss their greater significance as a multi-use form of requirements specification. We have found that by making acceptance tests not only central to the definition of a story but central to our process they can be used to drive the entire development.

Getting more out of automated acceptance tests

Author: 
Kristan Vingrys
Acceptance tests are used to verify that a story (requirement) is complete, automating these tests is common and it helps regression testing and iterative development. Even though the tests are extremely powerful and have improved quality of projects delivered, they are not being used to their full potential. Many projects need to be tested in a system test or pre-production environment before going live.
more

Blogs