On 18/12/2014 16:05, Michael Dürig wrote: > > On 18.12.14 9:56 , Davide Giannella wrote: >> Don't know if it's really your case; but some time ago we created the >> /oak-jcr/src/test/java/org/apache/jackrabbit/oak/jcr/FixturesHelper.java >> to help and centralise the available fixtures so that could later on >> split the build (in Travis) based on fixtures. >> >> worth a check as you're on the way. :) > > Right,forgot about that one. The problem is however that the fixture > helper is in oak-jcr and those tests are in oak-core. Also the tests > are more unit test like and run quite fast, so for the time being I > don't see much need for action here. Feel free to move around the FixturesHelper. It makes actually more sense to have it in core available to everyone.
If we instruct already all the testing where possible (including unit) to be fixture aware it will help us later on in a further splits of the build on travis. Our unittesting profile is anyhow one of the longest one ;) Davide PS: just noted that travis has been failing for a while now. We should restore the notifications...
