Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsSome links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
To import JaCoCo coverage, generate a JaCoCo XML report after tests run, then give that report to the destination platform’s uploader or CI task. Do not upload JaCoCo’s binary .exec execution-data file in place of XML. Whether you can use JaCoCo XML directly depends on the destination: Codecov, Codacy, and Azure Pipelines document JaCoCo support, while GitHub Code Quality’s manual setup requires Cobertura XML.
Choose the report format and upload method first
JaCoCo XML is a report generated by analyzing execution data against compiled class files. The binary .exec file is an input to report generation, not a substitute for the XML report most dashboards consume. A platform’s ability to parse JaCoCo XML also does not guarantee that it will match your source paths or attach the result to the commit you expect.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
GameStop Physical Gift Card | $25.00 | Buy on Amazon |
| 2 |
|
Xbox Physical Gift Card | Buy on Amazon | |
| 3 |
|
$100 XBOX Gift Card [Digital Code] | $100.00 | Buy on Amazon |
| 4 |
|
Fortnite Physical Gift Card | $50.00 | Buy on Amazon |
| 5 |
|
$25 PlayStation Store Gift Card [Digital Code] | $25.00 | Buy on Amazon |
| Destination | Report format | Upload route |
|---|---|---|
| Codecov | JaCoCo XML is documented as supported. | Pass the report file to the Codecov CLI or configured uploader. |
| Codacy | JaCoCo XML; its docs identify Java reports matching jacoco*.xml. |
Coverage Reporter with the repository token and report path. |
| Azure Pipelines | XML; Microsoft documents JaCoCo and source-path mapping. | PublishCodeCoverageResults@2 in a build pipeline. |
| GitHub Code Quality | Cobertura XML in its current manual setup. | Convert JaCoCo XML to Cobertura, then use the documented upload action. |
Use the destination’s current documentation for authentication and workflow requirements. Choose native JaCoCo ingestion when it is documented; convert formats only when the destination requires it. Conversion adds another step where the report’s source paths must still correspond to the checked-out source.
Generate JaCoCo XML
Maven
Configure the JaCoCo Maven plugin to attach its agent during tests and generate a report afterward. The report goal produces HTML, XML, and CSV output; its documented default output directory is ${project.reporting.outputDirectory}/jacoco. In a standard Maven project, XML is commonly at target/site/jacoco/jacoco.xml, but custom build settings can change the path. The goal binds by default to verify, so a typical CI invocation is:
#1 Best Overall
- Redeemable at US GameStop, EB Games, Babbage's, Electronic Boutique, EBX, Planet X, and Software Etc. stores. Also redeemable online at and GameStop.com and EBGames.com.
- Over 6,100 stores located throughout the United States.
- GameStop. Power to the Players.
- Redemption: Instore and Online
- No returns and no refunds on gift cards.
mvn clean verify
Check the actual report location in your build rather than assuming the default. JaCoCo’s Maven plugin documentation, prepare-agent goal documentation, and report goal documentation describe setup and output. With Maven Surefire or Failsafe, settings such as forkCount=0 or forkMode=never prevent tests from running with the configured Java agent, so execution data is not recorded.
For a multi-module Maven project whose modules contribute to one result, consider JaCoCo’s report-aggregate goal, configured in the appropriate aggregator module. An aggregate report is useful when the destination expects one project-wide report; it does not remove the need to verify that all intended modules and class files are included.
Gradle
When the Java plugin is applied, Gradle’s JaCoCo plugin adds a jacocoTestReport task. XML is not enabled by default in the documented report configuration, and the report task does not depend on test automatically. Configure both explicitly, for example in build.gradle.kts:
Rank #2
- XBOX GIFT CARD: Buy full digital game downloads, game add-ons, in-game currency, memberships, devices, apps, movies, TV shows, and more.
- DIGITAL GAMES: Choose from hundreds of games, from AAA to indie options. Start playing the moment your most anticipated game is available when you pre-order and pre-download it.
- GAME AD-ONS: Extend the experience of your favorite games with add-ons and in-game currency.
- MOVIES & TV SHOWS: Rent or buy new and popular movies and TV shows from a massive library.
- PERFECT GIFT: Great as a gift for a friend or yourself. Xbox Gift Cards are easy to use, never expire, and give the freedom to pick the gift they want. Enjoy more ways to play without a credit card attached to your Microsoft account.
tasks.jacocoTestReport {
dependsOn(tasks.test)
reports {
xml.required = true
}
}
Then run the report task in CI:
./gradlew test jacocoTestReport
The Gradle JaCoCo plugin documentation covers task behavior, report configuration, and output. For Android, Kotlin, custom source sets, or variant-based builds, task names and paths can differ from a simple Java module. Inspect the tasks and build outputs for the variant you tested, and pass the resulting XML path to the uploader.
Upload the report to your destination
Codecov
Codecov lists JaCoCo XML as a supported report format. Supply the generated report path to its CLI uploader with -f, following the authentication and CI setup for your environment. For example, the upload command’s report-file argument takes the form:
codecov -f path/to/jacoco.xml
The exact invocation can depend on the uploader version and CI environment; follow the Codecov uploader instructions and confirm the report is associated with the intended commit. Codecov’s supported report formats page lists accepted report types. An arbitrary XML file is not necessarily a coverage report.
Rank #3
- THE PERFECT GAMING GIFT — Buy an XBOX Gift Card for yourself or a friend and let them choose the games, add‑ons, subscriptions, and accessories they want most.
- USE FOR GAMES & CONTENT — Redeem for thousands of digital XBOX games, from backward compatible classics to the latest new releases, plus DLC and in‑game currency.
- GAME PASS READY — Apply your balance toward XBOX Game Pass Ultimate to play new titles on day one* and access a library of hundreds of high‑quality console games.
- PRE‑ORDER & PRE‑INSTALL GAMES — Use your balance to pre‑order and pre‑download upcoming titles so you’re ready to play the moment they launch.
- NO FEES OR EXPIRATION — XBOX Gift Cards never expire and have no service fees, so your balance is ready whenever you are.
Codacy
Codacy’s Coverage Reporter accepts a JaCoCo report path with -r. Store the repository token in a CI secret and expose it as CODACY_PROJECT_TOKEN; do not commit the token to the repository. The documented command pattern is:
export CODACY_PROJECT_TOKEN=<repository-token>
bash <(curl -Ls https://coverage.codacy.com/get.sh) report -r path/to/jacoco.xml
Use the report generated for the commit being built, and make sure its source paths correspond to repository-relative files. Codacy can report commit-detection failures such as “Commit not found” or “Branch not enabled” when repository or branch identity is not recognized. See Codacy Coverage Reporter setup for current command and token details.
Azure Pipelines
Publish JaCoCo XML with PublishCodeCoverageResults@2. JaCoCo reports do not use absolute source paths, so Microsoft documents pathToSources to help map report entries to source files. Set it to the absolute source directory on the agent; adapt both paths to your checkout, modules, and any container mounts:
Rank #4
- An Epic Games account is required to redeem an Epic Games Store Card code
- If playing on a console platform (PlayStation Network, Xbox Live, Nintendo Switch or Mobile) you need to link your Epic Games account to that gaming platform (one time) to redeem your gift card code
- The 16 digit code on the back of the card WILL NOT work if redeemed directly through your gaming platform (PlayStation Network, Xbox Live, Nintendo Switch, Mobile, etc.)
- Note: Nintendo devices do not support Fortnite Shared Wallet, so V-Bucks purchased using your account balance will not show up on your Nintendo device. However, if you purchase items in the web Item Shop — or another platform where you play Fortnite — those items will be available in your Locker across all platforms.
- Redemption: Online
- task: PublishCodeCoverageResults@2
inputs:
summaryFileLocation: '$(System.DefaultWorkingDirectory)/app/**/jacoco.xml'
pathToSources: '$(System.DefaultWorkingDirectory)/app/src/main/java/'
failIfCoverageEmpty: true
The example paths are illustrative, not universal. The task can merge multiple summary files and is intended for build pipelines, not release pipelines. See Microsoft’s PublishCodeCoverageResults@2 reference for supported inputs and behavior.
GitHub Code Quality
GitHub Code Quality’s current manual coverage setup calls for Cobertura XML, not raw JaCoCo XML. Convert the JaCoCo report using a documented route such as cover2cover.py or a JaCoCo-to-Cobertura Gradle or Maven plugin, then upload the converted report with actions/upload-code-coverage@v1. Follow the workflow’s documented code-quality: write permission and conditions; GitHub’s example excludes uploads for forked pull requests. Configure the workflow to run on default-branch pushes as well as pull requests so coverage can be compared with the default branch. The GitHub Code Quality coverage setup documents the conversion and workflow requirements.
Free tools Windows power users keep installed
One-click scans. No signup required.
Handle multi-module builds and parallel test jobs
Choose between a unified JaCoCo aggregate report and multiple report uploads based on how the project and destination represent coverage. An aggregate is appropriate when modules form one project-level result. Independent modules or parallel test jobs may instead produce separate reports; the platform must be told how to combine or associate them.
Best Value
- Redeem for anything on PlayStationStore: games, add-ons, PlayStationPlus and more.
- Everything you want to play. Choose from the largest library of PlayStation content.
- Use gift card funds to contribute towards PlayStationPlus memberships.
- For Codacy, upload every tested file, including unchanged files and unchanged monorepo modules. Its advanced upload guidance supports repeated
-rarguments to upload reports together, or--partialfor each report followed by afinalupload after all partials have arrived. - For Azure Pipelines,
summaryFileLocationcan match multiple summary files, which the task can merge. Ensure the pattern includes the intended modules and not unintended duplicate reports. - For other services, use their documented aggregation or partial-report mechanism rather than assuming that repeated uploads are merged. Avoid uploading only one module when the result is meant to cover the whole repository.
Codacy’s advanced coverage upload guidance describes its partial-report workflow.
Verify that the platform processed the right coverage
- Check the generated file. Confirm that the XML exists at the path passed to the uploader. Inspect it for expected packages, classes, source files, and counters; the JaCoCo XML DTD describes its report structure.
- Check upload identity. Review uploader output and the platform’s report status to confirm it detected the intended repository, branch, and commit SHA.
- Check source matching. Open a known source file in the platform and compare its displayed coverage with the XML’s relevant entries. If paths do not match, correct the path mapping or checkout-root configuration before changing coverage data.
- Check report scope and metric. Confirm the report includes the modules and test jobs you intended. Line, branch, instruction, method, and class coverage are distinct counters, and platforms may display or summarize them differently.
Troubleshoot missing or misleading coverage
| Symptom | What to check | Likely correction |
|---|---|---|
| No XML file is produced. | Whether the report task or goal ran, whether Gradle XML output is enabled, and whether CI is looking at the actual module or variant path. | Run Maven through verify or invoke the configured Gradle report task; enable XML and update the uploader path. |
| The XML exists but coverage is zero or unexpectedly low. | Whether tests ran under the JaCoCo agent; whether execution data and report-time class files match; whether Surefire or Failsafe disables forking. | Restore agent instrumentation and analyze the matching compiled classes. JaCoCo explains class identity in its class ID documentation and FAQ. |
| Coverage is present but source files are missing or unmatched. | Whether report paths are repository-relative or container-specific, and whether the platform knows the checkout/source root. Also check compiler debug information for line numbers. | Correct source path mapping, including Azure’s pathToSources where applicable; ensure compilation includes debug information needed for line coverage. |
| The upload succeeds but does not appear on the expected branch or pull request. | The commit SHA detected by the uploader, workflow event, and repository/branch configuration. | Upload against the intended checked-out commit and correct the CI trigger or identity configuration. |
| The result reflects only part of a repository or looks duplicated. | Whether the report pattern selected every module or selected the same report more than once; whether parallel uploads follow the service’s partial-report rules. | Use an aggregate report or the destination’s documented multi-report process, and adjust file globs to include the intended reports exactly once. |
A syntactically valid XML file is only one part of a useful import: the execution data, compiled classes, source paths, and commit must align. Coverage indicates which code was exercised under the recorded tests; it does not by itself establish test quality or correctness.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →

