[
https://issues.jboss.org/browse/SRAMP-431?page=com.atlassian.jira.plugin....
]
Brett Meyer commented on SRAMP-431:
-----------------------------------
Embedded would be ok for Tomcat/Jetty, I suppose, but I was leaning towards reproducing as
"real-world" setups as possible, utilizing the actual installer on a local
deployment.
Good point about EAP. Technically, it's possible (at least it used to be, but that
may be behind VPN), but there are certainly legal issues with that. If we have to do what
RTGov currently does (download/unpack an EAP distro, set $JBOSS_HOME), so be it. I was
hoping to have all this cooking in Jenkins, but we'd need to think through that.
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)