为什么scalatest会混淆输出?

时间:2012-03-20 06:29:38

标签: scala sbt scalatest

我从sbt运行我的scalatest,输出变得混乱 - scalatest打印所有测试运行,并对它们发表评论,并在中间某处打印统计信息:

> test
[info] Compiling 1 Scala source to /home/platon/Tor/scala-dojo-02/target/scala-2.9.1/classes...
[info] FunsWithListsTests:
[info] - should return list of labels
[info] - should return the average rating of games belonging to Zenga
[info] - should return the total ratings of all games
[info] - should return the total ratings of EA games *** FAILED ***
[info]   0 did not equal 170 (FunsWithListsTests.scala:35)
[error] Failed: : Total 8, Failed 5, Errors 0, Passed 3, Skipped 0
[info] - should increase all games rating by 10 *** FAILED ***
[error] Failed tests:
[error]     dojo.FunsWithListsTests
[info]   List() did not equal List(Game(Activision,40), Game(Zenga,70), Game(Zenga,20), Game(EA,70), Game(EA,120)) (FunsWithListsTests.scala:40)
[info] - should decrease all Zenga games rating by 10 *** FAILED ***
[info]   List() did not equal List(Game(Activision,30), Game(Zenga,50), Game(Zenga,0), Game(EA,60), Game(EA,110)) (FunsWithListsTests.scala:45)
[info] - should create function to find Activision games *** FAILED ***
[info]   List(Game(Activision,30), Game(Zenga,60), Game(Zenga,10), Game(EA,60), Game(EA,110)) did not equal List(Game(Activision,30)) (FunsWithListsTests.scala:50)
[info] - should return a List of tuples consisting of game label and game *** FAILED ***
[info]   List() did not equal List((ACTIVISION,Game(Activision,30)), (ZENGA,Game(Zenga,60)), (ZENGA,Game(Zenga,10)), (EA,Game(EA,60)), (EA,Game(EA,110))) (FunsWithListsTests.scala:56)
[error] {file:/home/platon/Tor/scala-dojo-02/}default-940f03/test:test: Tests unsuccessful
[error] Total time: 1 s, completed Mar 20, 2012 9:27:13 AM

似乎如果我要积累大量的测试,搜索这些统计数据和失败的测试将会变得很痛苦。

有没有办法解决这个问题?

2 个答案:

答案 0 :(得分:7)

在我看来,原因是SBT默认情况下并行执行测试,就像maven-surefire-plugin一样。

正如ScalaTest wiki中所解释的那样,这可以通过以下方式解决:

禁用并行执行测试 默认情况下,sbt并行运行所有任务。由于每个测试都映射到一个任务,因此默认情况下测试也会并行运行。要禁用并行执行测试:

测试中的

parallelExecution:= false

答案 1 :(得分:1)

遇到同样的问题并通过将日志保存到单独的文件中来解决它。不理想,但对CI有好处,特别是在长期集成测试的情况下。我是怎么做到的:

  1. 为日志创建一个特殊目录(例如,在build.sbt的末尾):

    lazy val logDirectory = taskKey[File]("A directory for logs")
    logDirectory := {
      val r = target.value / "logs"
      IO.createDirectory(r)
      r
    }
    
  2. [可选]指定项目中摘要信息的文件:

    testOptions in test += Tests.Argument(
      TestFrameworks.ScalaTest, "-fW", (logDirectory.value / "summary.log").toString
    )
    

    W禁用颜色

  3. 为每个测试创建一个组。每个组必须在具有特殊参数的分叉JVM中运行测试:

    testGrouping in test := testGrouping.value.flatMap { group =>
      group.tests.map { suite =>
        val fileName = {
          // foo.bar.baz.TestSuite -> f.b.b.TestSuite
          val parts = suite.name.split('.')
          (parts.init.map(_.substring(0, 1)) :+ parts.last).mkString(".")
        }
    
        val forkOptions = ForkOptions(
          bootJars = Nil,
          javaHome = javaHome.value,
          connectInput = connectInput.value,
          outputStrategy = outputStrategy.value,
          runJVMOptions = javaOptions.value ++ Seq(
            "-Dour.logging.appender=FILE",
            s"-Dour.logging.dir=${logDirectory.value / fileName}"
          ),
          workingDirectory = Some(baseDirectory.value),
          envVars = envVars.value
        )
    
        group.copy(
          name = suite.name,
          runPolicy = Tests.SubProcess(forkOptions),
          tests = Seq(suite)
        )
      }
    }
    

    注意,我们可以通过 our.logging.appender our.logging.dir

  4. 告诉我们我们保存日志的日志。
  5. 创建日志记录配置(test / resources / logback-test.xml):

    <?xml version="1.0" encoding="UTF-8"?>
    <configuration>
        <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">
            <target>System.out</target>
            <encoder>
                <pattern>%date{yyyy-MM-dd HH:mm:ss} %-5level [%thread] %logger{26} - %msg%n</pattern>
            </encoder>
        </appender>
    
        <appender name="FILE" class="ch.qos.logback.core.FileAppender">
            <file>${our.logging.dir}/test.log</file>
            <append>false</append>
            <encoder>
                <pattern>%date{yyyy-MM-dd HH:mm:ss.SSS} %-5level [%thread] %logger{26} - %msg%n</pattern>
            </encoder>
        </appender>
    
        <root level="TRACE">
            <appender-ref ref="${our.logging.appender}"/>
        </root>
    </configuration>
    
  6. 就是这样。