silverstripe-framework/phpunit.xml.dist

<?xml version="1.0" encoding="UTF-8"?>
<!--
Standard module phpunit configuration.
Requires PHPUnit ^5.7
-->
<phpunit bootstrap="tests/bootstrap.php" colors="true">
	<testsuite name="Default">
		<directory>tests/php</directory>
    </testsuite>
    <testsuite name="framework">
        <directory>tests/php</directory>
    </testsuite>
    <testsuite name="cms">
        <directory>vendor/silverstripe/cms/tests</directory>
    </testsuite>
    <filter>
        <whitelist addUncoveredFilesFromWhitelist="true">
            <directory suffix=".php">.</directory>
            <exclude>
                <directory suffix=".php">tests/</directory>
                <directory suffix=".php">thirdparty/</directory>
            </exclude>
        </whitelist>
    </filter>
</phpunit>
Update test configuration Note: Retains CMS build 2017-04-04 07:30:02 +02:00			`<?xml version="1.0" encoding="UTF-8"?>`
NEW: Don’t set up SilverStripe project for test run The SilverStripe project structure complicates the travis test run, and the goal of this branch is to prevent it from being necessary. - Unit tests can be run simply with PHPUnit. - Behat test can be run with the silverstripe/serve module Note that initially this commit doesn’t cater to the behat tests. As part of this, we allow dev packages to be installed when testing These settings don’t affect projects that use framework, only when framework’s composer install / require calls are used themselves. Since SS4 is pre-stable, these are important. They can probably be removed once SS4 stable (and stable versions of support packages) have been released. 2016-09-12 07:42:05 +02:00			`<!--`
Update test configuration Note: Retains CMS build 2017-04-04 07:30:02 +02:00			`Standard module phpunit configuration.`
			`Requires PHPUnit ^5.7`
NEW: Don’t set up SilverStripe project for test run The SilverStripe project structure complicates the travis test run, and the goal of this branch is to prevent it from being necessary. - Unit tests can be run simply with PHPUnit. - Behat test can be run with the silverstripe/serve module Note that initially this commit doesn’t cater to the behat tests. As part of this, we allow dev packages to be installed when testing These settings don’t affect projects that use framework, only when framework’s composer install / require calls are used themselves. Since SS4 is pre-stable, these are important. They can probably be removed once SS4 stable (and stable versions of support packages) have been released. 2016-09-12 07:42:05 +02:00			`-->`
Revert "[Improvement\|testing] Use scriptfusion to immediately print PHPUnit output" 2017-05-22 11:02:34 +02:00			`<phpunit bootstrap="tests/bootstrap.php" colors="true">`
NEW: Don’t set up SilverStripe project for test run The SilverStripe project structure complicates the travis test run, and the goal of this branch is to prevent it from being necessary. - Unit tests can be run simply with PHPUnit. - Behat test can be run with the silverstripe/serve module Note that initially this commit doesn’t cater to the behat tests. As part of this, we allow dev packages to be installed when testing These settings don’t affect projects that use framework, only when framework’s composer install / require calls are used themselves. Since SS4 is pre-stable, these are important. They can probably be removed once SS4 stable (and stable versions of support packages) have been released. 2016-09-12 07:42:05 +02:00			`<testsuite name="Default">`
API Namespace framework tests 2016-10-14 03:30:05 +02:00			`<directory>tests/php</directory>`
Update test configuration Note: Retains CMS build 2017-04-04 07:30:02 +02:00			`</testsuite>`
			`<testsuite name="framework">`
			`<directory>tests/php</directory>`
			`</testsuite>`
			`<testsuite name="cms">`
Actually run CMS tests 2018-02-07 17:24:40 +01:00			`<directory>vendor/silverstripe/cms/tests</directory>`
Update test configuration Note: Retains CMS build 2017-04-04 07:30:02 +02:00			`</testsuite>`
FIX Enable code coverage builds with phpdbg and 7.1.7 PHP 7.1.7 is currently not segfaulting when generating coverage reports with phpdbg 2017-07-16 03:56:12 +02:00			`<filter>`
			`<whitelist addUncoveredFilesFromWhitelist="true">`
			`<directory suffix=".php">.</directory>`
			`<exclude>`
			`<directory suffix=".php">tests/</directory>`
FIX Exclude thirdparty dir from code coverage 2017-07-18 12:21:45 +02:00			`<directory suffix=".php">thirdparty/</directory>`
FIX Enable code coverage builds with phpdbg and 7.1.7 PHP 7.1.7 is currently not segfaulting when generating coverage reports with phpdbg 2017-07-16 03:56:12 +02:00			`</exclude>`
			`</whitelist>`
			`</filter>`
NEW: Don’t set up SilverStripe project for test run The SilverStripe project structure complicates the travis test run, and the goal of this branch is to prevent it from being necessary. - Unit tests can be run simply with PHPUnit. - Behat test can be run with the silverstripe/serve module Note that initially this commit doesn’t cater to the behat tests. As part of this, we allow dev packages to be installed when testing These settings don’t affect projects that use framework, only when framework’s composer install / require calls are used themselves. Since SS4 is pre-stable, these are important. They can probably be removed once SS4 stable (and stable versions of support packages) have been released. 2016-09-12 07:42:05 +02:00			`</phpunit>`