Download the PHP package matthiasnoback/behat-remote-code-coverage-extension without Composer

On this page you can find all versions of the php package matthiasnoback/behat-remote-code-coverage-extension. 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 behat-remote-code-coverage-extension

Behat remote code coverage extension

This extension can be used to collect code coverage data from the web server that's called by Mink while running Behat.

To use this extension, enable it under extensions and for every suite that needs remote code coverage collection, set remote_coverage_enabled to true.

Now modify the front controller of your web application to look like this:

Make sure to modify the call to RemoteCodeCoverage::bootstrap() if needed:

  1. Provide your own logic to determine if code coverage should be enabled in the first place (this example uses an environment variable for that). This is important for security reasons. It helps you make sure that the production server won't expose any collected coverage data.
  2. Provide your own directory for storing the coverage data files (.cov).
  3. Provide the path to your own phpunit.xml(.dist) file. This file is only used for its code coverage filter configuration.

After a test run, the extension makes a special call (/?code_coverage_export=true&...) to the web application. The response to this call contains the serialized code coverage data. It will be stored as a file in target_directory, named after the test suite itself, e.g. default.cov.

You can use these .cov files to generate nice reports, using phpcov.

You could even configure PHPUnit to generate a .cov file in the same directory, so you can combine coverage data from PHPUnit and Behat in one report.

To (also) generate (local) code coverage during a Behat test run, use the LocalCodeCoverageExtension.


All versions of behat-remote-code-coverage-extension with dependencies

PHP Build Version
Package Version
Requires php Version >=7.0
behat/behat Version ^3.0
matthiasnoback/live-code-coverage Version ^1.0
behat/mink-extension Version ^2.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 matthiasnoback/behat-remote-code-coverage-extension contains the following files

Loading the files please wait ....