On 23/04/07, Alan Conway <[EMAIL PROTECTED]> wrote:
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.
I agree that we really need to focus on testing (unit, functional and
interop). It is interesting to see every one's opinion on a
reorganisation. I remember the pain we had with our maven
reorganisation but that was more to do with getting the tool to work.
I'm not driven to have a particular layout especially when development
tools these days present everything as one view anyway.
We do currently have an mix between functional and language structure.
The gentools are for all languages rather than there being a
c++/gentools or a java/gentools. Thinking about the interop testing
system that we are in the process of building. I would have thought it
would have been good to have it together rather than spread across
language specific folders.
Thanks for the thoughts, guess as a group we don't really want to move
things around just now. As long as we do not force our developers to
build entire products they do not wish/need with our current setup
then I have no real problem. Just thought I'd mention it while we had
a brief pause between AMQP versions.
Cheers
--
Martin Ritchie
