|Apr 12, 2006||–||
Tests Vs Specifications
Reading Brian Marick's post on Tests and Specifications made me wonder about how to describe the assertions in Agitator. They certainly are of the form Brian describes:
In math geek terms, specifications are universally quantified statements, ones of the form "for all inputs such that <something> is true of them, <something else> is true of the output." Tests are constant statements, ones with no variables. They look like this: "given input 5, the output is 87."This distinction comes into play when we use TDD with Agitation. The tests help us move forward one case at a time and then Agitiator helps us review if we've accurately captures the specification of the system, or if we've missed boundary cases. It is a shift from the "There Exists" to the "For All" mindset.
|Mar 31, 2006||–||
Agitator is Not a Test Generator
Agitator is not a test generator. It is an exploritory testing tool for developers. You turn to it to answer the questions "what does this code actually do? what did the author forget to consider?"
|Jan 26, 2004||–||Violent Agreement In his blog Patrick Logan makes a very good point that "we have to make a distinction about what kinds of tests we're writing and what kinds of tests we want to automate." more »|