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. 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. Cheers, Alan.
