leanphp / phpspec-code-coverage Goto Github PK

Update PHPDoc comments in the class files to use standard leanphp package headers

It would be nice to have a PHP7+ targeted release. Perhaps some parts of the code can be cleaned up for this.

Hi

Are there any plans for supporting phpspec v5 in the near future? :)

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.

We need coding style guide for the project so existing codebase and new contributions would follow same coding style.

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.

Integrate with ScrutinizerCI

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 coverage

For relevant discussion see #11 (esp. #11 (comment) )

• Fix error regarding --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 usecase

Enable Windows based CI to make sure package and tests are compatible with Windows OS

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

As of #19 the functional / integration tests was disabled. The tests were previously written in PhpSpec and now cannot run anymore due to phpunit/php-code-coverage marking their classes as final (we cannot mock them anymore).

As a result of #19 we need new functional tests.

Could be possible to add please support for phpspec/phpspec v4?

Add example screenshots for code coverage reports

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

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.

PhpSpec crashes with code generation enabled, I was just wondering if that is a known issue?