Early Access Program

Fork your tests with IntelliJ IDEA 10.5 EAP build 106.447

One of the latest features was long awaited fork mode for JUnit run configurations. Since now it is possible to run your tests in separate VMs. It is possible to choose to fork on class level only.

Check out the list of all changes in the release notes on the IntelliJ IDEA EAP page and download the new build.
Btw, we are going to freeze IDEA 10.5 development soon, so we are actively looking forward for your feedback!

Comments below can no longer be edited.

7 Responses to Fork your tests with IntelliJ IDEA 10.5 EAP build 106.447

  1. Avatar

    Sebastiano Pilla says:

    April 12, 2011

    I would really like to see git-svn in 10.5. There’s an issue already in YouTrack: http://youtrack.jetbrains.net/issue/IDEABKL-5677

  2. Avatar

    yole says:

    April 12, 2011

    Unfortunately there’s no chance that we’ll be able to implement git-svn in the time remaining before the 10.5 release.

  3. Avatar

    Cem Koc says:

    April 12, 2011

    What about themes? Especially Dark themes. There is a dozen open ticket and comments regarding this problem. But still could not be addressed.

  4. Avatar

    Norris Shelton says:

    April 13, 2011

    Maybe I am missing something. I was thinking that this was going to be more like being able to run your JUnit tests in multiple threads like how Maven/JUnit does it. I tried it for the class level and method level and it was VERY slow. It took forever for the individual tests to start. I think it has to do with the JVM allocation. I am running Windows 64-bit.

  5. Avatar

    Anna Kozlova says:

    April 13, 2011

    That is how ant does it (to fully prevent test side effect). It is known to be slow. In order to run your tests in parallel you can use special JUnit runner. Thank you

  6. Avatar

    Paul says:

    January 10, 2012

    Anna, do you mean that we must implement a special JUnit runner to get parallel execution, or is there an existing one we can use?

  7. Avatar

    anet says:

    January 13, 2012

    Paul, you may try to use e.g. org.junit.experimental.ParallelComputer

Discover more