A cool feature of Symfony is that you can configure your application to open files from your browser directly in your IDE. This is great when working with PHPStorm or VSCode. To do this, add the IDE line to your config/packages/framework.yaml file.

  1. Symfony's framework.ide config for PhpStorm and Vagrant. Ask Question Asked 4 years, 1 month ago. Active 7 months ago. Viewed 731 times 1. How do I set up framework.ide config value so that it properly links to files in PhpStorm, when the code is run from Vagrant?
  2. PhpStorm is a PHP IDE which keeps up with latest PHP & web languages trends, integrates a variety of modern tools, and brings even more extensibility with support for major PHP frameworks.
  3. As we all know that Phpstorm is an ideal IDE for PHP programing language. It supports Symfony, Laravel, Drupal, WordPress, Zend Framework, Magento, Joomla!, CakePHP.

One of the great things that happened in PHP world was the introduction of Composer, a dependency manager for PHP which allows us to specify dependencies for our project and have Composer install and update them for us. With PhpStorm 6, we’re taking Composer support one step further with full support for this great tool in the UI and in PhpStorm’s command line tool.

In this post, we’ll cover our new tooling support:

Jetbrain Phpstorm

  • Creating a new project with Composer
  • Init Composer
  • Add dependencies
  • Command line tool support

Let’s create a project using the Symfony framework and install dependencies using Composer support in PhpStorm.

Creating a new project with Composer

When creating a new project in PhpStorm using the File New project… menu, we can choose from a list of project types. PhpStorm 6 introduces a new project type: Composer project.

When using this project type, PhpStorm will present us with a dialog which allows us to do two things. We can specify the path to composer.phar (or have PhpStorm download it from getcomposer.org) and we can start adding dependencies through Composer. Using the package filter we can search through packages listed at the Packagist.

Let’s install the symfony/symfony package, the official package for the Symfony framework. By default the latest version will be installed, however we can select the version to install from this dialog as well. After clicking OK, PhpStorm will install the selected package into a new project.

Once finished, we have a blank Symfony project which we can start developing in.

Init Composer

In an empty project (or an existing project in which Composer was not initialized), we can right-click the project and use the Composer Init Composer… context menu to enable Composer support for our project. If you don’t have composer.phar anywhere on your system, the Click here to download from getcomposer.org helper will download the latest composer.phar from the official website.

This will generate a default composer.json file in our project in which we can describe our project and its dependencies.

Add dependencies

Why type raw JSON in the composer.json file to add dependencies? Not to mention that Composer should be invoked to install dependencies described. PhpStorm 6 comes with a new context menu which is displayed when right-clicking our project: Composer Add dependency…

Imagine we would like to create spreadsheet documents in our application. We can add a dependency to the phpexcel/phpexcel package with the click of the Install button.

PhpStorm will add the dependency to composer.json and satisfy any other required dependency automatically for us.

Command line tool support

When full control is needed, we can always use the command line tool in PhpStorm to invoke Composer. We can bring up the command line tool using the Tools Run Command… menu or with Ctrl+Shift+X (Cmd+Shift+X on Mac).

PhpStorm comes with full Composer framework support in the command line tool. When we start typing “composer”, PhpStorm will come with a list of suggestions and autocompletion support.

Please download the latest build, provide as much feedback for bugs and feature requests here, and leave questions in the comments below or in our forums!


Develop with pleasure!
– JetBrains Web IDE Team

I've always been a heavy IDE user - but for some things, like running tests, I still prefered a terminal. Recently I've played around with the in-IDE possibilities for testing and was pretty satisfied with them. Since Symfony ships with a kinda custom testing experience here's how to setup your IDE to test your Symfony applications with it - and additional features of testing within your IDE.

IDE configuration

After following the current Testing documentation it's mandatory to manually run ./bin/phpunit once in your terminal. Symfony will install its own instance of PHPUnit within your bin directory which will provide the executable phpunit file for our IDE.

After you've run this command you'll see a .phpunit directory within your bin directory.

For being able to run your tests via your IDE open your Settings window and navigate to Languages & Frameworks > PHP > Test Frameworks. Battlevoid: harbinger crack.

Click on the + icon on the right side and select PHPUnit Local. Specify the Path to phpunit.phar and select the phpunit file within your .phpunit directory. Additionally set your Default configuration file to your phpunit.xml in your Symfony directory.

Note: Keep in mind to change your configuration file to phpunit.xml instead of phpunit.xml.dist in case you're using a customized configuration file.

Open one of your tests and click on the Run test icon and select Run '<your test name>'. A window will pop up where you can edit your configuration (we'll come to this topic in a second); and, if you haven't set an interpreter for your project, you'll see a exclamation mark with a pretty weird message:

Symfony Ide Phpstorm

Clicking on the Fix button will open a window where you can set your CLI interpreter. If there's no interpreter in your dropdown click on the icon next to the dropdown and add your PHP interpreter path. This should look somewhat like this:

Note: It's recommended to have a debugger like xdebug installed. In case you're using Ubuntu simply install it with sudo apt install php-xdebug.

Now select your interpreter path and the exclamation mark should disappear - meaning you're now ready to run your tests.

Clicking on Run should now open an additional view within your IDE showing the result of your test.


Being able to run tests within your IDE is one thing - understanding and taking advantage of it is something different. Let's take a deeper look at our possibilities:


You could add configurations for every single test, for an entire test class or whatever you want. For example you could create a configuration which executes all your unit tests but not your functional tests - click on the Edit configurations item within your configurations dropdown at top of your IDE and create a new configuration for your unit tests which points to your unit tests directory.

Now selecting the Unit tests configuration will run all your unit tests - and nothing else.

Code coverage

Important: Keep in mind that this requires the xdebug extension!

If you strive for higher code coverage PhpStorm offers great tools to make your life easier. Assume the following code:

A test for this would be pretty simple:

Phpstorm Written In

A great test for a great method, nevertheless we're missing something: we've missed to test the path for non-numeric values.

If you run your tests with the Run '<your test> with Coverage PhpStorm will generate a visual representation of your tests. In case of your equals13 method it will look like this:

This makes it very easy for you to detect untested code. Additionally PhpStorm will now show a coverage report and show code coverage within your project structure.

In case you're ashamed of your low coverage and want to hide these stats again simply click on Tools > Hide coverage to make them disappear.

Auto testing

Another useful feature is auto testing, which essentially just executes your tests after your code is changed (without you having to do anything). To enable this feature simply click on the Toggle auto test button in your Run window. To adjust the delay between code changes and tests being executed you might change the value of the AutoTest Delay (click on the cogwheel icon within your Run window).

Why no terminal?

Phpstorm Download Free

Since I've acknowledged the importance of tests and started writing them I've executed them in a terminal. Throughout the time I figured out that the only arguments I'm sometimes changing are generating a coverage export (with --coverage-clover) and to just execute a single test instead of all of them (with --filter). A big drawback of that was that I always had to re-load my coverage file in case I wanted to see updated code coverage within my IDE which was really annoying.

Phpstorm Download Mac

Both of these options are fully covered within my IDE - and I could do even more without having to store a shitload of terminal commands. Clicking on a 'Play' icon may doesn't make you look like a hackerman like typing complex terminal commands would do - but it's easier and faster.

Phpstorm For Students

If there are any features regarding testing you'd think should be added to this post (or any drawbacks in your opinion using an IDE for testing instead of a terminal) please let me know in the comments.