]
Brett Meyer edited comment on SRAMP-431 at 6/5/14 3:54 PM:
-----------------------------------------------------------
This probably won't be too useful for this specific task, as we're more concerned
with testing S-RAMP in various containers, but it's worth looking into.
Investigate using Arquillian for S-RAMP unit and 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.