[overlord-issues] [JBoss JIRA] (SRAMP-431) Arquillian-based integration tests

[Brett Meyer (JIRA)]

    [ https://issues.jboss.org/browse/SRAMP-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982484#comment-12982484 ] 

Brett Meyer commented on SRAMP-431:
-----------------------------------

Re-wrote the description, after scraping off my Arquillian rust ;)

All, take a look at https://github.com/brmeyer/s-ramp/compare/integration-tests and let me know your thoughts.  So far, it downloads Tomcat, unpacks it, and runs the full S-RAMP installer on it.  Arquillian runs Tomcat in a managed-mode, then runs a simple client test (passes).  Jetty's setup will be nearly identical.  EAP too, minus the downloading (unpack the distro zip from a known location or support $JBOSS_HOME).

However, Arquillian does not currently have a Jetty 8 container.  Since there is Jetty 7 & 9, I may look into contributing one for 8.

> Arquillian-based integration tests
> ----------------------------------
>
>                 Key: SRAMP-431
>                 URL: https://issues.jboss.org/browse/SRAMP-431
>             Project: S-RAMP
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>
> Create a new s-ramp-test module to contain all integration tests.  Thoughts:
> - 1 central ant script, executed by the POM, should be in charge of downloading the Jetty and and Tomcat distros, then unpacking them.  Arquillian would then use them in a "managed mode."
> - The ant script will eventually be in charge of downloading EAP as well, but not until we have CI hardware within the RH network.  Until then, we'll need to do something similar to RTGov's current tests: require the distro be manually downloaded and unpacked, then set $JBOSS_HOME
> - Fuse should be run in embedded mode.
> - No tests should run by default.  Hide all behind container-specific profiles, enabled only on the CI job(s).
> - Include a simple s-ramp-client based test to at least ensure the app comes up, auth works, and uploading/querying works.
> - Pull in any functional tests from the other modules requiring the server to be spun-up.  Leave behind only pure *unit* tests.
> The work-in-progress: https://github.com/brmeyer/s-ramp/compare/integration-tests



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)