June 2014 - overlord-issues - Jboss List Archives

[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/5/14 4:47 PM: ----------------------------------------------------------- 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. The exception to that may be Fuse. Arquillian's OSGi containers work well and simply re-using our features.xml (or at least model the deployment after it) should be doable. was (Author: brmeyer): 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)

10 years, 6 months

1
0
0 / 0

[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: ----------------------------------- 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)

10 years, 6 months

1
0
0 / 0

[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 updated SRAMP-431: ------------------------------ Summary: Arquillian-based integration tests (was: Investigate using Arquillian for S-RAMP unit and integration tests) > 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

1
0
0 / 0

[JBoss JIRA] (SRAMP-460) Integration tests: Fuse

by Brett Meyer (JIRA)

[ https://issues.jboss.org/browse/SRAMP-460?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-460: ----------------------------------- Hey [~virchete], initially assigning this to you. Checkout my ideas on SRAMP-431 and let me know what you think. I have a branch where I'm starting to work on some of the core ideas -- when you're ready to look at this a bit, ping me. > Integration tests: Fuse > ----------------------- > > Key: SRAMP-460 > URL: https://issues.jboss.org/browse/SRAMP-460 > Project: S-RAMP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Brett Meyer > Assignee: David virgil naranjo > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-461) Integration tests: EAP

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-461: --------------------------------- Summary: Integration tests: EAP Key: SRAMP-461 URL: https://issues.jboss.org/browse/SRAMP-461 Project: S-RAMP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer May need to split this into EAP 6.1 and 6.3 -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-460) Integration tests: Fuse

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-460: --------------------------------- Summary: Integration tests: Fuse Key: SRAMP-460 URL: https://issues.jboss.org/browse/SRAMP-460 Project: S-RAMP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: David virgil naranjo -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-458) Integration tests: Tomcat

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-458: --------------------------------- Summary: Integration tests: Tomcat Key: SRAMP-458 URL: https://issues.jboss.org/browse/SRAMP-458 Project: S-RAMP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-459) Integration tests: Jetty

by Brett Meyer (JIRA)

Brett Meyer created SRAMP-459: --------------------------------- Summary: Integration tests: Jetty Key: SRAMP-459 URL: https://issues.jboss.org/browse/SRAMP-459 Project: S-RAMP Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brett Meyer Assignee: Brett Meyer -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (SRAMP-431) Investigate using Arquillian for S-RAMP unit and 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/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. https://community.jboss.org/wiki/S-RAMPContainerAdapterForArquillianAvail... was (Author: brmeyer): https://community.jboss.org/wiki/S-RAMPContainerAdapterForArquillianAvail... > 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. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (RTGOV-482) Register mbeans in Karaf, to be available in hawtio console

by Gary Brown (JIRA)

[ https://issues.jboss.org/browse/RTGOV-482?page=com.atlassian.jira.plugin.... ] Gary Brown updated RTGOV-482: ----------------------------- Original Estimate: 1 week (was: 3 days) Remaining Estimate: 1 week (was: 3 days) > Register mbeans in Karaf, to be available in hawtio console > ----------------------------------------------------------- > > Key: RTGOV-482 > URL: https://issues.jboss.org/browse/RTGOV-482 > Project: RTGov (Run Time Governance) > Issue Type: Sub-task > Reporter: Gary Brown > Assignee: Gary Brown > Fix For: 2.0.0.Final > > Original Estimate: 1 week > Remaining Estimate: 1 week > -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues June 2014