[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:all-tabpanel ]

Brett Meyer updated SRAMP-431:
------------------------------

    Description: 
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/commits/integration-tests
https://github.com/brmeyer/s-ramp/compare/integration-tests

  was:
Create a new s-ramp-test module to contain all integration tests.  Thoughts:

- 1 central abstract class (IntegrationTest) that contains all the functional tests and assertions (or if that gets too large, split it up into delegates)
- 1 Arquillian test per supported container, extending the above.  Mainly in charge of the @RunWith and @Deployments.  Ex: EAPIntegrationTest extends IntegrationTest
- None of them should run by default.  Pull them all into a specific Maven profile, then setup a new CI job specifically for it.
- 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.

The work-in-progress: https://github.com/brmeyer/s-ramp/commits/integration-tests



> 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/commits/integration-tests
> https://github.com/brmeyer/s-ramp/compare/integration-tests



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