On 20/04/07, Alan Conway <[EMAIL PROTECTED]> wrote:
On Fri, 2007-04-20 at 18:24 +0100, Robert Godfrey wrote: > I would add that at a higher level the best way to get feature choerence is > to use a common set of requirements :-) Hear hear! And the best kind of requirements are executable requirements, aka: tests. If you want common behavior you have to test for it.
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 :-) 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. With a good interop test suite its very easy to tell where you are on
each component: which tests does pass? Its easy to tell how close you are to release - how many tests still fail? Its easy to prepare the list of supported features - which features do we test? Implementing a good interop test framework, mapping our requirements to test cases and implementing those tests across all languages is the most important next step towards a coherent project.
Yes agreed. Cheers, Rob Cheers,
Alan.
