[ https://issues.jboss.org/browse/SRAMP-431?page=com.atlassian.jira.plugin.... ] David virgil naranjo commented on SRAMP-431: -------------------------------------------- Hi Brett, I like how you structure the Arquillian Integration Tests. This post is useful: https://docs.jboss.org/author/display/ARQ/Container+adapters It does not say anything about eap 6.3, that is the latest one we support. Interesting post that explains difference between remote, embedded and managed containers. http://arquillian.org/blog/2012/04/13/the-danger-of-embedded-containers/ About UI testing. I have been reviewing today, selenium and arquillian: Selenium: There is a firefox plugin that generates the test suite code, recording the steps done in the browser. Then it generates java code. You need to specify the url (can be modified depending the profile). It also allow to run the same test in different browsers using the parameterized annotation. It would require that the server instance (tomcat, jetty, jboss...) is started. In continuous integration that could be done easily. Just adding the tomcat plugin, or jboss plugin and calling start and stop. As the selenium tests would be just junit tests, they would be located in the src/test folder of every ui project. Related Links: http://seleniumsimplified.com/get-started/ Good videos to show how easy could be to develop tests. http://blog.wedoqa.com/2013/10/parameterized-junit-tests-with-selenium-we... Arquillian Arquillian allows UI testing using Arquillian drone. But the problem here is that, it requires the test to create all the artifact to be deployed manually: https://community.jboss.org/en/arquillian/blog/2011/09/17/functional-test... In our case we do not have just html files in the webapp folder. We have gwt as UI technology. I have seen another project arquillian-gwt-extension, but there is not so much documentation and the community is not big. https://community.jboss.org/thread/236077 It could be interesting because it would test the gwt ui as dev mode. But as ease of development, I prefer selenium. Why? Because you do not need to think a lot, just go to the browser, make the bunch of steps, generate the code and adapt it little bit. Maybe I could be wrong. Just waiting your comments and ideas. Thanks David -- This message was sent by Atlassian JIRA (v6.2.6#6264)