On Fri, Apr 24, 2009 at 10:51 AM, kelvin goodson <[email protected]> wrote: > I've just added the start of something that will make the otests available > to all. Under the new otest directory is a current and a fixed_version > directory. We can't rely on the foreign svn repository that holds these > tests not changing significantly (that wouldn't be a risk to the build since > I don't have any intention of hooking this into the build at the moment). > > The "current" directory has an svn:externals property set which does an > unqualified extract of the otests from the foreign svn repo. The > "fixed_version" directory does the same svn:externals extract, but > qualified with a revision number of the foreign repo. That way any one > wanting to have a play with these tests can go to an informally blessed > version. At the time of writing these work out to be identical. > > Without having dug very far at the moment I see 84 tests running, with 40 > failures and 1 error. I'll work to see how many of these are just down to > an imature tuscany infrastructure and how many are real failures/errors. > I'll then look at ensuring we have JIRAs to accompany the issues. > ...snip
Hi Kelvin Sounds good to me. I haven't updated and tried this yet but am looking at svn. Can you say something about how the Tuscany framework code, that makes the generic OASIS tests work, will be arranged? Simon
