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. Kelvin. 2009/4/22 kelvin goodson <[email protected]> > Hi > > after a long time away from Tuscany I'm in a position to start contributing > again. I'm planning to get involved in testing SCA against the OASIS specs. > To that end I'm going to have a little play in my sandbox with svn:externals > and whatever other tricks I can discover to investigate whether we > can/should auto extract the OASIS tests on a Tuscany svn extract. > > Kelvin. >
