friends-of-phpspec / phpspec-code-coverage
Generate Code Coverage reports for PhpSpec tests
Installs: 1 880 937
Dependents: 142
Suggesters: 0
Security: 0
Stars: 20
Watchers: 3
Forks: 39
Open Issues: 5
Requires
- php: >= 7.3
- phpspec/phpspec: ^6.0 || ^7.0
- phpunit/php-code-coverage: ^9.2 || ^10.0 || ^11.0
- phpunit/php-file-iterator: ^3.0 || ^4.0 || ^5.0
Requires (Dev)
- friendsofphp/php-cs-fixer: ^3.4
- phpstan/phpstan: ^1.5
Suggests
- ext-pcov: Install PCov extension to generate code coverage.
- ext-xdebug: Install Xdebug to generate phpspec code coverage.
Conflicts
- sebastian/comparator: < 2.0
This package is auto-updated.
Last update: 2024-12-12 14:10:28 UTC
README
phpspec-code-coverage
phpspec-code-coverage is a PhpSpec extension that generates Code Coverage reports for PhpSpec tests.
Generating Code Coverage reports allows you to to analyze which parts of your codebase are tested and how well. However, Code Coverage alone should NOT be used as a single metric defining how good your tests are.
Requirements
- PHP 7+ (for PhpSpec v4+) or PHP 5.6+ (for PhpSpec v3)
- Xdebug, phpdbg or pcov extension enabled (PHP 7+ is required for code generation to work with phpdbg).
Compatibility
Change Log
Please see CHANGELOG.md for information on recent changes.
Install
Install this package as a development dependency in your project:
$ composer require --dev friends-of-phpspec/phpspec-code-coverage
Enable extension by editing phpspec.yml
of your project:
extensions: FriendsOfPhpSpec\PhpSpec\CodeCoverage\CodeCoverageExtension: ~
This will sufficient to enable Code Coverage generation by using defaults provided by the extension. This extension supports various configuration options. For a fully annotated example configuration file check configuration section.
Usage
If you execute phpspec run
command, you will see code coverage generated in coverage
directory (in html
format):
$ bin/phpspec run
Note! When generating Code Coverage reports make sure PHP processes run via
CLI are not memory limited (i.e. memory_limit
set to -1
in
/etc/php/cli/php.ini
).
Running with phpdbg
This extension now supports phpdbg, which results in faster execution when
using more recent versions of PHP. Run phpspec
via phpdbg:
$ phpdbg -qrr phpspec run
Note! PHP 7+ is required for code generation to work with phpdbg.
Configuration
You can see fully annotated phpspec.yml
example file below, which can be used
as a starting point to further customize the defaults of the extension. The
configuration file below has all of the Configuration Options.
# phpspec.yml # ... extensions: # ... other extensions ... # friends-of-phpspec/phpspec-code-coverage FriendsOfPhpSpec\PhpSpec\CodeCoverage\CodeCoverageExtension: # Specify a list of formats in which code coverage report should be # generated. # Default: [html] format: - text - html #- clover #- php #- xml #- cobertura # # Specify output file/directory where code coverage report will be # generated. You can configure different output file/directory per # enabled format. # Default: coverage output: html: coverage #clover: coverage.xml #php: coverage.php #xml: coverage #cobertura: cobertura.xml # # Should uncovered files be included in the reports? # Default: true #show_uncovered_files: true # # Set lower upper bound for code coverage # Default: 35 #lower_upper_bound: 35 # # Set high lower bound for code coverage # Default: 70 #high_lower_bound: 70 # # Whilelist directories for which code generation should be done # Default: [src, lib] # # Should text output show only summary? # Default: false #show_only_summary: true # whitelist: - src - lib # or to apply filtering on files names #- directory: src # suffix: "Controller.php" # prefix: "Get" # # Whiltelist files for which code generation should be done # Default: empty #whilelist_files: #- app/bootstrap.php #- web/index.php # # Blacklist directories for which code generation should NOT be done #blacklist: #- src/legacy # or to apply filtering on files names #- directory: src/legacy # suffix: "Spec.php" # prefix: "Test" # # Blacklist files for which code generation should NOT be done #blacklist_files: #- lib/bootstrap.php
Options
format
(optional) a list of formats in which code coverage should be generated. Can be one or many of:clover
,cobertura
,crap4j
,php
,text
,html
,xml
(defaulthtml
) Note: When usingclover
format option, you have to configure specificoutput
file for theclover
format (see below).output
(optional) sets an output file/directory where specific code coverage format will be generated. If you configure multiple formats, takes a hash offormat:output
(e.g.clover:coverage.xml
) (defaultcoverage
)show_only_summary
(optional) for showing only summary in text report (defaultfalse
)show_uncovered_files
(optional) for including uncovered files in coverage reports (defaulttrue
)lower_upper_bound
(optional) sets lower upper bound for code coverage (default35
).high_lower_bound
(optional) sets high lower bound for code coverage (default70
)whitelist
takes an array of directories to whitelist (default:lib
,src
). The array can be made more specific if an associative array is given with the following keys (directory
,prefix
,suffix
)whitelist_files
takes an array of files to whitelist (default: none).blacklist
takes an array of directories to blacklist (default:test, vendor, spec
). The array can be made more specific if an associative array is given with the following keys (directory
,prefix
,suffix
)blacklist_files
takes an array of files to blacklist
Authors
Copyright (c) 2017-2018 ek9 dev@ek9.co (https://ek9.co).
Copyright (c) 2013-2016 Henrik Bjornskov, for portions of code from henrikbjorn/phpspec-code-coverage project.
License
Licensed under MIT License.