[seam-dev] Arquillian Testsuite structure for Modules

[Dan Allen]

On Wed, Aug 10, 2011 at 15:01, Ken Finnigan <ken at kenfinnigan.me> wrote:

> Shane,
>
> Jason's correct, the main extrapolation point at the moment is pulling the
> container-boms I've created into a location that all modules can use, and
> expanding them to include the ones that Dan has put together.
>

Good. I gave a stab at the container-boms idea in the Arquillian showcase to
prototype this for Seam. Maven is very unfriendly to this idea (I should
blog what I wrote to Aslak about this), but it's at least manageable.

I do have one question. Can the tests still be run in the IDE without any
commandline build step. I think that's essential for maximizing the
friendliness of the Arquillian environment. That's one of the biggest
complaints I had about Solder. It was doing some really strange stuff to
pull in the final artifact JAR, which lengthened the testing cycle.
Arquillian should be edit-save-test. If that's preserved already, excellent.

-Dan

-- 
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110810/37412d29/attachment.html