ScalaCheck issue (w/ junitxml?) in 3.6.4, not present in 2.4.2

[ach...@box.com]

My project has some simple ScalaCheck tests, and when I use 2.4.2 everything runs fine. However, when I use 3.6.4, I get

java.lang.Exception: Invalid ScalaCheck args: List(junitxml, console)

Maybe this is a ScalaCheck issue, but wondering if maybe something changed in Specs2? Ideally I would not have to alter the build too much as this is eventually sent to Jenkins which I'm guessing uses junitxml.

Thanks!

[etorreborre]

This looks like a sbt configuration issue.

You must be passing test arguments to all frameworks whereas you need to be specific:

testOptions in Test += Tests.Argument(TestFrameworks.Specs2, "junitxml", "console")

I suspect that some earlier version of ScalaCheck was not checking its arguments.

Eric

[Kenji Yoshida]

fixed in master branch https://github.com/rickynils/scalacheck/commit/061ccd0f4798ab

[ach...@box.com]

@etorreborre, I copy/pasted that into my build.sbt, same error. This is on Specs2 3.6.

[etorreborre]

That's weird because you seem to have the same issue as the one described here: https://github.com/rickynils/scalacheck/issues/173.

And the solution was indeed to specify the specs2 args only for the specs2 framework in sbt. 

Since this seems to be a regression from 1.12.1 to 1.12.3 maybe you can also try to downgrade your ScalaCheck version to 1.12.1?

[ach...@box.com]

So doing

testOptions in Test += Tests.Argument(TestFrameworks.Specs2, "junitxml", "console")

worked - I hadn't realized that there were similar settings (albeit with TestFrameworks.Specs2 omitted) in the top-level build configuration. Changing that fixed the issue. Thanks!

[etorreborre]

Great!