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

65 lines
1.5 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
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
Run unit tests against PHP 7.2 as well on Travis
2017-12-11 15:56:47 +00:00
- php: 7.2
Run e2e tests on Travis builds (#18374)
2018-01-18 18:42:19 +00:00
env: WP_VERSION=latest WP_MULTISITE=0 RUN_PHPCS=1 RUN_E2E=1
Switch travis codecoverage from xdebug to phpdbg (#20857) This commit changes the travis codecoverage from using xdebug to phpdbg, phpdbg seems much faster and gives similar results. Reason for switching is we have been running into constant timeouts on our codecoverage due to the 50min job limit on travis, which means our codecoverage has not been updated in a couple of months. * Remove xdebug as it slows tests down, switch to using phpdbg for code coverage. * Update parameters for phpdbg * It is qrr not qqr * Include vendor/bin path when using phpdbg * Use PHP 7.1 to run phpdbg * Update phpunit dire * Include $HOME in phpdbg call to phpunit * Set no memory limit to avoid out of memory errors. * Assign timeout group to test_request_url test for paypal and do not execute that on coverage as it causes a memeory timeout. Test needs optimization to run for code coverage. * @covers usage for methods should be prefixed with ::
2018-07-20 12:34:43 +00:00
- 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
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.3
env: WP_VERSION=5.0-beta5 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
Travis
2017-09-26 12:24:11 +00:00
- export PATH="$HOME/.composer/vendor/bin:$PATH"
- 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\//