Download the PHP package dmecke/coverage-checker without Composer

On this page you can find all versions of the php package dmecke/coverage-checker. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package coverage-checker

Installation

Install this library by require it via Composer:

Composer will install an executable in its bin-dir which defaults to vendor/bin.

Usage

Add a configuration file called coverage-checker.yaml to your project root:

Run your test suite with clover coverage enabled:

Run the code coverage check with:

The script will use a return code > 0 if any code coverage does not meet the specified criteria. This way it can be used in CI.

FAQ

Why does the check fail when the coverage is better than defined?

If you managed to improve your test coverage you should increase your defined limits. Otherwise you could fall back to a lower coverage again.

All versions of coverage-checker with dependencies

PHP Build Version
Package Version
Requires php Version ^7.3|^8.0
ext-simplexml Version *
symfony/console Version ^4.2|^5.0
symfony/yaml Version ^4.2|^5.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package dmecke/coverage-checker contains the following files

Loading the files please wait ...