d'abord, je crois que 1.0 est la bonne version selon leur site Web. Mon project/build/def.scala
ressemble à ceci:
import sbt._
class Tests(info: ProjectInfo) extends DefaultProject(info) {
val scalatest = "org.scalatest" % "scalatest" % "1.0" % "test"
}
Ensuite, faites un sbt update
, puis un sbt reload
(pas sûr que le rechargement est nécessaire, mais il ne fait pas mal)
maintenant dans /src/test/scala
, utilisez leur exemple, mais aussi l'importation scala.collection.mutable.Stack
et sbt test
fonctionne bien pour moi
[email protected]:~/dev/test2$ sbt test
[info] Building project test 1.0 using Tests
[info] with sbt 0.5.6 and Scala 2.7.7
[info]
[info] == compile ==
[info] Source analysis: 0 new/modified, 0 indirectly invalidated, 0 removed.
[info] Compiling main sources...
[info] Nothing to compile.
[info] Post-analysis: 0 classes.
[info] == compile ==
[info]
[info] == copy-test-resources ==
[info] == copy-test-resources ==
[info]
[info] == copy-resources ==
[info] == copy-resources ==
[info]
[info] == test-compile ==
[info] Source analysis: 0 new/modified, 0 indirectly invalidated, 0 removed.
[info] Compiling test sources...
[info] Nothing to compile.
[info] Post-analysis: 4 classes.
[info] == test-compile ==
[info]
[info] == test-start ==
[info] == test-start ==
[info]
[info] == StackSpec ==
[info] A Stack
[info] Test Starting - A Stack should pop values in last-in-first-out order
[info] Test Succeeded - A Stack should pop values in last-in-first-out order
[info] Test Starting - A Stack should throw NoSuchElementException if an empty stack is popped
[info] Test Succeeded - A Stack should throw NoSuchElementException if an empty stack is popped
[info] == StackSpec ==
[info]
[info] == test-complete ==
[info] == test-complete ==
[info]
[info] == test-finish ==
[info] Run: 2, Passed: 2, Errors: 0, Failed: 0
[info]
[info] All tests PASSED.
[info] == test-finish ==
[info]
[info] == test-cleanup ==
[info] == test-cleanup ==
[info]
[info] == test ==
[info] == test ==
[success] Successful.
Juste pour vous assurer, avez-vous placé le fichier de test dans le chemin Maven correcte? –