Run/Debug Configuration: PHPUnit
Use this dialog box to create a configuration to be used for running and debugging unit tests on PHP applications in the console using the PHPUnit framework.
Running PHPUnit tests requires the following prerequisites to be fulfilled:
- The PHPUnit tool should be is installed and configured on your machine.
PEARfolder should be added to the list of include paths or project content roots.
The PHP plugin is installed and enabled.
The plugin is not bundled with IntelliJ IDEA, but it can be installed from the JetBrains plugin repository as described in Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins. Once enabled, the plugin is available at the IDE level, that is, you can use it in all your IntelliJ IDEA projects.
The dialog box consists of the following areas:
Click here for the description of the options that are common for all run/debug configurations.
In this area, specify the unit tests to launch and the command line switches to be passed to the test runner.
In this area, specify the location of tests or the configuration file where they are listed.
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 and appoint the desired file in the Choose Test File dialog box, that opens.
|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 and type the desired switches in the Command Line Options dialog box. Type each switch on a new line. When you close the dialog box, the specified switches are displayed in the Test runner options text box with spaces as separators.
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.
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.
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 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.
|Move into new folder / Create new folder||Use this button to create a new folder.
If one or more run/debug configurations are in focus, the selected run/debug configurations are automatically moved to the newly created folder. If only a category is in focus, an empty folder is created.
Move run/debug configurations to a folder using drag-and-drop, or the buttons.
|Sort configurations||Click this button to sort configurations in alphabetical order.|
|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.|
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
If the file-based format is used,
the settings are stored in the
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||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.