You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
There is a project containing both legacy (spec2) tests and new scalatest tests.
gradle-scalatest plugin with append mode made it possible to run legacy tests with "gradle test" and the new scalatest tests with "gradle scalatest".
looks like gradle-scoverage plugin runs "test" task to measure coverage.
is it possible to change gradle test task name to be run by gradle-scoverage task?
or is it possible to create multiple scoverage tasks like this:
reportScoverage -> test
reportScalatestScoverage -> scalatest
thanks!!
there is some discussion here #77
but looks like no clear solution is available
The text was updated successfully, but these errors were encountered:
The new release (3.0.0) of this plugin does now run the test task to measure coverage, but it sounds like you want to be able to measure the coverage that results from running both sets of tests?
If so you might try the following snippet (modified from org/scoverage/ScoveragePlugin.groovy:203):
Hi!
There is a project containing both legacy (spec2) tests and new scalatest tests.
gradle-scalatest plugin with append mode made it possible to run legacy tests with "gradle test" and the new scalatest tests with "gradle scalatest".
looks like gradle-scoverage plugin runs "test" task to measure coverage.
is it possible to change gradle test task name to be run by gradle-scoverage task?
or is it possible to create multiple scoverage tasks like this:
reportScoverage -> test
reportScalatestScoverage -> scalatest
thanks!!
there is some discussion here
#77
but looks like no clear solution is available
The text was updated successfully, but these errors were encountered: