leanphp / phpspec-code-coverage Goto Github PK
View Code? Open in Web Editor NEWGenerate Code Coverage reports for PhpSpec tests
Home Page: https://packagist.org/packages/leanphp/phpspec-code-coverage
License: Other
Generate Code Coverage reports for PhpSpec tests
Home Page: https://packagist.org/packages/leanphp/phpspec-code-coverage
License: Other
I was struggling to get this working with phpdbg on a project with a moderately large number of tests ( > 1400 phpspec examples), no code coverage was being generated. Eventually I noticed that I was getting an exit code of 255.
The problem was the memory_limit in phpdbg's php.ini
- it would probably help others to add a note to the readme to suggest that the memory_limit there should be set to -1.
This is main issue to track changes to the package related to phpunit/php-code-coverage:~6.0
Please do not hesitate to provide any feedback
Running phpspec with coverage brings my total tests (5 right now) to a 1 to 1.5second execution time.
While running it without coverage (by commenting out the configuration) has a 100ms or less execution time.
Is it possible that we can run phpspec like: phpspec run --no-coverage
or maybe even turn it around like
phpspec run --coverage
like phpunit has it?
Since I don't nessecarilly want to ALWAYS generate coverage, especially at development.
Version 4.0.0
requires phpunit/php-code-coverage
version ~4.0||~5.0
but attempts to use code from version 5 regardless.
Lines 82 - 84 of CodeCoverageExtension
:
case 'xml':
$reports['xml'] = new Report\Xml\Facade(Version::id());
break;
This doesn't work because class SebastianBergmann\CodeCoverage\Version
was only added in version 5.0.0
. I'm using 4.0.8
and I'm getting a fatal error instead. An upgrade is not an option, since I'm stuck with PHPUnit 5.7 which requires phpunit/php-code-coverage ^4.0.4
(legacy codebase).
Class Report\Xml\Facade
doesn't expect any constructor arguments which means that Version::id()
part can be safely removed.
Is there a chance a fix could be released as a 4.0.1
? I could fix the issue myself but there's no v4.0
branch to create a pull request to.
Could be possible to add please support for phpspec/phpspec
v4?
--no-coverage
when running other commands than run
--no-coverage
argument will be added to all commands, to allow skipping coverage generation (currently it is only supported by run
command). See #29 for a usecasePhpSpec crashes with code generation enabled, I was just wondering if that is a known issue?
Add example screenshots for code coverage reports
Support specifying code coverage configuration parameters via cli instead of only supporting configuration file. In case both (configuration and CLI arguments) are specified, the CLI arguments should always take priority.
Set of arguments we need to support:
--coverage-clover <file>
- Generate code coverage report in Clover XML format--coverage-crap4j <file>
- Generate code coverage report in Crap4J XML format--coverage-html <dir>
- Generate code coverage report in HTML format--coverage-php <file>
- Export PHP_CodeCoverage object to file--coverage-text=<file>
- Generate code coverage report in text format Default: Standard output--coverage-xml <dir>
- Generate code coverage report in PHPUnit XML format--whitelist <dir>
- Whitelist <dir>
for code coverage analysis--disable-coverage-ignore
- Disable annotations for ignoring code coverageFor relevant discussion see #11 (esp. #11 (comment) )
Hi,
Don't know if it is possible, but could be handful for CI.
@erichard opened this Issue on 24 Nov 2016 on https://github.com/henrikbjorn/PhpSpecCodeCoverageExtension/issues/60
Integrate with ScrutinizerCI
Update PHPDoc comments in the class files to use standard leanphp package headers
Hi
Are there any plans for supporting phpspec v5 in the near future? :)
We need coding style guide for the project so existing codebase and new contributions would follow same coding style.
Enable Windows based CI to make sure package and tests are compatible with Windows OS
It would be nice to have a PHP7+ targeted release. Perhaps some parts of the code can be cleaned up for this.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.