-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tests and project in two modules #39
Comments
Thanks - yes, from running with I agree that even if I add some inputs to make it run, it still doesn't work. I'll take a closer look at this tomorrow if that's ok? |
👍 |
I have different message:
|
It seems like |
Sorry, I've been away the past few days. Yes, there's something strange going on. I think that we see the testScoverage task being linked to the testScoverage sourceset, which is empty. I wonder if this occurs because we configure the build twice, once for all subprojects and then again for the test subprojects. A workaround might be to manually set the testClassesDir: testScoverage { I think this runs the tests, I'll try to put together a pull request with a better fix for your branch over the weekend. |
Thanks, I'll check this workaround for now. |
Where should I apply this config for |
On review I think that the testClassesDir is insufficient to achieve coverage - it's also necessary to include the instrumented classes from project 'a'. I've updated Kwestor#1 to add an additional task supporting this. I can merge this to the main repository if you agree that it's ok? |
Unfortunately I have another issue: if you have a source files in This time it's a problem with Travis tests passes because if you join two absolute paths on Linux it creates correct path to non-existing file. On windows this path is incorrect, as it have a drive letter in the middle. |
@maiflai do you know an easy way of excluding files in |
Sorry for the lack of comms, I've been away from the computer for the past week or so. re: the HTML path issue, I thought this was resolved, I'll take a closer look this week. I think excluding files from coverage can be done either at the file or the class level: // behaviour of scalac plugin is detailed in scoverage.RegexCoverageFilterTest
scoverage {
excludedFiles = [ 'path/to/file.scala', 'path/to/another/file.scala' ]
excludedPackages = [ 'path.to.* ]
}
|
I think we should move conversation from scoverage/scalac-scoverage-plugin#79, here, as it's more about gradle configuration now, and not about changes to plugin.
@maiflai I tested sample project from gradle samples and while it seems to work (report is generated and classes in report are ok), I believe this report is invalid, as it states 0% coverage.
I included
separate-tests
in my fork ofgradle-scoverage
and wrote an acceptance test for it, could you please take a look?The text was updated successfully, but these errors were encountered: