[overlord-issues] [JBoss JIRA] (SRAMP-431) Arquillian-based integration tests
[
https://issues.jboss.org/browse/SRAMP-431?page=com.atlassian.jira.plugin....
]
Gary Brown commented on SRAMP-431:
----------------------------------
Agree using managed containers would be good for all but fuse, to replicate the
installation process as well. Areas to consider:
1) As Eric said, EAP cannot be downloaded, so we need to work out an alternative approach
for obtaining this distribution. Although we will want to support WildFly at some point,
it would be good to have EAP as a separate test.
2) RTGov requires Switchyard to also be installed - atleast for EAP - however this should
just be a case of adding its installation as an additional step before running the
integration tests.
3) For RTGov we will need to partition the integration tests, as there are groups of tests
that use different deployments. Although this may not be an issue for SRAMP or DTGov, it
would be good to factor this in to the design, so we use a common approach across the
sub-projects.
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 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.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)