[
https://issues.jboss.org/browse/JBIDE-10257?page=com.atlassian.jira.plugi...
]
Pavol Srna commented on JBIDE-10257:
------------------------------------
All the tests are the same for JBT and also for JBDS. The only thing what is different -
are the runtimes we use. All the tests should be able to run against community projects as
well as against the JBoss products.
Max, Denis, what about this:
1) Denis will add only community project (riftsaw, modeshape, teiid runtime, etc.)
requirements that we miss.
2) I will create 2 sets of testing jobs on jenkins. One set for JBDS (testing against
JBoss product runtimes - like for example SOA) and the other for JBT (testing against
community projects).
So as a result there will be a default configuration that can be run outside vpn. But we
have to find out how to run the tests against JBoss product runtimes. My first idea is to
write some script (it will be devstudio specific and can be stored in devstudio
repository) which will prepare the jboss product runtimes and to pass the location path of
the runtime to maven using a system property, or somehow similar.
Add new set of requirements for usage in SWT Bot tests
------------------------------------------------------
Key: JBIDE-10257
URL:
https://issues.jboss.org/browse/JBIDE-10257
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng, testing
Affects Versions: 3.3.0.M5
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 3.3.0.M5
1) riftsaw 2.3.0.final
2) jboss-esb-4.10, 4.9
3) modeshape 2.6.0.Final
4) teiid 7.5, 7.4
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira