We are using it now on Camel trunk, thanks to Willem migrating it from Pax Exam 1.x. Its much better and faster to test. Albeit it still takes longer than a regular unit test, but that is expected its still running a container et all.
On Wed, Jun 20, 2012 at 3:06 PM, Willem Jiang <[email protected]> wrote: > +1 > > Willem > > > On 6/18/12 4:09 PM, Jean-Baptiste Onofré wrote: >> >> Hi all, >> >> Working on karaf-2.3.x branch, I detected issue on the itests after >> upgrading to OSGi 4.3: >> >> https://issues.apache.org/jira/browse/KARAF-1554 >> >> As the Karaf 2.3.x itests are based on the 2.2.x ones, they are >> "fragile" and so it's not easy to update pax-runner and/or OSGi >> framework without breaking something else. >> >> That's why I propose to refactore the itests in order to use >> paxexam-karaf (from github): it will simplify the itests and we will be >> able to easily extend it. >> >> WDYT ? >> >> Regards >> JB > > > > -- > Willem > ---------------------------------- > FuseSource > Web: http://www.fusesource.com > Blog: http://willemjiang.blogspot.com (English) > http://jnn.javaeye.com (Chinese) > Twitter: willemjiang > Weibo: willemjiang -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
