woocommerce

Author	SHA1	Message	Date
Rodrigo Primo	2dcb04e2e2	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 15:57:11 -02:00
Claudio Sanches	cd554c1bdf	Restored tests/bin/phpunit.sh	2017-10-05 13:14:56 -03:00
Claudio Sanches	4251bd5614	Move code coverage to Scrutinizer	2017-07-20 16:50:12 -03:00
Mike Jolley	178888fbdb	Travis script	2017-03-14 16:59:40 +00:00
Mike Jolley	ed09c20715	Trying to fix travis tests	2017-03-14 12:50:54 +00:00
Jon Surrell	994167046f	Disable coverage except on master, not PR, 7.1 builds This should vastly increase most automated travis builds. Coverage reports are only interesting on master and not needed on all PRs.	2017-01-25 22:28:57 +01:00
Jon Surrell	9069bce4d3	Change travis setup to exclude coverage from all but latest stable Add PHP_LATEST_STABLE env to travis Use same bash conditional for test scripts	2017-01-16 21:11:21 +01:00