Mockito scala验证测试不起作用(播放框架)

时间:2013-09-05 13:31:59

标签: scala playframework mockito

我正在尝试使用Scala中的Play框架进行单元测试。 我写了一个类来检查配置是否正确(我有更多的错误处理,但我实际上现在使用此代码进行测试):

class TaskQueueConfig(conf: Configuration) {
  val schedulingEnabled = conf.getBoolean("schedulingEnabled").get
  val processingEnabled = conf.getBoolean("processingEnabled").get
  val queueName = conf.getString("queue").get
}

我正在使用play 2.1.1的默认测试设置进行测试:

class ConfigTestSpec extends Specification with Mockito with CalledMatchers {
  "TaskQueueConfig" should {
     "verify calls" in {
      val tqConf = mock[Configuration]
      tqConf.getString("queue") returns Some("queueName")
      tqConf.getBoolean("schedulingEnabled") returns Some(true)
      tqConf.getBoolean("processingEnabled") returns Some(true)
      Logger.error("setup done")

      val config = new TaskQueueConfig(tqConf)

      there was one(tqConf).getString("queue")
      there were two(tqConf).getBoolean(any[String])
      there were one(tqConf).getBoolean("schedulingEnabled")
      there were one(tqConf).getBoolean("processingEnabled")
    }
  }
}

我收到以下错误:

[error] x verify calls
[error]    The mock was not called as expected:
[error]    configuration.getString$default$2();
[error]    Wanted 1 time:
[error]    -> at config.ConfigTestSpec$$anonfun$2$$anonfun$apply$4$$anonfun$apply$12.apply(ConfigTestSpec.scala:61)
[error]    But was 2 times. Undesired invocation:
[error]    -> at config.TaskQueueConfig.<init>(TaskQueueConfig.scala:10) (ConfigTestSpec.scala:61)

这很奇怪,因为代码非常孤立,在TaskQueueConfig中显然只有1个conf.getString调用。第10行是带有getString方法的行。第61行是“有一个(tQConf).getString”

的行

如何解决此问题?

(是和之间没有区别。)

PS:我知道这个例子对于测试来说是无用的,但我有更复杂的配置,其中有一些规则需要测试。

更新1 getString方法有两个参数,第二个参数的默认值为None(它的类型是Option [Set [String]])。当我明确地将None添加到设置和验证时,它仍然不起作用。但是,当我添加null时,我会让它发挥作用。

  val tqConf = mock[Configuration]

  tqConf.getString("queue", null) returns Some("queueName")
  tqConf.getBoolean("schedulingEnabled") returns Some(true)
  tqConf.getBoolean("processingEnabled") returns Some(true)

  val c = new TaskQueueConfig(tqConf)

  there was one(tqConf).getString("queue", null)
  there was one(tqConf).getString(any[String], any[Option[Set[String]]])
  there were two(tqConf).getBoolean(any[String])
  there was one(tqConf).getBoolean("schedulingEnabled")
  there was one(tqConf).getBoolean("processingEnabled")

  c.processingEnabled must beTrue
  c.schedulingEnabled must beTrue
  c.queueName must be("queueName")

所以我想现在的问题是,为什么我必须使用null?

1 个答案:

答案 0 :(得分:4)

您必须在双参数null调用中使用getString(),因为Mockito要求您使用所有参数的使用匹配器或 none < / em>的。

因此将"queue"(文字)与any[Option[Set[String]]](匹配器)混合起来是行不通的。 有时 Mockito可以解决你已经完成的事情并且它会给你一个错误,但看起来你在这里很不走运......

尝试在所有位置使用匹配器:

tqConf.getString(org.mockito.Matchers.eq("queue"), any[Option[Set[String]]]) returns Some("queueName")

验证:

there was one(tqConf).getString(eq("queue"), any[Option[Set[String]]])