Zero coverage with IntelliJ IDEA: Grails with Spock unit tests

Question

I am trying to configure code coverage reporting for our Grails application when running Spock-based unit tests. I am able to generate the reports, but the coverage is 0.

I have tried playing with various options (e.g. Sampling vs. Tracing), but the results are always the same: the total number of classes/methods/lines shown is correct, but the coverage is always 0, e.g.:

Class,%: 0%(0/2)

Method,%: 0%(0/4)

Line,%: 0%(0/16)

Which is clearly bogus, since the relevant code can be modified in such a way that the tests fail.

The setup:

OS X Yosemite 10.10.2
IntelliJ IDEA Ultimate 14.1.3
Grails 2.4.4
Spock 0.7
Groovy 2.4.3
Java 1.8.0-31

score 2 · Answer 1 · edited May 23 '17 at 11:59

2

I wrote to JetBrains support and they pointed me to the following issue:

https://youtrack.jetbrains.com/issue/IDEA-137285

In short, the resolution is to specify

grails.project.fork = [
  test: false
]

in BuildConfig.groovy .

Also, see IntelliJ IDEA Debugger isn't working on a Grails Project - there is some useful info there on when/how/why use fork mode.

edited May 23 '17 at 11:59

Community

1
1

answered Jul 23 '15 at 15:45

malenkiy_scot

16,415
6
64
87

This will slow down your test case execution tremendously in some scenarios. I am currently facing the slowness issue after this. – Vinay Prajapati Dec 17 '15 at 10:09

score 1 · Answer 2 · answered Jul 23 '15 at 09:47

1

I also faced similar problem couple of months back. I was using STS and written Spock based test cases.

The plugin for the code coverage which you are using is not considering Spock based test cases as the actual test cases. It considers only JUinit test cases.

So the solution here would be look for other code coverage plugin compatible with IntelliJ. I couldn't suggest you the plugin which I used for STS since It may or may not work well for IntelliJ.

I hope at-least I made it clear what's the problem.

answered Jul 23 '15 at 09:47

Santosh Anantharamaiah

273
4
21

Thanks! I've submitted this question to JetBrains support. If they indeed verify that this is the problem I'll accept your answer. – malenkiy_scot Jul 23 '15 at 15:30
Got an answer from JetBrains - disabling forking does the trick – malenkiy_scot Jul 23 '15 at 15:46
Perfect. Will check in STS for the similar scenario with my old plugin. But end of the day it was the problem with the IDE. Cool. – Santosh Anantharamaiah Jul 23 '15 at 15:50

score 1 · Answer 3 · answered Nov 26 '15 at 14:05

I ran into this error today. I eventually found that you should not use "run application with coverage" from the toolbar, but "Run 'Test in 'application'' with Coverage" from the project context menu.

When you run a test in IntelliJ, a JUnit test is created in the 'Run/Debug Configurations' these can be used from the toolbar (e.g. for re-running).

Zero coverage with IntelliJ IDEA: Grails with Spock unit tests

3 Answers3