Steve-Dee-Designs
/
woocommerce
mirror of https://github.com/woocommerce/woocommerce.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
woocommerce/.travis.yml

73 lines
1.7 KiB
YAML
Raw Normal View History

[#3176] Add unit test boostrap
2014-09-01 06:03:52 +00:00
language: php
Run e2e tests on Travis builds (#18374)
2018-01-18 18:42:19 +00:00
addons:
chrome: stable
apt:
packages:
- nginx
Update travis config; remove 5.2, add 5.6 and hhvm
2015-02-03 16:43:01 +00:00
sudo: false
test tweak
2017-08-22 10:02:32 +00:00
# Test main supported versions of PHP against latest WP.
Update travis config; remove 5.2, add 5.6 and hhvm
2015-02-03 16:43:01 +00:00
php:
- 5.6
Added PHP 7 in the tests
2015-12-08 18:26:14 +00:00
- 7.0
Run unit tests against PHP 7.2 as well on Travis
2017-12-11 15:56:47 +00:00
- 7.1
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
- 7.2
Use WP latest instead of 5.0-beta3 to run the PHP 7.3 Travis build job Now that WP 5.0 has been released, we don't need to use 5.0-beta3 anymore to run the PHP 7.3 Travis build job.
2018-12-19 13:32:51 +00:00
- 7.3
Update travis config; remove 5.2, add 5.6 and hhvm
2015-02-03 16:43:01 +00:00
env:
Remove unused Travis environment variable This commit removes the unused Travis enrivonment variable PHP_LATEST_STABLE.
2017-11-13 19:22:46 +00:00
- WP_VERSION=latest WP_MULTISITE=0
Update travis config; remove 5.2, add 5.6 and hhvm
2015-02-03 16:43:01 +00:00
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
# Additional tests against stable PHP (min recommended version is 5.6) and past supported versions of WP
# and code coverage report.
[#3176] Add unit test boostrap
2014-09-01 06:03:52 +00:00
matrix:
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
fast_finish: true
[#3176] Add unit test boostrap
2014-09-01 06:03:52 +00:00
include:
Travis
2017-07-20 10:23:37 +00:00
- php: 5.3
5.3 does not like dist
2017-07-20 14:55:45 +00:00
dist: precise
Travis
2017-07-20 10:23:37 +00:00
- php: 5.2
5.3 does not like dist
2017-07-20 14:55:45 +00:00
dist: precise
Use the "name" config property to better identify build jobs
2018-12-19 13:08:32 +00:00
- name: "Coding standard check"
php: 7.2
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
env: WP_VERSION=latest WP_MULTISITE=0 RUN_PHPCS=1
Use the "name" config property to better identify build jobs
2018-12-19 13:08:32 +00:00
- name: "e2e tests"
php: 7.2
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
env: WP_VERSION=latest WP_MULTISITE=0 RUN_E2E=1
Use the "name" config property to better identify build jobs
2018-12-19 13:08:32 +00:00
- name: "Unit tests code coverage"
php: 7.1
Remove unnecessary Travis environment variable PHP_LATEST_STABLE
2017-11-13 19:24:52 +00:00
env: WP_VERSION=latest WP_MULTISITE=0 RUN_CODE_COVERAGE=1
Add a new Travis job to run WC unit tests using WordPress nightly Doing this to help us find problems in the upcoming versions of WordPress.
2019-01-16 11:06:35 +00:00
- name: "WooCommerce unit tests using WordPress nightly"
php: 7.3
env: WP_VERSION=nightly WP_MULTISITE=0
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
allow_failures:
Use WP 5.0-beta5 when running PHP 7.3 in Travis To make it easier to test WC running the upcoming PHP 7.3, this commit changes the PHP 7.3 Travis build to run unit tests using WP 5.0-beta5. This way we won't display WP core warnings related to PHP 7.3 that were already fixed in the upcoming WP version and will be able to see only WC related warnings. My initial plan was to use WP nightly but that didn't work as nightly is still build from trunk and WP 5.0 development is being done on another branch (https://make.wordpress.org/core/2018/10/05/wordpress-5-0-commit-management/).
2018-11-19 19:46:50 +00:00
- php: 7.1
env: WP_VERSION=latest WP_MULTISITE=0 RUN_CODE_COVERAGE=1
[#3176] Add unit test boostrap
2014-09-01 06:03:52 +00:00
before_script:
Remove xdebug.ini only if it exists This commit adds an if to check if xdebug.ini exists before trying to remove it. Doing this to avoid a build error in PHP versions where the file doesn't exist like PHP 7.3.
2018-10-16 13:36:25 +00:00
- |
# Remove Xdebug for a huge performance increase:
if [ -f ~/.phpenv/versions/$(phpenv version-name)/etc/conf.d/xdebug.ini ]; then
phpenv config-rm xdebug.ini
else
echo "xdebug.ini does not exist"
fi
Make sure PHPUnit tests runs when using PHP 7.2+ in the Travis builds Due to a recent change in the Travis environment, WooCommerce unit tests stopped working with the following error (see for example https://travis-ci.org/woocommerce/woocommerce/jobs/463470674#L876) in the PHP 7.2 and 7.3 build jobs: Fatal error: Class PHPUnit_Util_Test may not inherit from final class (PHPUnit\Util\Test) in /tmp/wordpress-tests-lib/includes/phpunit6-compat.php on line 18 This error is happening because Travis started ignoring the PHPUnit version that we install manually via Composer (https://github.com/woocommerce/woocommerce/blob/f7bc3fb85195df8f96c70d2846b0104ee224fef2/tests/bin/travis.sh#L6) and started using the PHPUnit version that is shipped with each of its PHP docker images. This means that for the docker images running PHP 7.2 and 7.3, PHPUnit 7 is used but the WordPress unit test framework is not compatible with PHPUnit 7 (see WordPress core ticket https://core.trac.wordpress.org/ticket/43218) and produces the error above. I believe that this is happening because Travis changed the directory where it installs composer global packages from `$HOME/.composer/` to `$HOME/.config/composer/` (https://github.com/travis-ci/travis-ci/issues/7289#issuecomment-427333966) and we add `$HOME/.composer/vendor/bin:$PATH` to the `$PATH`. So this commit simply updates the path in the line where we add it to the `$PATH`. I tried to use `composer exec` instead of updating `$PATH` but that didn't work for PHP 5.2.
2018-12-05 13:52:07 +00:00
- export PATH="$HOME/.config/composer/vendor/bin:$PATH"
Travis
2017-09-26 12:24:11 +00:00
- bash tests/bin/install.sh woocommerce_test root '' localhost $WP_VERSION
- bash tests/bin/travis.sh before
[#3176] Add unit test boostrap
2014-09-01 06:03:52 +00:00
attempt to run PHPCS on travis
2016-08-27 14:18:14 +00:00
script:
Restored tests/bin/phpunit.sh
2017-10-05 16:09:39 +00:00
- bash tests/bin/phpunit.sh
Moved phpcs after phpunit
2017-10-10 13:50:22 +00:00
- bash tests/bin/phpcs.sh
Retry e2e tests automatically in case of failure Tests should be consistent. That is true for our unit tests suite, but it is something that is harded to achieve for functional tests. Our end to end tests often times fail due to factors outside of our control, and simply manually restarting the Travis build is enough to make them pass (example: https://github.com/woocommerce/woocommerce/pull/21150#issuecomment-415132390). This commits uses `travis_retry` to make Travis automatically retry a maximum of three times to run WC e2e tests in case of a failure.
2018-08-23 19:20:41 +00:00
- travis_retry bash tests/bin/run-e2e-CI.sh
Add coveralls.io for tracking test coverage
2014-09-07 18:53:33 +00:00
after_script:
added .yml format in .editorconfig, closes #6364
2014-09-22 19:15:16 +00:00
- bash tests/bin/travis.sh after
Prevent Travis builds duplication This commit changes Travis configuration file to specify a list of branches that it should build. This way Travis will only create a new build when a commit is pushed to the master branch and release branches and when tags are created. The behavior for PRs is not modified and PR creation and updates will still trigger builds. Doing this to speed up Travis build by preventing it from running two builds for PR that are created from a branch of the same repository. Before this change, Travis would create a build when the branch is pushed to GitHub (continuous-integration/travis-ci/push) and another one when the PR is created (continuous-integration/travis-ci/pr). For an example, see https://github.com/woocommerce/woocommerce/pull/17680.
2017-11-20 19:18:29 +00:00
# Specifies that Travis should create builds for master and release branches and also tags.
branches:
only:
- master
- /^\d+\.\d+(\.\d+)?(-\S*)?$/
- /^release\//