Hey all,

there are two things I would like to address regarding our integration test
suite.

1. Currently each module has its own arquillian.xml file. IMHO this doesn't
make sense. What about using a single arquillian.xml and placing it in the
test-utils module?

2. We have both "managed" and "remote" profiles for some containers. But
the "managed" profiles (especially Wildfly + Glassfish) require you to
manually download and setup the corresponding container which I would like
to avoid. I think it would be nicer if the "managed" profiles could do this
automatically. This would simplify the process of running the tests locally
before committing and it would also be easier to create CI jobs for them.
See [1] for an example of a profile which sets up the container
automatically and therefore runs out of the box even in transient CI
environments like Travis [2].

Thoughts?

[1] https://github.com/ocpsoft/rewrite/blob/master/pom.xml#L706
[2] https://travis-ci.org/ocpsoft/rewrite/builds/16192940

Christian


-- 
Christian Kaltepoth
Blog: http://blog.kaltepoth.de/
Twitter: http://twitter.com/chkal
GitHub: https://github.com/chkal

Reply via email to