It’s easy to using the built-in feature. One line in to rule them all: add test coverage on GitLab .gitlab-ci.yml test:
  coverage: /\d+.\d+ \% covered/ On the opposite side, GitHub doesn’t provide an option to add the test coverage badge. There are many third-party services for this purpose: , , , . It’s not a problem for an open-source project to use these services, cause they mostly provide a free tier for the open-source. codeclimate codecov codacy coveralls It hurts if you want to add the coverage badge to a private repository. All 3rd party options are paid. Samurai has two choices: Use a service to draw a badge based on provided JSON ( ); shields.io Generate a badge during CI/CD run and store it in the repository. Both options work. In the first case, you'll have to use an intermediate GitHub Gist, where you'll send the . Not an elegant approach. fresh coverage as a JSON file You must commit the SVG image to the repository in the second case. I've often seen recipes on the Internet where the badge was committed directly to the main branch. I think this is a bad practice: you'll clog up the history with garbage commits, which are useless by nature. There is a better choice. GitHub provides Pages service, where you can publish a coverage report for example. Technically, you can publish any static set of HTML files placed in a special branch. Looks like an ideal place for storing badges because it will not clog up the history of the main branch. gh-pages Take a look at the snippet with URLs below. If you are using a private repository, you will probably want to make the published report on GitHub Pages closed behind authorization as well. In that case, you won't be able to add a badge reference inside your README. Instead, provide a link to the RAW file in the repository. GitHub will redirect the request to something like . The parameter is generated for a closed repository for authorization purposes. The token is temporary — after several hours the link will become a 🎃. To avoid such behavior you may add a parameter to the file’s link: (1) (2) (3) token raw=true https://github.com/user/my-project/raw/gh-pages/badges/jacoco.svg?raw=true https://my-project.pages.github.io/badges/coverage.svg (1) GitHub Pages link
https://github.com/user/my-project/raw/gh-pages/badges/coverage.svg (2) RAW link
https://raw.githubusercontent.com/user/my-project/gh-pages/badges/coverage.svg?token=GHSAT0AAAAAABTVGF2OW2264AQOCSDOKKHGYXPQLUA (3) Permalink to the file in the private repo Let's put all the requirements together: You need to generate a badge using a command-line tool or a GitHub Action; It’s better to place the resulting badge in the branch; gh-pages In order to display the picture in the README even in a closed repository, you must use a direct link to the file with the parameter. raw=true Practice time! I forked repository. This is one of the implementations of the Conduit App (Medium.com clone). spring-boot-realworld-example-app We’ll use Action. jacoco-badge-generator Add a new step to the GitHub : Workflow config - name: Generate JaCoCo Badge
#      if: ${{ github.ref == 'refs/heads/master' }}
      uses: cicirello/jacoco-badge-generator@v2
      with:
        jacoco-csv-file: build/reports/jacoco/test/jacocoTestReport.csv
        badges-directory: build/reports/jacoco/test/html/badges We are specifying paths to JaCoCo CSV report and the resulting badge's directory. Uncomment the second line if you’d like to execute the step only in the main branch. The next step is to publish the report along with badges. I choose . github-pages-deploy-action - name: Publish coverage report to GitHub Pages
#      if: ${{ github.ref == 'refs/heads/master' }}
      uses: JamesIves/github-pages-deploy-action@v4
      with:
        folder: build/reports/jacoco/test/html We need to set the path to the HTML report. Just a reminder, the generated badge will also be inside this directory. After the commit you’ll need to open the repository and select the branch you want to publish the site from: Settings → Pages The last piece to add is the link to the badge in README. Don't forget about the parameter, so that the picture will be displayed for private repositories as well: raw=true [![Test Coverage](https://cdn.hackernoon.com/images/2hVuiN1gfbdO9OXUxjCttPNETq73-2022-08-08T22:19:48.257Z-cl6lbgrz6002p0as65v8sfgja)](https://drakulavich.github.io/spring-boot-realworld-example-app/) Hooray! All steps have been completed, you can . check the result By clicking on the badge you’ll open the coverage report: Please share in the comments your favorite GitHub Actions to prepare and publish the badges. Thank you for reading!

Paid

Adding Test Coverage Badge on GitHub Without Using Third-party Services

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

DOM Testing Library: Is it Worth a Try?

10 Must Have Chrome Extensions for a Web Developer

The Noonification: Can Mankind Survive as an Interplanetary Species? (10/20/2022)

132 Stories To Learn About Performance

3 Golang Pitfalls Every Developer Needs to Know

DOM Testing Library: Is it Worth a Try?

10 Must Have Chrome Extensions for a Web Developer

The Noonification: Can Mankind Survive as an Interplanetary Species? (10/20/2022)

132 Stories To Learn About Performance

3 Golang Pitfalls Every Developer Needs to Know

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps