Bug in IntelliJ / ScalaTest2 / dynamic.classpath

We have a problem with unreliable unit-tests in IntellIJ using ScalaTest2.

When dynamic.classpath property is set to true,  the process often hangs, we get false failures, and the reporting is messed up (individual tests are not reported under the proper class name, etc.)

When it is set to false everything works, but we have too many tests to do this.

My colleague has posted a question on SO: stackoverflow.com/questions/22038949/scalatest2-cannot-run-unit-tests-when-dynamic-classpath-is-enabled-in-intellij1

IntelliJ v13.0.2
scala plugin v0.30.387
scala v2.10.0
scalatest v2.10.2.0

1 comment
Comment actions Permalink


Here is youTrack bug submission for this issue: http://youtrack.jetbrains.com/issue/SCL-6737

A fix that solves reporting problems and should solve all other problems (failed to reproduce other weird behaviors) will be present in latest EAP and nightly build scala plugin versions.



Please sign in to leave a comment.