THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- Re-organise all system tests into a sensible structure, such that closely related tests reside near each other. We could organise them by category, e.g.
- Areas of the JMS spec
- Separation of JMS vs non-JMS tests. The former would in theory be able to be run with different JMS clients.
- It should then be easy to identify and remove the cruft. This could include replacing some system tests with unit tests.
...
This would be possible to do using our existing test-profiles approach, but may be easier using JUnit4 categories (http://kentbeck.github.com/junit/javadoc/latest/org/junit/experimental/categories/Categories.html
). An added benefit of Categories is that they allow us to categorise test classes "in-line" rather than storing their names in a separate file. This reduces the chance of the class name in a test exclusion becoming incorrect after, say, the test's package changes.
...