[
https://issues.jboss.org/browse/SRAMP-431?page=com.atlassian.jira.plugin....
]
Brett Meyer updated SRAMP-431:
------------------------------
Description:
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
was:
Create a new s-ramp-test module to contain all integration tests. Thoughts:
- 1 central abstract class 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.
- None of them should run by default. Pull them all into a specific Maven profile, then
setup a new CI job specifically for it.
Also, many unit tests currently spin up a temporary S-RAMP server, once per test class.
Eventually, investigate whether or not some of those test cases should instead be pulled
into the 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 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
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)