Summary: | [JUnit] allow running Tests in separate JVMs (fork=true) | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | alexander golubev <golubec> |
Component: | UI | Assignee: | JDT-UI-Inbox <jdt-ui-inbox> |
Status: | ASSIGNED --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 | CC: | bindulbhowmik, gautier.desaintmartinlacaze, golubec, markus.kell.r, schauer |
Version: | 3.6 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Windows Vista | ||
Whiteboard: |
Description
alexander golubev
2009-12-17 06:20:17 EST
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 |