Community
Participate
Working Groups
Build Identifier: M20090917-0800 It's common case when ant script has fork=true for junit task. Not all of tests in a project are written by qualified test writers , so the exectuion context can be polluted with different stuff. If you need to just run tests without fixing or correcting them to properly use setUp() and tearDown() - such option like fork=true would be very useful. Reproducible: Always Steps to Reproduce: 1.Go Windows->Preferences->Java->Junit 2.No preferences for Junit is available except "Stack trace filter patterns"
Move to JDT/UI
We won't add a global option for this, but it could maybe be added to the JUnit launch configuration dialog. However, it's not clear with what granularity test should be split up to VMs. In Ant, you can control this via <batchtest> elements. In Eclipse, we don't have a UI to configure individual tests.
Hello, This would be a very welcome enhancement if implemented. It leaves me in a situation with a project where I am unable to run all tests within a project from the same Run Configuration (has to do with derby instances and derby system being persistent on a JVM) within Eclipse. I can however successfully run the tests from Maven (command line). If there is interest, the fork logic could be implemented like Maven Surefire Plugin (see https://maven.apache.org/surefire/maven-surefire-plugin/examples/fork-options-and-parallel-execution.html). Bindul
