Test Runner
In this area, specify the unit tests to launch and the command line switches to be passed to the test runner.
| Item | Description |
|---|---|
| Test scope |
In this area, specify the location of tests or the configuration file where they are listed.
|
| Configuration file |
In this text box, specify the XML file with additional test runner configuration options and possibly definitions of tests to execute.
When such file is specified, its configuration options override the default test runner configuration settings. If you have selected the Defined in the configuration file option in the Test scope area, the tests to execute are also taken from this file.
Type the path manually or click the Browse button |
| Bootstrap file |
In this text box, specify the PHP script to be always executed before launching tests. Type the path manually
or click the Browse button and select the desired folder
in the dialog that opens.
|
| Test runner options |
In this text box, specify the test runner switches .
If necessary, click |
Command Line
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.
| Item | Description |
|---|---|
| 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 |
| 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.
Type the path manually or click the Browse button and select the desired folder in the dialog that opens.
This settings 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. |
| Environment variables |
In this text box, specify the environment variables to run the PHP interpreter with, if applicable.
Click the Browse button to the right of the field and configure a list of variables
in the Environment Variables dialog box, that opens:
The definitions of variables are displayed in the Environment variables read-only field with semicolons as separators. |
Toolbar
| Item | Shortcut | Description |
|---|---|---|
| Insert | Click this button to add new configuration to the list. |
| 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 the newly created configurations. |
or
| Alt+Up or Alt+Down | Use these buttons to move the selected configuration or group of configurations (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. |
| Use this button to create a new folder.
If one or more run/debug configurations have the focus, then the selected run/debug configurations 0 are automatically moved to the newly created folder. If only a category has the focus, then an empty folder is created. |
Common options
| Item | Description | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Name | In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations. | ||||||||||||||||||
| 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.
If the directory-based project format is used, the settings for a run/debug configuration are stored in a separate xml file in the .idea\runConfigurations folder if the run/debug configuration is shared and in the .idea\workspace.xml file otherwise. If the file-based format is used, the settings are stored in the .ipr file for shared configurations or in the .iws file for the ones that are not shared. 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, IntelliJ IDEA 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 make sense, when 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 | In this area, specify the actions to be performed prior to executing the current run/debug configuration.
|
tool should be
and select the desired directory in the
and type the desired switches in the
and specify the variable name and value.
.
or
