On Wed, Mar 3, 2010 at 8:44 AM, Luciano Resende <[email protected]> wrote: > On Tue, Mar 2, 2010 at 11:36 AM, ant elder <[email protected]> wrote: >> Now that we have some of the compliance test suites running cleanly >> again what would people think about having them run as part of the >> full build? That seems like the best way to prevent or spot >> regressions but it would add some time to the build. >> >> When we did this before it used svn externals which can be a bit of a >> pain, and it was building all the oasis contributions which adds a bit >> of time, so to make it a bit easier and faster we could publish the >> built contributions somewhere to avoid externals and building them >> each time. Probably OASIS will do that at some point but for now we >> could just have our own zip of them all. Running them could be using a >> separate build profile for now though it does seem like it would be >> good to have them part of the default build eventually. >> >> ...ant >> > > I'd appreciate not using svn externals, as it does not work with git :) > > As for a profile, that has the same implications of going and running > them separately... then it's a matter of getting in peoples mind that > we should run the oTests frequently with our commits. > > > -- > Luciano Resende > http://people.apache.org/~lresende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ >
In r918311 i've added a folder compliance-tests\assembly-tests to trunk that show how the tests could be made part of trunk without using svn externals or duplicating oasis code. There's two OASIS artifacts I've created from the OASIS svn and published in my ASF people space at http://people.apache.org/~antelder/tuscany/otests/maven/. One is a zip of all the assembly test contributions, the other is a jar of the test runner and all the unit tests. Ideally OASIS would release and publish those two somewhere themselves. Then in the tuscany assembly-tests module all there is is a pom.xml that gets/unpacks those two oasis artifacts, the two .properties files to configure the test suite, and the Tuscany TestRuner impl. This works for me and all the test pass, i'd be interested if someone else can try it. It takes about 5 minutes to run for me so its not insignificant if we did add it to the default trunk build. ...ant
