Community
Participate
Working Groups
It is nice to be able to right-click on the src folder and run the JUnit tests. Unfortunately I have Cactus JUnit tests too, and they have to be launched in a special way. Ant knows how to do it, but Eclipse doesn't. With that in mind, there's a need to tell Eclipse to launch "all JUnit tests that are not Cactus junit tests". This is done from Ant via regular filters, like "**/junit/*.java" etc. Therefore, I'd like to request that the JUnit plugin in Eclipse be changed to incorporate the notion of filters like in Ant. This way I could easily create a launch configuration that represents "all JUnit tests that are not Cactus tests". This could be done with an extra widget for the filter text expression, and the code would actually use the filter when traversing everything under "src".
Markus, any comments?
Can't you put these not-pure-JUnit tests into a separate source folder?
If you send me detailed steps I cam try, but I suspect that it will break our build entirely. You see, we have Ant tasks to compile the code, JAR it, run JDepend on the source, run JavaNCSS on the source, run Findbugs on the source, instrument the code with Emma (code coverage) etc and produce 1 consolidated report from each tool. We run these tools on the actual app code and test code. These tools assume a sources dir, not multiple sources dir. Eclipse has tight integration with Ant, and has tight integration with JUnit, but not both at the same time, as we can see here. My Ant tasks run perfectly fine in Eclipse, they know how to run the pure JUnit tests (API tests that run outside the servlet container) and the Cactus tests (tests that need to run inside the servler container). But from teh JUnit GUI / plugin, it is another story... One option is to fix the JUnit plugin so that it knows how to properly run the Cactus tests as well (too hard, you need to cactify a WAR etc), or at least knows how to recognize them and ignore them when running from the Eclipse GUI (do you really want to hardcode Cactuis knowledge?). I think the SimplestThingThatCouldPossiblyWork is to add support for filters and let users teach Eclipse what tests it should skip because it just doesn't know how to handle properly. Simple and clean.
Bug 40598 also wants to modify the set of tests to be executed from a container.
Would like to have a filter for test to run. Some external projects have conventions like *TestManual for TestCases which should only be run manually. Another request is to exclude Abstract Test Cases, e.g. Abstract*Test. Build tools like Maven have such filters, why not Eclipse too?
