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