Type: Feature Request
Status: Open (View Workflow)
Affects Version/s: None
Fix Version/s: None
Similar Issues:Show 10 results
ARQ-379 Arquillian does not allow any configuration of OpenEJB ARQ-838 Allow Arquillian Drone to handle Robotium ARQ-832 Get familiar with Arquillian project ARQ-1653 Drone use concurrent.ExecutorService without Context inheritance on Threads ARQ-809 Arquillian Build Broken Using Default Config ARQ-1377 Arquillian / Concordion integration ARQ-880 Allow extensions create new child tests with dynamic nature ARQ-646 TestNG groups can only be used to run non Arquillian tests ARQ-1207 Support arquillian. prefix in configuration properties ARQ-994 Allow Arquillian Drone to wait asynchronously for instance creation
Thanks for all your hard work on Arquillian! I have a small feature request:
At present Arquillian has a rather 'programmatic' API: you have to write Java code to do anything. This works great for ShrinkWrap, JUnit, HtmlUnit etc (ie. testing CDI, EJB, JMS etc). But it doesn't work so well for non-Java-code tools such as Canoo WebTest (ie. testing JSF).
In order to support Canoo WebTest, Arquillian should be able to deploy/start/stop the server purely from Maven. Then I can use maven-webtest-plugin to run my webtest.xml (purely from Maven) and I'm done! I find testing XHTML output using an XML-based testing framework good because there is a lower 'impedence mismatch' than when using Java-code to test XHTML output.
At present I'm able to get what I want using jboss-maven-plugin. It closely mirrors tomcat-maven-plugin and jetty-maven-plugin, which is great. However:
1. I have to use a fragile 'sleep' to wait until my app has deployed (see http://jira.codehaus.org/browse/MJBOSS-61)
2. jboss-maven-plugin appears to be unsupported (hasn't been updated to support AS 6 or 7)
So I'd really like to see Arquillian supersede in this space? There is this: https://github.com/arquillian/arquillian-maven, but apparently it isn't able to act quite like jboss-maven-plugin can: http://community.jboss.org/message/622128#622128
An example of how I currently do this (using jboss-maven-plugin) can be found here:
This is a pom.xml which you can do 'mvn install' on, and it'll download/unpack/deploy/start/test/stop. You'll also need the parent poms: