[JBoss JIRA] (SRAMP-431) Arquillian-based integration tests
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-431?page=com.atlassian.jira.plugin.... ]
Brett Meyer edited comment on SRAMP-431 at 6/6/14 2:37 PM:
-----------------------------------------------------------
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. There are definitely pros/cons -- I could go either way.
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.
was (Author: brmeyer):
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)
10 years, 6 months
[JBoss JIRA] (SRAMP-431) Arquillian-based integration tests
by Brett Meyer (JIRA)
[ 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)
10 years, 6 months
[JBoss JIRA] (SRAMP-431) Arquillian-based integration tests
by Eric Wittmann (JIRA)
[ https://issues.jboss.org/browse/SRAMP-431?page=com.atlassian.jira.plugin.... ]
Eric Wittmann commented on SRAMP-431:
-------------------------------------
Can't auto-download EAP though, right? Do we use wildfly instead?
Also, why not use the embedded containers? (question from an Arquillian n00b)
> 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)
10 years, 6 months
[JBoss JIRA] (RTGOV-490) Refactor to better support multiple installation targets
by Gary Brown (JIRA)
Gary Brown created RTGOV-490:
--------------------------------
Summary: Refactor to better support multiple installation targets
Key: RTGOV-490
URL: https://issues.jboss.org/browse/RTGOV-490
Project: RTGov (Run Time Governance)
Issue Type: Task
Reporter: Gary Brown
Assignee: Gary Brown
Fix For: 2.0.0.Final
Aim is to create a single distribution that will contain an installer for all supported platforms.
Subject to changes in the overlord-commons installer, to setup the target environment, the rtgov installer should apply additional changes to the target location.
As part of this refactor, the integration tests should be moved out into a separate top level folder - aim will be to support integration testing across all supported platform from the same set of arquillian tests.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (SRAMP-443) The Teiid model deriver is not being used
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-443?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated SRAMP-443:
------------------------------
Fix Version/s: 0.5.0.Alpha1
> The Teiid model deriver is not being used
> -----------------------------------------
>
> Key: SRAMP-443
> URL: https://issues.jboss.org/browse/SRAMP-443
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Core
> Affects Versions: 0.4.0 - Tomcat Support
> Reporter: Eric Wittmann
> Assignee: Brett Meyer
> Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> The org.overlord.sramp.integration.teiid.deriver.ModelDeriverProvider class is not providing the correct deriver. I think this class was copy/pasted and never changed to return the correct provider type.
> I think we just need to change from this:
> {code}
> return Collections.singletonMap(TeiidArtifactType.MODEL.extendedType(), (ArtifactDeriver)new VdbManifestDeriver());
> {code}
> to this:
> {code}
> return Collections.singletonMap(TeiidArtifactType.MODEL.extendedType(), (ArtifactDeriver)new ModelDeriver());
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months
[JBoss JIRA] (SRAMP-443) The Teiid model deriver is not being used
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-443?page=com.atlassian.jira.plugin.... ]
Brett Meyer resolved SRAMP-443.
-------------------------------
Resolution: Done
> The Teiid model deriver is not being used
> -----------------------------------------
>
> Key: SRAMP-443
> URL: https://issues.jboss.org/browse/SRAMP-443
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Core
> Affects Versions: 0.4.0 - Tomcat Support
> Reporter: Eric Wittmann
> Assignee: Brett Meyer
> Fix For: 0.5.0.Final, 0.5.0.Alpha1
>
>
> The org.overlord.sramp.integration.teiid.deriver.ModelDeriverProvider class is not providing the correct deriver. I think this class was copy/pasted and never changed to return the correct provider type.
> I think we just need to change from this:
> {code}
> return Collections.singletonMap(TeiidArtifactType.MODEL.extendedType(), (ArtifactDeriver)new VdbManifestDeriver());
> {code}
> to this:
> {code}
> return Collections.singletonMap(TeiidArtifactType.MODEL.extendedType(), (ArtifactDeriver)new ModelDeriver());
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
10 years, 6 months