为何Scala中可通过JUnit使用Scalatest？未声明依赖却能运行测试？

Let's tackle your two questions one by one—they tie directly into how Scala testing tools integrate with Java's ecosystem and sbt's dependency management.

1. Why can ScalaTest be used with JUnit in Scala? #

ScalaTest was built to play nicely with established Java testing tools, and JUnit is a big part of that ecosystem. The magic here is the JUnitRunner class you’re using (org.scalatest.junit.JUnitRunner). It acts as a bridge adapter: it implements JUnit’s Runner interface, which lets JUnit’s test execution engine recognize and run ScalaTest test classes seamlessly.

In practice, this means:

• Teams already using JUnit for CI/CD, build pipelines, or test reporting can adopt ScalaTest without overhauling their entire testing setup.
• You get to use ScalaTest’s expressive, Scala-native syntax (like FunSuite and Matchers) while leveraging JUnit’s mature tooling for running and reporting tests.

2. Why does ScalaTest work in your project even when build.sbt only lists JUnit 4.10? #

This is almost certainly due to transitive dependencies or sbt’s automatic test framework resolution—here’s the breakdown:

Option 1: Transitive dependencies from another library #

While you only explicitly added JUnit 4.10, another dependency in your project (maybe a course-provided utility library, or a hidden plugin) might be pulling in ScalaTest as a transitive dependency. sbt automatically resolves and adds these indirect dependencies to your test classpath, so you don’t have to list them manually.

Option 2: sbt’s automatic test framework dependency injection #

If your build.sbt includes a line specifying ScalaTest as the test framework (even if you missed it), sbt will automatically add the required ScalaTest dependencies behind the scenes. Look for something like this in your build file:

testFrameworks += new TestFramework("org.scalatest.tools.Framework")

When you declare a test framework, sbt knows exactly which libraries are needed to run tests with that framework and adds them without you having to write out scalatest in libraryDependencies.

Option 3: Hidden plugin or template defaults #

Many Scala project templates (like those used in courses or IDE-generated projects) include plugins such as sbt-scalatest by default. These plugins automatically configure ScalaTest dependencies and settings for you, so you don’t have to define them explicitly.

To confirm exactly where ScalaTest is coming from, run this sbt command to see your full test dependency tree:

sbt test:dependencyTree

This will show all direct and transitive dependencies in your test scope, pointing you right to the source of the ScalaTest jars.

内容的提问来源于stack exchange，提问作者Polymerase