Question

我最近在项目中添加了对Specs2的依赖，并注意到一些用ScalaTest和Mockito编写的现有测试失败了。删除Specs2后，这些测试再次通过。为什么会这样？

lazy val scalatestandspecscoexisting = Project(
  id = "scalatest-and-specs-coexisting",
  base = file("."),
  settings = Project.defaultSettings ++
    GraphPlugin.graphSettings ++
    Seq(
    name := "Scalatest-And-Specs-Coexisting",
    organization := "com.bifflabs",
    version := "0.1",
    scalaVersion := "2.9.2",
//  libraryDependencies ++= Seq(scalaTest, mockito)   //Tests Pass, no-specs2
    libraryDependencies ++= Seq(scalaTest, specs2, mockito)  //Tests Fail
  )
)

所有使用Mockito失败的测试都设置了一个带有两个不同参数的模拟方法。对mock的调用之一不会返回它设置的值。以下示例失败。另一个要求是类型必须是Function1（或具有apply方法）。

import org.scalatest.FunSuite
import org.scalatest.mock.MockitoSugar
import org.mockito.Mockito.when

trait MockingBird {
  //Behavior only reproduces when input is Function1
  def sing(input: Set[String]): String
}

class MockSuite extends FunSuite with MockitoSugar {

  val iWannaRock = Set("I wanna Rock")
  val rock = "Rock!"

  val wereNotGonnaTakeIt = Set("We're not gonna take it")
  val no = "No! We ain't gonna take it"

  test("A mock should match on parameter but isn't") {

    val mockMockingBird = mock[MockingBird]
    when(mockMockingBird.sing(iWannaRock)).thenReturn(rock)
    //Appears to return this whenever any Set is passed to sing
    when(mockMockingBird.sing(wereNotGonnaTakeIt)).thenReturn(no)

    // Succeeds because it was set up last
    assert(mockMockingBird.sing(wereNotGonnaTakeIt) === no)
    // Fails because the mock returns "No! We ain't gonna take it"
    assert(mockMockingBird.sing(iWannaRock) === rock)
  }
}

输出：

 [info] MockSuite:
 [info] - A mock should match on parameter but isn't *** FAILED ***
 [info]   "[No! We ain't gonna take it]" did not equal "[Rock!]" (MockSuite.scala:38)
 [error] Failed: : Total 1, Failed 1, Errors 0, Passed 0, Skipped 0

Answer 1

编辑 - 根据Eric的评论，这是Specs2≤1.12.2中的错误。应该在1.12.3中修复。

事实证明，Specs2重新定义了Mockito中的一些行为，以便获取匹配的名字参数。

Eric answered my question

“我不喜欢这个，但这是我找到匹配的唯一方法参数：http://bit.ly/UF9bVC。你可能想要那个。“

来自Specs2文档

Byname

可以验证Byname参数，但如果specs2，这将不起作用   在mockito jar之前，jar不会放在类路径上。确实   specs2重新定义了一个Mockito类来拦截方法调用，以便这样做   byname参数得到妥善处理。

为了让我的测试再次通过，我做了与specs2文档中建议相反的操作，并在 Mockito之后添加了Specs2依赖。我没试过，但我希望通过名字参数匹配失败。

lazy val scalatestandspecscoexisting = Project( id = "scalatest-and-specs-coexisting", base = file("."), settings = Project.defaultSettings ++ GraphPlugin.graphSettings ++ Seq( name := "Scalatest-And-Specs-Coexisting", organization := "com.bifflabs", version := "0.1", scalaVersion := "2.9.2", // libraryDependencies ++= Seq(scalaTest, mockito) //Tests Pass libraryDependencies ++= Seq(scalaTest, mockito, specs2) //Tests Pass // libraryDependencies ++= Seq(scalaTest, specs2, mockito) //Tests Fail ) )

我的测试现在通过了

[info] MockSuite: [info] - A mock should match on parameter but isn't [info] Passed: : Total 1, Failed 0, Errors 0, Passed 1, Skipped 0

当我在Specs2上添加依赖项时，为什么我的一些使用Mockito的ScalaTest测试失败？

1 个答案: