A clover test coverage checker for Github Actions.

Simply add the following step to your workflow:

- name: Check test coverage
  id: test-coverage
  uses: johanvanhelden/gha-clover-test-coverage-check@v1
  with:
    percentage: "95"
    filename: "coverage.xml"

The minimum percentage of coverage allowed.

The filename of the clover coverage XML file.

The precision of the rounded coverage value. Where 0 will round to the highest rounded number (e.g: 99.999999 > 100).

Wether the coverage check should exit if the required percentage is not met.

Output is exported as GitHub Action output.

You can use it in other steps, for example:

- name: Test coverage
  run: echo "${{ steps.test-coverage.outputs.coverage }}"

Or make a step conditional:

- name: Test coverage report
  if: steps.test-coverage.outputs.coverage > 50
  run: echo "We are more than halfway there!"

The calculated coverage value.

The calculated coverage value for display purposes.

The rounded coverage value.

The rounded calculated coverage value for display purposes.

The true or false value of the check result. You can use this output with the exit input to implement your own coverage logic.

This is how you can generate a test coverage report using PHPUnit:

- name: Generate code coverage
  run: ./vendor/bin/phpunit --coverage-clover ./coverage.xml

You can test the action locally by running: docker-compose up --build Any arguments can be configured in the docker-compose.yml file.

Building happens automaticly once a new version is tagged.

To push a manual build, ensure you are logged in locally to hub.docker.com using docker login and have access to the hub repository. (note: your username is used, not your email address).

$ docker build ./ --tag johanvanhelden/gha-clover-test-coverage-check:TAG
$ docker push johanvanhelden/gha-clover-test-coverage-check:TAG

Replace TAG with the tag you are working on.