« Why the big pause? | Main | James Shore: The Art of Agile Development »

June 13, 2006

Testing smesting ...

Today’s lunchtime addition to my book:

Tim the testing manager is talking about their testing:

‘What we found was that we could find a surprisingly large number of defects without doing any actual testing.  This happened when the requirements were ambiguous or misunderstood.  Writing the test scripts clarified the requirements. 

‘Now, we used this approach to find defects without testing but we still had to rework them.  Here’s my idea: why don’t we write tests for each feature, before we write the code, so that we can prevent defects before anything is built?  The tests will essentially be used instead of an ambiguous specification.  As we learn more about each feature we can update the tests.  How does that sound?’.

And then someone points to this in a yahoo group: http://www.butunclebob.com/ArticleS.UncleBob.AgilePeopleStillDontGetIt

 

 

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00e5501159c3883400e54ffd1cc38833

Listed below are links to weblogs that reference Testing smesting ...:

Comments

Feed You can follow this conversation by subscribing to the comment feed for this post.

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment