Details
-
Type:
Task
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.0.0-RC2
-
Fix Version/s: 2.0.0-RC2
-
Component/s: Build: Integration Tests
-
Labels:None
-
User impact:Low
-
Similar Issues:None
Description
A few things that come to mind:
1. There are many functional tests which are currently in the Integration Tests (/tests) module but only depend on a single transport and could therefore be moved to their respective module (e.g., HTTP, JMS, E-mail)
2. Leverage m2 profiles for better enabling/disabling of functional tests (e.g., if I'm off-line but run "mvn -Poffline test" all tests should pass anyways because any tests which require a network connection are disabled by the profile)
3. Now that we've got a beefy build server we should try to get as many 3rd-party integration tests running as possible (e.g., run live tests against Geronimo, JBoss, ActiveMQ, Websphere, Oracle, Tibco, etc.)
4. Perhaps we could use VMWare and/or User Mode Linux to run integration tests under different Operating Systems?
Issue Links
- relates to
-
MULE-975
Move org.mule.tck classes out to a separate module
-
Add stress + load tests to this list.