Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Enable clover.xml coverage reports by default.

Open
  • Is something wrong?
#101 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
php
Domain
ci-cd, testing

Research direction

Start with bin/run-tests and inspect how coverage output is currently configured. Enable clover.xml generation by default, then verify that bin/run-tests produces the file and that Travis can use it for coverage checks.

Written by the indexing model from the issue text.

Description

2.x enhancement

They were previously disabled by default because they slow down bin/run-tests.

Thanks to the forthcoming loadsys/CakePHP-Shell-Scripts#43 we'll soon have the ability to check code coverage percentage via Travis...provided we have the clover.xml file available. So it now makes sense to generate that file by default so the shell-scripts package is more feature-complete out of the box when paired with the Skeleton.

Dominant language
PHP
Stars
10
Forks
1
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from loadsys/CakePHP-Skeleton

All issues in loadsys/CakePHP-Skeleton

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.