Hi,
JaCoCo code coverage typically only adds a few percent of runtime
overhead to test execution. I recommend studiying your build logs to
understand what is going on when invoked with different build goals.
There is a separate goal for report-integration, see documentation:
http://eclemma.org/jacoco/trunk/doc/report-integration-mojo.html
Regards,
-marc
On 02.04.16 14:58, [email protected] wrote:
Thanks for answer!
I use maven lifecycle and it worked but in CI cloud test run time was doubled
(before it was 55 min now 1 hour 45 min).
what do you mean by saying "specify
another goal for report generation (jacoco:report-integration) "? Can you
please specify how it should be done?
Thanks!
On Tuesday, March 29, 2016 at 6:12:24 PM UTC+2, Marc R. Hoffmann wrote:
Hi,
if you execute
mvn failsafe:integration-test
than exactly this goal is executed -- nothing else. You can specify
another goal for report generation (jacoco:report-integration) or use
the Maven lifecycle to execute multiple goals
(https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html).
Regards,
-marc
On 2016-03-29 17:20, wrote:
Hi all,
We are running integration test with failsafe maven plugin with a
command "mvn failsafe:integration-test".
When I am running test with mvn failsafe:integration-test command the
report is not generated, but when I am running with mvn verify with
integration test specific profile it generates fine.
Do you have any experience how to run tests with mvn
failsafe:integration-test command and generate JaCoCo report properly?
Thanks!
--
You received this message because you are subscribed to the Google Groups "JaCoCo
and EclEmma Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jacoco/5702003E.1000004%40mountainminds.com.
For more options, visit https://groups.google.com/d/optout.
