This dialog is available only when the PHP and Behat 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 Managing 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 to create a configuration to be used for running and debugging unit tests on PHP applications using the Behat framework.
Make sure the PHP and Behat 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 Managing plugins. Once enabled, the plugins are available at the IDE level, that is, you can use them in all your IntelliJ IDEA projects.
Test Runner area
In this area, specify the scenarios to launch and the command line switches to be passed to Behat.
In this area, specify the location of scenarios or the configuration file where they are listed.
Directory: select this option to have all the scenarios in a directory launched.
In the Directory field, specify the directory to search for .feature files with scenarios in. Type the path to the directory manually or click Browse and select the desired directory in the Choose Test Directory dialog that opens.
File: select this option to have all the scenarios in a specific .feature file launched.
In the File field, specify the .feature file to search the scenarios in. Type the path to the file manually or click Browse and select the desired directory in the dialog that opens.
In the Class field, specify the desired class. Type the class name manually or click Browse and select the desired class in the tree view, that opens.
Scenario: select this option to have a specific scenario launched.
In the File field, specify the .feature file to search for the scenario in. Type the filename manually or click Browse and select the desired file in the tree view, that opens.
In the Scenario field, specify the desired scenario.
Defined in the configuration file: select this option to have Behat execute the tests from a dedicated .yml configuration file.
By default, Behat 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 (behat.yml or config/behat.yml) or any other YML configuration file, which you specified as Default during the initial configuration of Behat in IntelliJ IDEA.
To have the default for all Behat run configurations file used, clear the Use alternative configuration file checkbox.
To launch scenarios from a custom configuration file, select the Use alternative configuration file checkbox and specify the location of the desired YML file in the field next to it.
To open the Behat page and specify another default configuration file to use, click the button.
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.
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 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.
When you edit a run configuration (but not a run configuration template), you can specify the following options:
In this field, specify the name for the run/debug configuration. The name will help you identify the created configuration when you choose to edit it later, or when you invoke it, for example, from the Run popup Shift+Alt+F10.
Share through VCS
Select this checkbox to put the run/debug configuration under version control and make it 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.
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.
Create a run/debug configuration.
Delete the selected run/debug configuration. Note that you cannot delete default configurations.
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 settings) for the selected run/debug configuration. The templates are displayed under the Templates node and used for newly created configurations.
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.
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:
Run External tool: select to run an external application. In the dialog that opens, select one or multiple applications you want to run. If it is not defined in IntelliJ IDEA yet, add its definition. For more information, see External tools and External Tools.
Run Another Configuration: select to execute another run/debug configuration. In the dialog that opens, select the configuration to be run.
If an error occurs during compilation, IntelliJ IDEA won't attempt to start the run/debug configuration.
Build, no error check: the same as the Build option, but IntelliJ IDEA will try to start the run/debug configuration irrespective of the compilation results.
Build Artifacts: select this option to build an artifact or artifacts. In the dialog that opens, select the artifact or artifacts that should be built.
Run Ant target: select this option to run an Ant target. In the dialog that opens, select the target to be run.
Run Grunt task: select this option to run a Grunt task.
In the Grunt task dialog 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 Gulp task.
In the Gulp task dialog 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 Maven Goal: select this option to run a Maven goal. In the dialog that opens, select the goal to be run.
Run npm Script: select this option to execute an npm script.
Start React Native Bundler: select this option to run the bundler automatically, as part of a running or debugging session. by default, this is done through react-native start. If your application uses Expo, you need to run the development server via the start npm task. To do that, click , then in the Configure React Native dialog, choose npm script and select start from the list.
If the Check errors checkbox is selected, the compiler will show all the errors and the run configuration will not start.
If the Check errors checkbox 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 generate the source maps for your CoffeeScript sources. In the dialog that opens, specify where your CoffeeScript source files are located.
Upload files to Remote Host: select this option to have the application files automatically uploaded to the server according to the default server access configuration.