jacoco-report's Introduction

jacoco-report

Github action that publishes the JaCoCo report as a comment in the Pull Request

Usage

Pre-requisites

Create a workflow .yml file in your repositories .github/workflows directory. An example workflow is available below. For more information, reference the GitHub Help Documentation for Creating a workflow file.

Inputs

paths - [required] Whitespace separated paths of the generated xml files.
token - [required] Github personal token to add commits to Pull Request
min-coverage-overall - [optional] The minimum code coverage that is required to pass for changed files
min-coverage-changed-files - [optional] The minimum code coverage that is required to pass for changed files
comment-id - [optional] A comment to update if there is an existing comment

Outputs

coverage-overall - The overall coverage of the project
coverage-changed-files - The total coverage of all changed files

Example Workflow

name: Measure coverage

on:
  pull_request:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Set up JDK 1.8
        uses: actions/setup-java@v1
        with:
          java-version: 1.8
      - name: Run Coverage
        run: |
          chmod +x gradlew
          ./gradlew testCoverage

      - name: Add coverage to PR
        id: jacoco
        uses: madrapps/[email protected]
        with:
          paths: >
              ${{ github.workspace }}/build/reports/jacoco/testCoverage/testCoverage.xml
          token: ${{ secrets.GITHUB_TOKEN }}
          min-coverage-overall: 40
          min-coverage-changed-files: 60

Example Project

For a working project refer to jacoco-playgound project. Check out the PR's in the project to get an idea on how the report is shown on a pull request comment.