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
As far as I can see there is no way to run scoverage for just a specific set of tests, just to either run scoverage for unit tests or integration tests. The test suite for my team's project takes 30 minutes to run altogether, so when I want to just check how the one Test class I am developing is changing scoverage, it would be much more efficient to be able to just run that one class.
If this feature already exists, I apologize and would be very grateful if someone pointed out to me how to use it.
The text was updated successfully, but these errors were encountered:
Take a look at the documentation of the available tasks, specifically reportScoverage. If you have multiple test tasks -- say, test and integrationTest -- you can run only the specific report task associated with each of them; for instance, reportIntegrationTestScoverage.
If you want to run only a specific test class, you can use the --tests technique. Note that you'll have to use the --tests argument with the test task rather than the report task, like so: gradle reportIntegrationTestScoverage integrationTest --tests *MySuite.
If you have a multi-module project, you'll need to use the tasks of the specific module you're after: gradle :myProjectA:reportIntegrationTestScoverage :myProjectA:integrationTest --tests *MyProjectASuite.
As far as I can see there is no way to run scoverage for just a specific set of tests, just to either run scoverage for unit tests or integration tests. The test suite for my team's project takes 30 minutes to run altogether, so when I want to just check how the one Test class I am developing is changing scoverage, it would be much more efficient to be able to just run that one class.
If this feature already exists, I apologize and would be very grateful if someone pointed out to me how to use it.
The text was updated successfully, but these errors were encountered: