You are browsing the Symfony 4.3 documentation, which changes significantly from Symfony 3.x. If your app doesn't use Symfony 4.3 yet, browse the Symfony 3.4 documentation.
Running Symfony Tests
Running Symfony Tests¶
The Symfony project uses a third-party service which automatically runs tests for any submitted patch. If the new code breaks any test, the pull request will show an error message with a link to the full error details.
In any case, it's a good practice to run tests locally before submitting a patch for inclusion, to check that you have not broken anything.
Before Running the Tests¶
To run the Symfony test suite, install the external dependencies used during the tests, such as Doctrine, Twig and Monolog. To do so, install Composer and execute the following:
1 | $ composer update
|
Running the Tests¶
Then, run the test suite from the Symfony root directory with the following command:
1 | $ php ./phpunit symfony
|
The output should display OK. If not, read the reported errors to figure out
what's going on and if the tests are broken because of the new code.
Tip
The entire Symfony suite can take up to several minutes to complete. If you
want to test a single component, type its path after the phpunit command,
e.g.:
1 | $ php ./phpunit src/Symfony/Component/Finder/
|
This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.