anchor.diff:    <artifactId>quarkus-jacoco</artifactId>
     <scope>test</scope>
   </dependency>
  +----
  +
  +If you are using Gradle, add this to your `build.gradle`:
  +
  +[source,gradle]
  +----
  +testImplementation 'io.quarkus:quarkus-jacoco'
   ----
   
   This Quarkus extension takes care of everything that would usually be done via the Jacoco maven plugin, so no additional
  
positive.code: WARNING: This config will only work if at least one `@QuarkusTest` is being run. If you are not using `@QuarkusTest` then
  you can simply use the Jacoco plugin in the standard manner with no additional config.
  
  === Coverage for Integration Tests
  
  To get code coverage data from integration tests, the following need to be requirements need to be met:
  
negative.code: </build>
  ----
  
  If you are using Gradle, add this to your `build.gradle`:
  
  [source, gradle]
  ----
  jacocoTestCoverageVerification {
      executionData.setFrom("$project.buildDir/jacoco-quarkus.exec")
      violationRules {
          rule {
              limit {
                  counter = 'INSTRUCTION'
                  value = 'COVEREDRATIO'
                  minimum = 0.80
              }
              limit {
                  counter = 'BRANCH'
                  value = 'COVEREDRATIO'
                  minimum = 0.72
              }
          }
      }
  }
  check.dependsOn jacocoTestCoverageVerification
  ----
  
  Excluding classes from the verification task can be configured as following: 
  
  [source,gradle]
  ----
  jacocoTestCoverageVerification {
      afterEvaluate { <1>
          classDirectories.setFrom(files(classDirectories.files.collect { <2>
              fileTree(dir: it, exclude: [
                      "org/example/package/**/*" <3>
              ])
          }))
      }
  }
  ----
  <1> `classDirectories` needs to be read after evaluation phase in Gradle
  <2> Currently, there is a bug in Gradle JaCoCo which requires the `excludes` to be specified in this manner - https://github.com/gradle/gradle/issues/14760.  Once this issue is fixed, excludes
  <3> Exclude all classes in `org/example/package` package
  
  
  == Conclusion
  
  You now have all the information you need to study the coverage of your tests!
  