Hi, I have just finished a rough draft [1] of our integration tests using Pax Exam [2]. Only "CreateNodeTest" until now.
I have had to make some changes in order to re-use our prior integration testing stuff: * HttpTestBase [3] doesn´t extend TestCase anymore and extends PaxExamTestBase [4] instead. * commons-httpclient and commons-codec has been provided as bundles from servicemix bundles distribution [5] for convenience. * o.a.s.commons.testing has been provided in a wrapped way. Maybe we could make a bundle of this later. In the other hand, I have used the jcrinstall Bertrand´s code to make all system properties available to OSGi framework VM instance and set optional debugging. Thanks Bertrand :). IMO the main drawback of this approach is that test execution become slower than before because every test is run in its own container instance. Although there is an opened issue to look for a workaround [6], this could not be so bad in order to run each test kept in isolation. As far this is concerned, I have not a clear opinion right now. In the other hand, this kind of testing offers some advantages such as OSGi container vendor pluggability. WDYT?. [1] http://svn.apache.org/repos/asf/incubator/sling/whiteboard/jvazquez/testing [2] http://wiki.ops4j.org/display/paxexam/Pax+Exam [3] http://svn.apache.org/repos/asf/incubator/sling/whiteboard/jvazquez/testing/src/test/java/org/apache/sling/itest/HttpTestBase.java [4] http://svn.apache.org/repos/asf/incubator/sling/whiteboard/jvazquez/testing/src/test/java/org/apache/sling/itest/PaxExamTestBase.java [5] http://repo2.maven.org/maven2/org/apache/servicemix/bundles/ [6] http://issues.ops4j.org/browse/PAXEXAM-79 On Mon, Apr 6, 2009 at 11:08 AM, Felix Meschberger<fmesc...@gmail.com> wrote: > Hi, > > Juan José Vázquez Delgado schrieb: >>> Do you know it a bit ? Can you take a stab at converting the current >>> Cargo based setup to be using Pax Exam ? >> >> First time for me. I´m gonna try this and tell us. > > Great ! Thanks. > > Regards > Felix > > >