This feature is supported in the Ultimate edition only.
This dialog box is available only when the PHP and PHPSpec plugins are installed and enabled. The plugins are not bundled with IntelliJ IDEA, but they 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 plugins are available at the IDE level, that is, you can use them in all your IntelliJ IDEA projects.
Use this dialog box to create a configuration to be used for running and debugging unit tests on PHP applications using the PHPSpec toolset.
In this area, appoint the specifications to launch and the command line switches to be passed to PHPSpec.
In this area, specify the location of specifications or the configuration file where they are listed.
Directory: select this option to have all the specifications in a directory launched.
In the Directory text box, appoint the directory to search for *Spec.php files with specifications in. Type the path to the directory manually or click the Browse button and select the desired directory in the Choose Test Directory dialog box, that opens.
File: select this option to have all the specifications in a particular *Spec.php file launched.
In the File text box, specify the *Spec.php file to search the specifications in. Type the path to the file manually or click the Browse button and select the desired directory in the dialog box, that opens.
In the Class text box, specify the desired class. Type the class name manually or click the Browse button and select the desired class in the tree view, that opens.
Specification: select this option to have a particular specification launched.
In the File text box, specify the *Spec.php file to search for the specification in. Type the file name manually or click the Browse button and select the desired file in the tree view, that opens.
In the specification text box, type the desired specification.
Defined in the configuration file: select this option to have PHPSpec execute the tests from a dedicated .yml configuration file.
By default, PHPSpec uses the configuration file appointed in the Test Runner area of the Test Frameworks page. In its turn, this can be either the native configuration file (phpspec.yml or phpspec.yml.dist) or any other .yml configuration file which you specified as Default during the initial configuration of PHPSpec in IntelliJ IDEA.
To have the default for all PHPSpec run configurations file used, clear the Use alternative configuration file check box.
To launch specifications from a custom configuration file, select the Use alternative configuration file check box and specify the location of the desired .yml file in the text box next to it.
To open the PHPSpec page and specify another default configuration file to use, click the button.
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.
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.
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.
Click this button to sort configurations in alphabetical order.
In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations.
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 .idea\runConfigurations folder if the run/debug configuration is shared, or 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 otherwise.
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 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.
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.
Click this icon to add a task to the list. Select the task to be added:
Run External tool. Select this option to run an application which is external to IntelliJ IDEA. In the dialog that opens, select the application or applications that should be run. If the necessary application is not defined in IntelliJ IDEA yet, add its definition. For more information, see Configuring Third-Party Tools and External Tools.
Build Artifacts. Select this option to have an artifact or artifacts built. In the dialog that opens, select the artifact or artifacts that should be built.
Run Another Configuration. Select this option to have another run/debug configuration executed. In the dialog that opens, select the configuration to run.
This option is available only if you have already at least one run/debug configuration in the current project.
Run Ant target. Select this option to have an Ant target run. In the dialog that opens, select the target to be run. For more information, see Ant.
Run Grunt task. Select this option to run a Grunt task. In the Grunt task dialog box that opens, specify the Gruntfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Grunt tool.
Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the grunt-cli package.
Run Gulp task. Select this option to run a Grunt task. In the Gulp task dialog box that opens, specify the Gulpfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Gulp tool.
Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the gulp package.
Run npm Script. Select this check box to execute an npm script. In the NPM Script dialog box that opens, specify the package.json file where the required script is defined, select the script to execute, choose the command to apply to it, and specify the arguments to execute the script with.
Specify the location of the Node.js interpreter and the parameters to pass to it.
If the Check errors check box is selected, the compiler will show all the errors and the run configuration will not start.
If the Check errors check box is cleared, the compiler will show all the detected errors but the run configuration still will be launched.
Generate CoffeeScript Source Maps. Select this option to have the source maps for your CoffeeScript sources generated. In the dialog that opens, specify where your CoffeeScript source files are located. For more information, see CoffeeScript.
Run Maven Goal. Select this option to have a Maven goal run. In the dialog that opens, select the goal to be run.