Creating a junit log file, or clover coverage is often a nice bonus, as it gives you a nice graphical view of your testing results: app/Console/cake test app AllTests \ --stderr \ --log-junit junit.xml \ --coverage-clover --coverage-clover clover.xml If you use clover coverage, or the junit results, make sure to configure those in Jenkins as well. Failing to configure those steps will mean you won’t see the results. Run

Creating a junit log file, or clover coverage is often a nice bonus, as it gives you a nice graphical view of your testing results: app/Console/cake test app AllTests \ --stderr \ --log-junit junit.xml \ --coverage-clover --coverage-clover clover.xml If you use clover coverage, or the junit results, make sure to configure those in Jenkins as well. Failing to configure those steps will mean you won’t see the results. Run

build. In this step install your dependencies and run the tests for your application. Creating a junit log file, or clover coverage is often a nice bonus, as it gives you a nice graphical view of your dependencies php composer.phar install vendor/bin/phpunit --log-junit junit.xml --coverage-clover clover.xml If you use clover coverage, or the junit results, make sure to configure those in Jenkins as well

build. In this step install your dependencies and run the tests for your application. Creating a junit log file, or clover coverage is often a nice bonus, as it gives you a nice graphical view of your dependencies php composer.phar install vendor/bin/phpunit --log-junit junit.xml --coverage-clover clover.xml If you use clover coverage, or the junit results, make sure to configure those in Jenkins as well