Getting Skipping JaCoCo execution due to missing execution data file upon executing JaCoCo

Question

I m using Maven 3 0 3  JUnit 4 8 1  and Jacoco 0 6 3 201306030806  and I am trying to create test coverage reports   I have a project with unit tests only  but I can t get reports to run  I m repeatedly getting the error  Skipping JaCoCo execution due to missing execution data file when I run   mvn clean install -P test-coverage   Here is how my pom is configured    lt plugin gt     lt groupId gt org apache maven plugins lt  groupId gt     lt artifactId gt maven-surefire-plugin lt  artifactId gt     lt version gt 2 14 1 lt  version gt     lt configuration gt       lt reuseForks gt true lt  reuseForks gt       lt argLine gt -Xmx2048m lt  argLine gt     lt  configuration gt   lt  plugin gt   lt plugin gt     lt groupId gt org apache maven plugins lt  groupId gt     lt artifactId gt maven-failsafe-plugin lt  artifactId gt     lt version gt 2 14 1 lt  version gt     lt configuration gt       lt reuseForks gt true lt  reuseForks gt       lt argLine gt -Xmx4096m -XX MaxPermSize 512M   itCoverageAgent  lt  argLine gt     lt  configuration gt     lt executions gt       lt execution gt         lt goals gt           lt goal gt integration-test lt  goal gt           lt goal gt verify lt  goal gt         lt  goals gt       lt  execution gt     lt  executions gt   lt  plugin gt       lt profile gt     lt id gt test-coverage lt  id gt     lt build gt       lt plugins gt         lt plugin gt           lt groupId gt org jacoco lt  groupId gt           lt artifactId gt jacoco-maven-plugin lt  artifactId gt           lt version gt 0 6 3 201306030806 lt  version gt           lt configuration gt             lt destfile gt   basedir  target coverage-reports jacoco-unit exec lt  destfile gt             lt datafile gt   basedir  target coverage-reports jacoco-unit exec lt  datafile gt           lt  configuration gt           lt executions gt             lt execution gt               lt id gt prepare-unit-tests lt  id gt               lt goals gt                 lt goal gt prepare-agent lt  goal gt               lt  goals gt             lt  execution gt             lt  -- prepare agent for measuring integration tests -- gt             lt execution gt               lt id gt prepare-integration-tests lt  id gt               lt goals gt                 lt goal gt prepare-agent lt  goal gt               lt  goals gt               lt phase gt pre-integration-test lt  phase gt               lt configuration gt                 lt propertyName gt itCoverageAgent lt  propertyName gt               lt  configuration gt             lt  execution gt             lt execution gt               lt id gt jacoco-site lt  id gt               lt phase gt verify lt  phase gt               lt goals gt                 lt goal gt report lt  goal gt               lt  goals gt             lt  execution gt           lt  executions gt         lt  plugin gt       lt  plugins gt     lt  build gt   lt  profile gt    All my tests run successfully  Here is some of the output from Maven    INFO  --- jacoco-maven-plugin 0 6 2 201302030002 prepare-agent  prepare-unit-tests    myproject ---  INFO  argLine set to -javaagent  Users davea  m2 repository org jacoco org jacoco agent 0 6 2 201302030002 org jacoco agent-0 6 2 201302030002-runtime jar destfile  Users davea Dropbox workspace myproject target jacoco exec  INFO           Tests run  14  Failures  0  Errors  0  Skipped  0   INFO           INFO    INFO  --- jacoco-maven-plugin 0 6 2 201302030002 prepare-agent  prepare-integration-tests    myproject ---  INFO  itCoverageAgent set to -javaagent  Users davea  m2 repository org jacoco org jacoco agent 0 6 2 201302030002 org jacoco agent-0 6 2 201302030002-runtime jar destfile  Users davea Dropbox workspace myproject target jacoco exec   INFO    INFO  --- maven-failsafe-plugin 2 14 1 integration-test  default    myproject ---  WARNING  File encoding has not been set  using platform encoding MacRoman  i e  build is platform dependent   INFO    INFO  --- maven-failsafe-plugin 2 14 1 verify  default    myproject ---  INFO  Failsafe report directory   Users davea Dropbox workspace myproject target failsafe-reports  WARNING  File encoding has not been set  using platform encoding MacRoman  i e  build is platform dependent   INFO    INFO  --- jacoco-maven-plugin 0 6 2 201302030002 report  jacoco-site    myproject ---  INFO  Skipping JaCoCo execution due to missing execution data file  INFO     Any ideas what configuration I m missing

User · Answer

There might a case where some other argline setup or plugin in pom may be overriding jacoco execution order setup.

argLine set to -javaagent:/Users/davea/.m2/repository/org/jacoco/org.jacoco.agent/0.6.2.201302030002/org.jacoco.agent-0.6.2.201302030002-runtime.jar=destfile=/Users/davea/Dropbox/workspace/myproject/target/jacoco.exec

One of the example

           <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-surefire-plugin</artifactId>
                <version>2.16</version>
                <configuration>
                    <forkCount>5</forkCount>
                    <reuseForks>true</reuseForks>
                    <argLine>-Dnet.sf.ehcache.disabled=true</argLine>
                </configuration>
            </plugin>

After getting rid of argLine from these plugins, jacoco started to work normally.

User · Answer

FWhat tdrury said   change your plugin configuration into this    lt plugin gt       lt groupId gt org jacoco lt  groupId gt       lt artifactId gt jacoco-maven-plugin lt  artifactId gt       lt version gt 0 6 3 201306030806 lt  version gt       lt executions gt         lt  -- prepare agent for measuring integration tests -- gt         lt execution gt           lt id gt prepare-integration-tests lt  id gt           lt phase gt pre-integration-test lt  phase gt           lt goals gt             lt goal gt prepare-agent lt  goal gt           lt  goals gt           lt configuration gt             lt destFile gt   basedir  target coverage-reports jacoco-unit exec lt  destFile gt           lt  configuration gt         lt  execution gt         lt execution gt           lt id gt jacoco-site lt  id gt           lt phase gt post-integration-test lt  phase gt           lt goals gt             lt goal gt report lt  goal gt           lt  goals gt           lt configuration gt             lt dataFile gt   basedir  target coverage-reports jacoco-unit exec lt  dataFile gt           lt  configuration gt         lt  execution gt       lt  executions gt     lt  plugin gt    Edit  Just noticed one important thing  destFile and dataFile seems case sensitive so it s supposed to be destFile  not destfile

User · Answer

I have added a Maven Java project with 1 Domain class with the following features     Unit or Integration testing with the plugins Surefire and Failsafe   Findbugs  Test coverage via Jacoco    Where are the Jacoco results  After testing and running  mvn clean   you can find the results in  target site jacoco index html   Open this file in the browser   Enjoy   I tried to keep the project as simple as possible  The project puts many suggestions from these posts together in an example project  Thank you  contributors

User · Answer

Came accross the same problem just now   I have a class named HelloWorld  and I created a test class for it named HelloWorldTests  then I got the output Skipping JaCoCo execution due to missing execution data file    I then tried to change my pom xml to make it work  but the attempt failed    Finally  I simply rename HelloWorldTests to HelloWorldTest  and it worked   So I guess that  by default  jacoco only recognizes test class named like XxxTest  which indicates that it s the test class for Xxx  So simply rename your test classes to this format should work

User · Answer

Sometimes the execution runs first time  and when we do maven clean install it doesn t generate after that  The issue was using true for skipMain and skip properties  under maven-compiler-plugin of the main pom File  Remove them if they were introduced as a part of any issue or suggestion

User · Answer

I ve tried all answers but only the following combination of advice has worked for me  Why  I had very specific requirements    JaCoCo generates report when build is run from command line  mvn clean verify  Maven 3 6 0  Intellij IDEA  2019 01  runs my tests as well It all works in presence of another javaagent defined in surefire plugin   Solution - prepend argLine value in surefire configuration with  late replacement  maven property        as explained in surefire FAQ  my fixed configuration      How do I use properties set by other plugins in argLine    Maven does property replacement for               values in pom xml before any plugin is run  So Surefire would never see the place-holders in its argLine property    Since the Version 2 17 using an alternate syntax for these properties                allows late replacement of properties when the plugin is executed  so properties that have been modified by other plugins will be picked up correctly    Failed first try - define jaCoCoArgLine property in prepare-agent goal configuration of jacoco - the scenario failed my second requirement  IntelliJ IDEA couldn t figure out agent for jmockit I use in the project for static method mocking

User · Answer

The execution says it s putting the jacoco data in  Users davea Dropbox workspace myproject target jacoco exec but your maven configuration is looking for the data in   basedir  target coverage-reports jacoco-unit exec

User · Answer

One can also get  Skipping JaCoCo execution due to missing execution data file  error due to missing tests in project  For example when you fire up new project and have no  Test java files at all

User · Answer

My response is very late but for others users  In your case you have to configure failsafe pluging to use the command line agent configuration saved in itCoverageAgent variable  For exemple    lt configuration gt       lt argLine gt   itCoverageAgent  lt  argLine gt   lt  configuration gt    In your maven configuration  jacoco prepare the command line arguments in prepare-agent phase  but failsafe plugin doesn t use it so there is no execution data file

User · Answer

It happens if the path of your project has blank spaces somewhere  such as   home user my projects awesome project the report is not generated  If that is the case  remove those spaces from directory names  About the plugin configuration  I just needed the basic as below   lt plugin gt       lt groupId gt org jacoco lt  groupId gt       lt artifactId gt jacoco-maven-plugin lt  artifactId gt       lt version gt 0 8 5 lt  version gt       lt executions gt           lt execution gt               lt id gt jacoco-initialize lt  id gt               lt goals gt                   lt goal gt prepare-agent lt  goal gt               lt  goals gt           lt  execution gt           lt execution gt               lt id gt jacoco-report lt  id gt               lt goals gt                   lt goal gt report lt  goal gt               lt  goals gt           lt  execution gt       lt  executions gt          lt  plugin gt

User · Answer

I know this question is pretty old but if someone like me comes here looking for an answer then this might help  I have been able to overcome the above error with this   1  Remove the below piece of code from the plugin maven-surefire-plugin    lt reuseForks gt true lt  reuseForks gt    lt argLine gt -Xmx2048m lt  argLine gt    2  Add the below goal    lt execution gt   lt id gt default-prepare-agent lt  id gt   lt goals gt      lt goal gt prepare-agent lt  goal gt   lt  goals gt   lt  execution gt

User · Answer

When using the maven-surefire-plugin or maven-failsafe-plugin you must not use a forkCount of 0 or set the forkMode to never as this would prevent the execution of the tests with the javaagent set and no coverage would be recorded   ref  https   www eclemma org jacoco trunk doc maven html this is my gist

User · Answer

In my case  the prepare agent had a different destFile in configuration  but accordingly the report had to be configured with a dataFile  but this configuration was missing  Once the dataFile was added  it started working fine

User · Answer

I faced a bit of a different issue that returned the same error   Skipping JaCoCo execution due to missing execution data  target jacoco exec   The truth is  this error is returned for many  many reasons  We experimented with the different solutions on Stack Overflow  but found this resource to be best  It tears down the many different potential reasons why Jacoco could be returning the same error    For us  the solution was to add a prepare-agent to the configuration    lt execution gt      lt id gt default-prepare-agent lt  id gt      lt goals gt          lt goal gt prepare-agent lt  goal gt      lt  goals gt   lt  execution gt    I would imagine most users will be experiencing it for different reasons  so take a look at the aforementioned resource

User · Answer

Try to use   mvn jacoco report -debug   to see the details about your reporting process   I configured my jacoco like this    lt configuration gt       lt dataFile gt   jacoco exec lt  dataFile gt       lt outputDirectory gt   jacoco lt  outputDirectory gt   lt  configuration gt    Then mvn jacoco report -debug shows it using the default configuration  which means jacoco exec is not in   jacoco exec  The error says missing execution data file   So just use the default configuration    lt execution gt       lt id gt default-report lt  id gt       lt goals gt       lt  goals gt       lt configuration gt           lt dataFile gt   project build directory  jacoco exec lt  dataFile gt           lt outputDirectory gt   project reporting outputDirectory  jacoco lt  outputDirectory gt       lt  configuration gt   lt  execution gt    And everything works fine

User · Answer

I struggled for days  I tried all the different configurations suggested in this thread  None of them works  Finally  I find only the important configuration is the prepare-agent goal  But you have to put it in the right phase  I saw so many examples put it in the  pre-integration-test   that s a misleading  as it will only be executed after unit test  So the unit test won t be instrumented    The right config should just use the default phase   don t specify the phase explicitly   And usually  you don t need to mass around maven-surefire-plugin      lt plugin gt       lt groupId gt org jacoco lt  groupId gt       lt artifactId gt jacoco-maven-plugin lt  artifactId gt       lt version gt 0 8 4 lt  version gt       lt executions gt         lt execution gt           lt id gt default-prepare-agent lt  id gt           lt goals gt             lt goal gt prepare-agent lt  goal gt           lt  goals gt         lt  execution gt         lt execution gt           lt id gt jacoco-site lt  id gt           lt phase gt post-integration-test lt  phase gt           lt goals gt             lt goal gt report lt  goal gt           lt  goals gt         lt  execution gt       lt  executions gt     lt  plugin gt

User · Answer

jacoco-maven-plugin 0 7 10-SNAPSHOT  From jacoco prepare-agent that says      One of the ways to do this in case of maven-surefire-plugin - is to   use syntax for late property evaluation    lt plugin gt     lt groupId gt org apache maven plugins lt  groupId gt     lt artifactId gt maven-surefire-plugin lt  artifactId gt     lt configuration gt       lt argLine gt   argLine  -your -extra -arguments lt  argLine gt     lt  configuration gt   lt  plugin gt     Note the   argLine  that s added to -your -extra -arguments   Thanks Slava Semushin for noticing the change and reporting in the comment   jacoco-maven-plugin 0 7 2-SNAPSHOT  Following jacoco prepare-agent that says       org jacoco jacoco-maven-plugin 0 7 2-SNAPSHOT prepare-agent  Prepares a property pointing to the JaCoCo runtime agent that can be   passed as a VM argument to the application under test  Depending on   the project packaging type by default a property with the following   name is set          tycho testArgLine for packaging type eclipse-test-plugin and   argLine otherwise          Note that these properties must not be overwritten by the   test configuration  otherwise the JaCoCo agent cannot be attached  If   you need custom parameters please append them  For example    lt argLine gt   argLine  -your -extra -arguments lt  argLine gt        Resulting   coverage information is collected during execution and by default   written to a file when the process terminates    you should change the following line in maven-surefire-plugin plugin configuration from  note the   argLine  inside  lt argLine gt      lt argLine gt -Xmx2048m lt  argLine gt    to   lt argLine gt   argLine  -Xmx2048m lt  argLine gt    Make also the necessary changes to the other plugin maven-failsafe-plugin and replace the following  again  notice the   argLine      lt argLine gt -Xmx4096m -XX MaxPermSize 512M   itCoverageAgent  lt  argLine gt    to   lt argLine gt   argLine  -Xmx4096m -XX MaxPermSize 512M   itCoverageAgent  lt  argLine gt

[maven] Getting "Skipping JaCoCo execution due to missing execution data file" upon executing JaCoCo

Examples related to maven

Examples related to junit

Examples related to jacoco