You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using scalatest from sbt in one of my scala project and everything works fine, meaning all my 31 tests runs in 5 seconds.
I have just installed scala ide and your awsome scalatest-eclipse-plugin and my tests are running in more than 14 seconds. 13 seconds out of these 14 seconds are spent in the discovery step. It happens even if I run the tests several times in a row.
More information about my environment/context:
Eclipse Standard/SDK
Version: Kepler Service Release 1
Build id: 20130919-0819
Scalatest Plugin version 2.9.3.v-3-2_10-201312120320
My 31 tests are in the same package: "my.company.tests" and I ran a package type scalatest configuration given this package name
The text was updated successfully, but these errors were encountered:
interesting, the plugin actually is delegating the discovery to ScalaTest itself (by using -w and -m), i wonder what version of ScalaTest are you using?
sorry for replying, only see the list when i am trying to update the plugin yesterday, and only discovered that i am not 'watching' the project, thus no email notification received!
!
sorry for replying, only see the list when i am trying to update the plugin yesterday, and only discovered that i am not 'watching' the project, thus no email notification received!
I am using scalatest from sbt in one of my scala project and everything works fine, meaning all my 31 tests runs in 5 seconds.
I have just installed scala ide and your awsome scalatest-eclipse-plugin and my tests are running in more than 14 seconds. 13 seconds out of these 14 seconds are spent in the discovery step. It happens even if I run the tests several times in a row.
More information about my environment/context:
Version: Kepler Service Release 1
Build id: 20130919-0819
The text was updated successfully, but these errors were encountered: