With sbt-scoverage version 0.99.11, the unit tests can be run using scoverage:test. I didn't see any command under scoverage: to run integration tests though.
Grzegorz Slowikowski
unread,
Jun 11, 2015, 4:05:24 AM6/11/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to scala-code-c...@googlegroups.com
Hi
Why don't you upgrade to latest version and use "sbt coverage it:test"?
Regards Grzegorz
jie...@google.com
unread,
Jun 11, 2015, 12:56:57 PM6/11/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to scala-code-c...@googlegroups.com
The sbt-scoverge 1.0.0 and above gave me following compiling error:
[error] (common/compile:compile) scala.tools.nsc.interactive.RangePositions$ValidateException: Synthetic tree [228456] contains nonsynthetic tree [228438]" when I tried to run unit test with coverage enabled.
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to scala-code-c...@googlegroups.com
To be more specific, I am using Scala 2.10.4, SBT 0.13.2, coverageHighlighting := false, the sbt-scoverge 1.0.0 and above gave the compiling error:
[error] (common/compile:compile) scala.tools.nsc.interactive.RangePositions$ValidateException: Synthetic tree [228456] contains nonsynthetic tree [228438]" when I tried to run unit test with coverage enabled.
I tried Scala 2.10.5, SBT 0.13.7 with sbt-scoverage 1.0.1. The compiling error is still there.