History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: IDEA-11797
Type: New Feature New Feature
Status: Open Open
Assignee: Alexey Kudravtsev
Reporter: Peter Lawrey
Votes: 3
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
IDEA: Feedback

Allow unit tests to be run seperate JVMs.

Created: 05 Mar 07 13:24   Updated: 12 Jun 07 04:57
Component/s: Unit Testing. JUnit

Environment: Window

Build: 6,148
Severity: Low


 Description  « Hide
Support a per test fork mode for unit tests.
Maven supports "If you need to run your tests in a new JVM process you can use the forkMode option to start a new JVM process once for all your tests, or start a new JVM process for each of your tests"
It would be useful if IntelliJ supported this as well.

Basically we see an occational error due resources not being cleanup between tests. While an issue, we won't be stop/starting components this way in maven/teamcity/dev or production so it isn't a high priority at present and it would be simpler for the moment to have perTest forking in IntelliJ as well.
We are also looking at resource consumption of different tests, perTest foring would assist to get accurate and consist values (without having to run all tests individually)

BTW: to find problems which only occur when running multiple tests in the same JVM it would help if the tests could run in a predictable order because the order tests are run becomes important in reproducing the problem.



 All   Comments   Work Log   Change History      Sort Order:
Dmitri Colebatch - 12 Jun 07 04:57
Could someone from Jetbrains comment on this please? Will it be fixed in 7? Whilst I realise it is a low priority, I also see it as being very easy to fix, and its annoying to have the worlds best IDE but then have to use ant or maven to run tests (I'm using a thirdparty product that has problems with its test mode and hence have to use forkMode=true).