C3 Laravel Package

• Add tracker of running test to avoid incomplete coverage results by @MarcelBolten in https://github.com/Codeception/c3/pull/90

• Fixed compatibility with PHPUnit 10.0.6+

• Supports PHPUnit 10

• Support path coverage with PHPUnit 9

• Fix Type Error when configuration loading failed

• Fix compatibility with Codeception 5

• Don't set empty headers, because null values can cause issues

• Fixed fatal error which could happen if vendor/autoload.php is included before c3.php #68

Support Cobertura code coverage format

Minor but important fixes: #45 #46 #42 #47

#35 Fixed Uncaught ArgumentCountError #36 Added missing parameter to constructor of PHP_CodeCoverage_Report_PHPUnit aka SebastianBergmann\CodeCoverage\Report\Xml\Facade

Export code coverage in PHPUnit format, see #33

Fixed regression in 2.0.11 for composer update. See #30

Fix Composer notifications during install #29

• crap4j support by @gimler #28
• speed up initialization by @gimler #27

• Fixed writing coverage summaries for parallel requests. See #25
• added check for class_exists PHP_CodeCoverage before declaring alias toit

• Fixed memory check for bytes and gigabytes #23
• Use package events instead of command events for Composer installations #22

Fixes by @Naktibalda

• Added shim for PHP CodeCoverage v.4 by @sharky98

Minor patch which ensures that directory to store codecoverage report exists. Adds just this line:

                if (!file_exists(dirname($current_report))) { // verify directory exists
                    mkdir(dirname($current_report), 0777, true);
                } else {
                    __c3_error("Can't write CodeCoverage report into $current_report");
                }

• codeception/c3 is now a Composer plugin and installs c3.php by automatically. Please remove old post-install and post-update hooks from composer.json.
• Installer will ask to replace c3.php file on update for not to overwrite local changes (with help of @jasny)
• Fixed loading of codeception functions (by @raistlin)
• Changed priority of autoloader (by @raistlin):

I think this new order has lot more sense: 1st. If codecept.phar file exists, load classes from there. 2nd. If autoloader exists, load it. 2nd-b. In case autoloader of codeception exists in vendor path, also it should be loaded, if not, some methods like 'codeception_relative_path' will not be loaded and Codeception/c3 will fail to load. 3rd. Try to load codeception autoloader (outside of vendor's path) 4th, Fail, no autoloader found.

• Allow c3 to use codeception.dist.yml by @gammamatrix
• Solution for Undefined variable C3_CODECOVERAGE_MEDIATE_STORAGE in __c3_error by @rhertogh https://github.com/Codeception/c3/pull/14

• #12 Fixed codecoverage header check