Run/Debug Configuration: PHPSpec
This dialog box is available only when the PHP and PHPSpec plugins are installed and enabled. The plugins are activated by default. If the plugins are disabled, enable them on the Plugins settings page as described in Enabling and Disabling Plugins.
Use this dialog box to create a configuration to be used for running and debugging unit tests on PHP applications using the PHPSpec toolset.
On this page:
Before you start
To run PHPSpec tests:
- Install and configure the PHPSpec toolset on your computer as described in Testing with PHPSpec.
- Make sure the PHP and PHPSpec plugins are enabled. The plugins are activated by default. If the plugins are disabled, enable them on the Plugins settings page as described in Enabling and Disabling Plugins.
Test Runner area
In this area, appoint the specifications to launch and the command line switches to be passed to PHPSpec.
|Test scope|| In this area, specify the location of specifications or the configuration file where they are listed. |
Command Line area
In this area, customize the behavior of the current PHP interpreter by specifying the options and arguments to be passed to the PHP executable file.
|Interpreter options|| In this text box, specify the options to be passed to the PHP executable file. They override the default behavior of the PHP interpreter and/or ensure that additional activities are performed. |
If necessary, click and type the desired options in the Command Line Options dialog box. Type each option on a new line. When you close the dialog box, they are all displayed in the Command line options text box with spaces as separators.
|Custom working directory|| In this text box, specify the location of the files that are outside the folder with tests and are referenced in your tests through relative paths. |
This setting does not block the test execution because the location of tests is always specified through a full path to the corresponding files and/or directories.
By default, the field is empty and the working directory is the root of the project.
|Environment variables||In this field, specify the environment variables be passed to the built-in server. See Environment Variables in Apache for details.|
|Alt+Insert||Click this button to add a new configuration to the list.|
|Alt+Delete||Click this button to remove the selected configuration from the list.|
|Ctrl+D||Click this button to create a copy of the selected configuration.|
|Edit defaults||Click this button to edit the default configuration templates. The defaults are used for newly created configurations.|
|or||Alt+Up or Alt+Down||Use these buttons to move the selected configuration or folder up and down in the list. |
The order of configurations or folders in the list defines the order in which configurations appear in the Run/Debug drop-down list on the main toolbar.
|Sort configurations||Click this button to sort configurations in alphabetical order.|
|Defaults||This node in the left-hand pane of the dialog box contains the default run/debug configuration settings. Select the desired configuration to change its default settings in the right-hand pane. The defaults are applied to all newly created run/debug configurations.|
|Temporary configurations limit||Specify here the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list.|
|Share|| Select this check box to make the run/debug configuration available to other team members. |
The shared run/debug configurations are kept in separate xml files under
This check box is not available when editing the run/debug configuration defaults.
|Single instance only||If this check box is selected, this run/debug configuration cannot be launched more than once. |
Every time a new run/debug configuration is launched, PhpStorm checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog box. If you click OK in the confirmation dialog box, the first instance of the runner will be stopped, and the next one will take its place.
This makes sense when the usage of certain resources can cause conflicts, or when launching two run/debug configurations of the same type consumes too much of the CPU and memory resources.
If this check box is not selected, it is possible to launch as many instances of the runner as required. So doing, each runner will start in its own tab of the Run tool window.
|Before launch||Specify which tasks must be performed before applying the run/debug configuration. The specified tasks are performed in the order they appear in the list. |