Test Frameworks
Choose the type of the PHP interpreter to run the tests with. Click
and choose the relevant configuration type from the list:
You can configure any test framework to use with a local or remote PHP interpreter.
For a remote configuration, choose one of the configured PHP interpreters:
In the right-hand pane, choose where to take the test framework from.
For Behat, PHPSpec, and Codeception, type the path to the framework executable.
For PHPUnit, specify the type of framework installation you are using, the available options are composer autoloader autoload.php or a phpunit.phar archive.
Check the chosen remote PHP interpreter and path mappings.
Optionally, specify the configuration file. For PHPUnit, you can also specify a bootstrap file to use.
Use Composer autoloader | Choose this option to run PHPUnit installed by the Composer dependency manager. The package is retrieved and loaded by the autoload.php file from the vendor folder. Specify the location of autoload.php in the Path to script field. |
Path to phpunit.phar | Choose this option to run PHPUnit from the phar archive.
|
The remote PHP CLI Interpreter to use PHPUnit with. The CLI Interpreter field is read-only. Click
to update the chosen interpreter in the Interpreters dialog. The Path Mappings between your local sources and the sources inside the Vagrant instance, or the Docker container, or on the remote host.
The Docker container settings that will be used to start the container from an image. These settings may include the volume configuration, the exposed ports, the network, and so on.
In most cases, PhpStorm detects the path mappings and the container settings and fills in all the fields automatically. Alternatively, click next to the field and specify the settings manually. For more information, refer to Configure remote PHP interpreters.
You can also type the path to a bootstrap file to have a PHP script always executed before launching tests. In the field, specify the location of the script. Type the path manually or click 
and select the desired folder in the dialog that opens.
Default configuration file | Select this checkbox to specify your own XML configuration file. This file will be later used as default in all PHPUnit run/debug configurations. Note that you can also provide an alternative configuration file when editing a PHPUnit run/debug configuration. In the field, specify the location of the configuration file to use. Type the path manually or click Clear the checkbox to have PHPUnit use the phpunit.xml or phpunit.xml.dist configuration file from the project root folder. If no such file is found, test execution fails, therefore it may be more reliable to specify the configuration file explicitly. |
Default bootstrap file | Select this checkbox to have a PHP script always executed before launching tests. In the field, specify the location of the script. Type the path manually or click |
The remote PHP CLI Interpreter to use Behat with. The CLI Interpreter field is read-only. Click
to update the chosen interpreter in the Interpreters dialog. The Path Mappings between your local sources and the sources inside the Vagrant instance, or the Docker container, or on the remote host.
The Docker container settings that will be used to start the container from an image. These settings may include the volume configuration, the exposed ports, the network, and so on.
In most cases, PhpStorm detects the path mappings and the container settings and fills in all the fields automatically. Alternatively, click next to the field and specify the settings manually. For more information, refer to Configure remote PHP interpreters.
Path to Behat executable | In this field, specify the location of the behat.phar archive or the folder with the Behat executable file. Behat does not necessarily have to be installed under the current project root. You can type the path manually or click |
Behat releases | Click this link to navigate to the Behat repository on GitHub where you can choose the relevant version of behat.phar archive. |
Behat version | This read-only field shows the version of the specified Behat installation. PhpStorm detects the version when you click the Refresh icon |
. The default value is Default configuration file | Select this checkbox to specify your own YML configuration file. This file will be later used as default in all Behat run/debug configurations. In the field, specify the location of the configuration file to use. Type the path manually or click Clear the checkbox to have Behat use the behat.yml or behat.yml.dist configuration file from the project root folder. If no such file is found, test execution fails, therefore it may be more reliable to specify the configuration file explicitly. |
The remote PHP CLI Interpreter to use Codeception with. The CLI Interpreter field is read-only. Click
to update the chosen interpreter in the Interpreters dialog. The Path Mappings between your local sources and the sources inside the Vagrant instance, or the Docker container, or on the remote host.
The Docker container settings that will be used to start the container from an image. These settings may include the volume configuration, the exposed ports, the network, and so on.
In most cases, PhpStorm detects the path mappings and the container settings and fills in all the fields automatically. Alternatively, click next to the field and specify the settings manually. For more information, refer to Configure remote PHP interpreters.
Path to Codeception executable | In this field, specify the location of the codeception.phar archive or the folder with the Codeception executable file. |
Codeception releases | Click this link to navigate to the Codeception repository on GitHub where you can choose the relevant version of codeception.phar archive. |
Codeception version | This read-only field shows the version of the specified Codeception installation. PhpStorm detects the version when you click |
Default configuration file | Select this checkbox to specify your own YML configuration file. This file will be later used as default in all Codeception run/debug configurations. In the field, specify the location of the configuration file to use. Type the path manually or click Clear the checkbox to have Codeception use the codeception.yml or codeception.dist.yml configuration file from the project root folder. If no such file is found, test execution fails, therefore it may be more reliable to specify the configuration file explicitly. |
The remote PHP CLI Interpreter to use PHPSpec with. The CLI Interpreter field is read-only. Click
to update the chosen interpreter in the Interpreters dialog. The Path Mappings between your local sources and the sources inside the Vagrant instance, or the Docker container, or on the remote host.
The Docker container settings that will be used to start the container from an image. These settings may include the volume configuration, the exposed ports, the network, and so on.
In most cases, PhpStorm detects the path mappings and the container settings and fills in all the fields automatically. Alternatively, click next to the field and specify the settings manually. For more information, refer to Configure remote PHP interpreters.
Default configuration file | Select this checkbox to specify your own YML configuration file. This file will be later used as default in all PHPSpec run/debug configurations. In the field, specify the location of the configuration file to use. Type the path manually or click Clear the checkbox to have PHPSpec use the phpspec.yml or phpspec.yml.dist configuration file from the project root folder. If no such file is found, test execution fails, therefore it may be more reliable to specify the configuration file explicitly. |
Thanks for your feedback!