[overlord-issues] [JBoss JIRA] (SRAMP-431) Arquillian-based integration tests
[
https://issues.jboss.org/browse/SRAMP-431?page=com.atlassian.jira.plugin....
]
Brett Meyer commented on SRAMP-431:
-----------------------------------
My initial thought was that none of these should use Arquillian's embedded containers.
Each targeted container would be downloaded (if running the tests for the first time) and
unpacked, then kick off the S-RAMP installer. Then, run Arquillian in a managed-container
mode.
I'd rather do something automated, w/ respect to the container distros, than require
the tester to pull them down on their own and set an env var.
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)