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.
Once initialized, we can use the new PhpStorm 6 Composer support to add dependencies. We can right-click the project and use the *_Composer

Add dependency..._* context menu to download PHPUnit into our project. That's right: PhpStorm 6 comes with a nice UI for searching packages from the Packagist website.

After successfully installing PHPUnit and all dependencies, our project structure is now the following: the vendor folder containing all dependencies brought in using Composer, including PHPUnit.

Just like with PHPUnit installed using PEAR or as a PHAR file, we need to configure PhpStorm with the location of PHPUnit. Under settings, navigate to the *_PHP

PHPUnit_* pane. We can now select the Use custom loader option and specify the path to Composer's generated autoload.php. Optionally we can specify a default PHPUnit configuration file or a PHPUnit bootstrap file to be used when running tests.

Our run configuration will look pretty simple: specify the directory containing tests (or a specific class/method or rely on the PHPUnit configuration file to find tests to run).

We can now invoke this run configuration and have our unit tests running using the PHPUnit version installed through Composer.

Please download the latest EAP, provide as much feedback for bugs and feature requests[

http://youtrack.jetbrains.com/dashboard#newissue=yes]here, and leave questions in the comments below or in our[

http://devnet.jetbrains.com/community/wi?view=discussions]forums!
Develop with pleasure!
– JetBrains Web IDE Team