apache / apache/grails-intellij-plugin
Grails unit test code coverage is not shown in coverage result report even though editor gutter shows that the line was covered
- Dominant language
- Java
- Stars
- 17
- Forks
- 4
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 4
Description
When I run all unit tests written in spock (test-app unit: -echoOut) with code coverage for my grails application the coverage report shows that it did not cover any of the classes which supposed to be tested.
Grails version is 2.4.3 (the fork did not work, and excluding/including packages had no effect)
For the completely new project with fork disabled I still do not see coverage
After cleaning the sample project and rebuilding it again - the coverage showed up correctly.
Doing the same thing with initial project did not yield the same result - it still shows 0% of class coverage.
It is a project that has an inplacePlugin (I have also disable fork there) and several non-public plugins - so it might be hard to send it over.
Any other ideas how to diagnose what might be wrong or diffrent then it should be?
I have done everything - the problem is reproduced on other computers so it is not a singular problem. After everything done I have the following situation:
1) No code coverage on every of written classes
2) When I open the src file I get code coverage markers for each line
which was covered or not - as on the screenshot
Project View does not show anything concerning coverage. Coverage view shows that packages were not covered **even thou the gutter
shows something different.**
---
*Imported from [IDEA-137828](https://youtrack.jetbrains.com/issue/IDEA-137828) · Type: Bug · Votes: 1*
*Comments, attachments, dates and reporter are not part of the export — follow the link above for the full history.*
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the imported IDEA-137828 report and reproduce the issue by running the Spock unit tests with `test-app unit: -echoOut` and code coverage. Compare the coverage result report with the editor gutter markers, including in the project with an inplacePlugin and fork disabled. Done means covered classes and packages appear in the report consistently with the gutter results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100