Black Friday 2022 Offers 30% discount in Symfony, Twig and Sylius certifications (offer ends tomorrow)

Running Symfony Tests

Edit this page

Warning: You are browsing the documentation for Symfony 3.0, which is no longer maintained.

Read the updated version of this page for Symfony 6.2 (the current stable version).

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:

$ composer update

Running the Tests

Then, run the test suite from the Symfony root directory with the following command:

$ 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.


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.:

$ php ./phpunit src/Symfony/Component/Finder/


On Windows, install the Cmder, ConEmu, ANSICON or Mintty free applications to see colored test results.

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.