grails test-app -coverage不包括分支模式下的功能测试的范围

Question

I'm having trouble understanding Grails forked mode and how it's impacting the code coverage reports when I'm running grails test-app -coverage . I am using Grails 2.3.1.

I turned off forked mode for the test configuration

grails.project.fork = [... test: false  ... ]

And unit tests show up in the coverage report.

However, coverage from functional tests is NOT included in the Cobertura output.

If I turn off forked mode for the run option as well, then I do get coverage from functional tests in the Cobertura report.

Questions:

• why does forked mode for run impact the coverage output? aren't the same instrumented classes also deployed to the embedded Tomcat?

• is there a way to use forked mode normally for run-app, but not when launched incidental to test-app -functional for tests?

Answer 1

The problem should be reported at https://github.com/beckje01/grails-code-coverage/issues .

Yes, there is a way to use forked mode for run-app but not for test-app. In BuildConfig.groovy you can do something like this:

grails.project.fork = [
    test: false,
    run: [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256, forkReserve:false],
    war: [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256, forkReserve:false],
    console: [maxMemory: 768, minMemory: 64, debug: false, maxPerm: 256]
]

That probably doesn't affect functional tests in the way that you want, but does affect other tests.

EDIT:

See https://github.com/beckje01/grails-code-coverage/issues/11

That probably doesn't help with functional tests and may need to be addressed as a separate problem.