User tests: Successful: Unsuccessful:
This allows us to use the latest and greatest version of PHPUnit - currently we're on 4.0.17 - the limit now for pear. But this will put us on 4.1.0
See https://github.com/sebastianbergmann/phpunit/wiki/End-of-Life-for-PEAR-Installation-Method
Travis has PHPUnit installed via PEAR which is throwing a nag screen right now (see https://travis-ci.org/joomla/joomla-cms/jobs/24479895).
Ah, I see.
What about letting know Travis guys about phpunit pear method depreciation?
PHPUnit with travis doesn't have dbUnit - which we still need to install - we're installing that via pear in the travis.yml (see the PR)
The phar file contains everything - which is why it does both jobs in one
Travis now uses PHPUnit PHAR installation, see travis-ci/travis-ci#2223.
I see since this Monday tests are green again.
Description | ⇒ | <p>This allows us to use the latest and greatest version of PHPUnit - currently we're on 4.0.17 - the limit now for pear. But this will put us on 4.1.0</p> <p>See <a href="https://github.com/sebastianbergmann/phpunit/wiki/End-of-Life-for-PEAR-Installation-Method">https://github.com/sebastianbergmann/phpunit/wiki/End-of-Life-for-PEAR-Installation-Method</a></p> | |
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2014-05-07 09:53:00 |
Labels |
Added:
?
?
|
Yeah the tests are green because there was still an update from PHPUnit 3.7 to 4.0 - and we had a bug in JRoute which meant all travis tests that utilized JRoute failed - I had that fixed up on Monday
Is it necessary to download phpunit's phar file for every job? According to travis docs, we should be fine with just