[jbosstools-dev] Time for a new SOA test repo?

Max Rydahl Andersen max.andersen at redhat.com
Thu Mar 14 04:27:51 EDT 2013


>https://github.com/jbosstools/jbosstools-integration-tests/pull/188
>
>
>The problem is (was) that:
>* The ESB tests require the ESB UI which requires Zest - tests build fails on master for 7.0
>* Zest is not in the JBT test package, but it is in the JBTIS test package

we probably need Zest for other reasons anyway so that probably makes sense to add to core TP anyway.

>* Adding JBTIS TP repo to our root pom in integration-tests would affect all our tests:

>-> The tests would run slower

Hopefully not...did you see a big effect ?

>-> The JBTIS test package might affect our tests - we might miss issues of plugins not being in the JBT test package

not following what you mean here ? if JBTIS test package does affect your test we want to know about it ;)

That said you should be using JBTIS since that is where the esb plugins are. Can't just use jbosstools core as base for this.

>So - what are the solutions?

Split out the github repository and move the integration-platform tests to a separate repo.

>Second, long-term
>* We had talked about this in the past - creating a new SOA test repo

integration-test repo - its no longer just SOA.

>-> The SOA 6 tests will be affected (remember that the ESB examples are still not configured here with JBTIS)

jira ?

>-> This will mean that existing 4.0.x work would move to the new repo

you'll need to migrate the history very carefully yes.

>-> Everyone using the SOA tests will have to adapt
>-> What else can go wrong?
>Need to tell Drools tests - BRMS team - Lukas Petroviky
>- the BRMS team has no one to do the testing at the moment.

/max



More information about the jbosstools-dev mailing list