This dialog is available only when the PHP and Codeception plugins are installed and enabled. The plugins are not bundled with IntelliJ IDEA, but they can be installed on the Settings/Preferences | Plugins page as described in Installing plugins from JetBrains repository. Once enabled, the plugins are available at the IDE level, that is, you can use them in all your IntelliJ IDEA projects.
Use this dialog to create a configuration to be used for running and debugging unit tests on PHP applications using the Codeception framework.
Before you start
Test Runner area
In this area, specify the tests to launch and the command line switches to be passed to Codeception.
In this area, specify the location of unit tests or the configuration file where they are listed.
Command Line area
In this area, choose a PHP interpreter and customize its behavior by specifying the options and arguments to be passed to the PHP executable file.
|Interpreter||The list contains all the currently configured local and remote PHP interpreters. Choose one of the configured PHP interpreters from the list, or click and define a new interpreter as described in Configuring Local PHP Interpreters and Configuring Remote PHP Interpreters.|
In this field, specify the options to be passed to the PHP executable file. They override the default behavior of the PHP interpreter or ensure that additional activities are performed.
If necessary, click and type the desired options in the Command Line Options dialog. Type each option on a new line. When you close the dialog, they are all displayed in the Command line options field with spaces as separators.
|Custom working directory|
In this field, specify the folder from which tests will be executed, that is, the parent folder of the tests root as it is specified in the
In this field, 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.|
When you edit a run configuration (but not a run configuration template), you can specify the following options:
Specify a name for the run/debug configuration to quickly identify it when editing or running the configuration, for example, from the Run popup Alt+Shift+F10 .
Allow parallel run
Select to allow running multiple instances of this run configuration in parallel.
By default, it is disabled, and when you start this configuration while another instance is still running, IntelliJ IDEA suggests to stop the running instance and start another one. This is helpful when a run/debug configuration consumes a lot of resources and there is no good reason to run multiple instances.
The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your project as well as adjust default configurations templates.
|Alt+Insert||Create a run/debug configuration.|
|Alt+Delete||Delete the selected run/debug configuration. Note that you cannot delete default configurations.|
|Ctrl+D||Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.|
|The button is displayed only when you select a temporary configuration. Click this button to save a temporary configuration as permanent.|
|View and edit the template (that is, the default run/debug configuration settings). The templates are displayed under the Templates node and used for newly created configurations.|
|/||Alt+Up / Alt+Down|
Move the selected run/debug configuration up and down in the list.
The order of configurations in the list defines the order, in which the configurations appear when you choose a run/debug configuration.
Default templates of run/debug configurations are always sorted alphabetically.
Move into new folder / Create new folder. You can group run/debug configurations by placing them into folders.
To create a folder, select the configurations within a category, click , and specify the folder name. If only a category is in focus, an empty folder is created.
Then, to move a configuration into a folder, between the folders or out of a folder, use drag or and buttons.
To remove grouping, select a folder and click .
|Click this button to sort configurations in the alphabetical order.|
In this area you can specify tasks that must be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.
Click this icon to add one of the following available tasks:
|Alt+Delete||Click this icon to remove the selected task from the list.|
|Enter||Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.|
|/||Alt+Up / Alt+Down||Click these icons to move the selected task one line up or down in the list. The tasks are performed in the order that they appear in the list.|
|Show this page||Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.|
|Activate tool window|
Otherwise, if the checkbox is cleared, the tool window is hidden. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5 .