woocommerce/tests/bin/phpunit.sh

#!/usr/bin/env bash

if [[ ${RUN_PHPCS} == 1 ]] || [[ ${RUN_E2E} == 1 ]]; then
	exit
fi

if [[ ${RUN_CODE_COVERAGE} == 1 ]]; then
	phpdbg -qrr $HOME/.composer/vendor/phpunit/phpunit/phpunit -d memory_limit=-1 -c phpunit.xml --coverage-clover=coverage.clover --exclude-group=timeout
else
	$HOME/.composer/vendor/phpunit/phpunit/phpunit -c phpunit.xml
fi
Restored tests/bin/phpunit.sh 2017-10-05 16:09:39 +00:00			`#!/usr/bin/env bash`
Use separate Travis build jobs to run e2e tests and PHPCS This commit creates two new Travis build jobs, one to run the e2e tests and another to run PHPCS. Doing this, instead of running those two checks in the same build job as the PHP 7.2 unit tests, should make the total build time shorter and it should make it easier to see why the build failed. 2018-12-05 18:00:05 +00:00
			`if [[ ${RUN_PHPCS} == 1 ]] \|\| [[ ${RUN_E2E} == 1 ]]; then`
			`exit`
			`fi`

Generate code coverage report on a separate non-blocking Travis job Travis build is taking about 40 minutes to complete, and that is mostly because of the generation of the code coverage report. To address that, this commit changes Travis configuration to run the command to generate code coverage report on a separate non-blocking Travis job. This way once the jobs that run the tests finishes, Travisi will mark the build as successful and will keep running code coverage on a separate job. 2017-11-13 17:53:42 +00:00			`if [[ ${RUN_CODE_COVERAGE} == 1 ]]; then`
Update PHPUnit location 2019-03-19 11:47:26 +00:00			`phpdbg -qrr $HOME/.composer/vendor/phpunit/phpunit/phpunit -d memory_limit=-1 -c phpunit.xml --coverage-clover=coverage.clover --exclude-group=timeout`
Restored tests/bin/phpunit.sh 2017-10-05 16:09:39 +00:00			`else`
Update PHPUnit location 2019-03-19 11:47:26 +00:00			`$HOME/.composer/vendor/phpunit/phpunit/phpunit -c phpunit.xml`
Restored tests/bin/phpunit.sh 2017-10-05 16:09:39 +00:00			`fi`