[jbosstools-issues] [JBoss JIRA] (JBTIS-27) migrate soa/brms tooling tests from jbosstools-integration-tests to new repo jbosstools-integration-stack-itests

[Nick Boldt (JIRA)]

Nick Boldt created JBTIS-27:
-------------------------------

             Summary: migrate soa/brms tooling tests from jbosstools-integration-tests to new repo jbosstools-integration-stack-itests
                 Key: JBTIS-27
                 URL: https://issues.jboss.org/browse/JBTIS-27
             Project: JBoss Tools Integration Stack
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: distribution
    Affects Versions: 4.0.0
            Reporter: Nick Boldt
             Fix For: 4.0.0


Currently, we have 3 update sites being built which include tests, from various repos. 

The most notable of these is jbosstools-integration-tests, which includes UI and integration tests (and framework code) for both the core and (JBT) the SOA/BRMS (JBTIS) projects. Additionally, the individual JBT and JBTIS project also publish test features/plugins to their respective update sites.

These test features are then composited, then aggregated into these sites:

http://download.jboss.org/jbosstools/updates/nightly/coretests/
http://download.jboss.org/jbosstools/updates/nightly/soatests/
http://download.jboss.org/jbosstools/updates/nightly/integrationtests/

Unfortunately, because of conflicting dependencies and version levels (soa is still on Juno, whereas core is on Kepler) not all tests can run against a single target platform/stack.

Therefore, I propose we move the SOA/BRMS (JBTIS) tests into a new github repo: 

*jbosstools-integration-stack-itests*

This would allow those tests to be build/run/published against the upstream JBTIS target platform and projects' test code, as well as incorporating shared code from the upstream core projects' tests (and framework code) published here:

http://download.jboss.org/jbosstools/updates/nightly/coretests/4.0.juno/


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira