On Fri, 2007-04-20 at 21:11 +0100, Robert Godfrey wrote: > Hmmm... How do you test your tests are testing the right thing? > > 1. write requirement in English > (1a. agree on requirement) > 2. write test > 3. write code that is going to be tested :-) > Absolutely, you can't map requirements to tests until you know what the requirements are.
> I've seen so many tests that tests that the code does what it does... > Verifying requirements, particularly with people who don't read/write code > is a valuable exercise in itself. The AMQP spec is obviously our major set > of requirements, however we also have Qpid specific requirements. Again absolutely. In an ideal world developers would write unit tests for their code, *users* would write acceptance tests for requirements. I've never seen that happen in real life, but we have quite a few Qpid team members from user organizations which is good, so hopefully we can at least pick up some good quality user requirements in English and get some developer input on test writing from people close to the action. Cheers, Alan.
