well it is very different and I think we'll need both to keep tests simple. Using a rule to handle our standalone test would be a good solution and simple without the need to package an app with classes and resources etc
Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2015-01-29 8:31 GMT+01:00 Mark Struberg <[email protected]>: > That's why I wanted some 'isolating' Arquillian SE adaptor :) > I prefer using Arquillian over any homegrown solution as we might use that to > later test EE containers as well. > > LieGrue, > strub > > > > >> On Thursday, 29 January 2015, 0:33, Romain Manni-Bucau >> <[email protected]> wrote: >> > it works while the SPI file doesn't exist on disk. We can also simply >> have a test classloader, should be far enough and avoid to depend on >> SW and having to create archives (we just switch the classloader which >> knows the SPI we want and that's it). >> >> >> Romain Manni-Bucau >> @rmannibucau >> http://www.tomitribe.com >> http://rmannibucau.wordpress.com >> https://github.com/rmannibucau >> >> >> >> 2015-01-29 0:28 GMT+01:00 Oliver B. Fischer <[email protected]>: >>> FYI: >>> >>> I found out who to write tests for Tamaya with an adapted classpath by >> using >>> ShrinkWrap. This will allow us to build test cases with various >> self-defined >>> Jars with different SPI implementations. I will try to provide an inital >>> example. >>> >>> Bye, >>> >>> Oliver >>> >>> -- >>> N Oliver B. Fischer >>> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany >>> P +49 30 44793251 >>> M +49 178 7903538 >>> E [email protected] >>> S oliver.b.fischer >>> J [email protected] >>> X http://xing.to/obf >>> >>
