Run/Debug Configuration: Behat

This dialog box 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 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 Behat framework.

On this page:

Before you start
Test Runner area
Command Line area
Toolbar
Common options

Before you start

To run Behat tests:

Install and configure the Behat framework on your computer as described in Testing with Behat.
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 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.

Test Runner area

In this area, specify the scenarios to launch and the command line switches to be passed to Behat.

Item Description

Test scope

Item	Description
Test scope	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 text box, 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 box, that opens. File: select this option to have all the scenarios in a specific `.feature` file launched. In the File text box, 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 box, that opens. In the Class text box, 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 text box, specify the `.feature` file to search for the scenario in. Type the file name manually or click Browse and select the desired file in the tree view, that opens. In the Scenario text box, 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 text box next to it. To open the Behat page and specify another default configuration file to use, click the button.

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 text box, 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 box, that opens.
File: select this option to have all the scenarios in a specific .feature file launched.
1. In the File text box, 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 box, that opens.
2. In the Class text box, 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.
1. In the File text box, specify the .feature file to search for the scenario in. Type the file name manually or click Browse and select the desired file in the tree view, that opens.
2. In the Scenario text box, 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 text box 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, 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 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.
Environment variables	In this field, specify the environment variables be passed to the built-in server. See Environment Variables in Apache for details.

Toolbar

Item	Shortcut	Description
	`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.

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.

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.

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.

Item	Keyboard shortcut	Description
	`Alt+Insert`	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. See also Working with Artifacts. 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 option to execute an npm script. In the NPM Script dialog box that opens, specify the npm run/debug configuration settings. Compile TypeScript. Select this option to run the built-in TypeScript compiler and thus make sure that all the changes you made to your TypeScript code are reflected in the generated JavaScript files. In the TypeScript Compile Settings dialog that opens, select or clear the Check errors checkbox to configure the behaviour of the compiler in case any errors are detected: 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 have the source maps for your CoffeeScript sources generated. In the dialog that opens, specify where your CoffeeScript source files are located. Run Maven Goal. Select this option to have a a href="Maven_Support.xml">Maven goal runRun/Debug Configuration: Behat. In the dialog that opens, select the goal to be run. Run Remote External tool: Add a remote SSH external tool. Refer to the section Remote SSH External Tools for details. Run Rake task:Add a Rake task to be executed prior to running or debugging. To choose a Rake task, click the browse button , and select the desired task from the list of available tasks. Note that code completion is available here. To learn more about Rake support, refer to Rake Support section. Run JRuby compiler: choose this option to execute JRuby compiler with the specified target path, compiler process heap size, and command line parameters (if any).
	`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`	Click this icon to move the selected task one line up in the list.
	`Alt+Down`	Click this icon to move the selected task one line down in the list.
Show this page		Select this check box to have the run/debug configuration settings shown prior to actually starting the run/debug configuration.
Activate tool window		Select this option if you want the Run/Debug tool windows to be activated automatically when you run/debug your application. This option is enabled by default.

IntelliJ IDEA 2018.1 Help

Run/Debug Configuration: Behat

Before you start

Test Runner area

Command Line area

Toolbar

Common options

See Also

Procedures:

Reference:

Concepts: