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 PhpStorm, 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 it in all your PhpStorm 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.
Running Behat tests requires the following prerequisites to be fulfilled:
- The Behat framework is installed on your machine and integrated with PhpStorm as described in Using Behat Framework.
- The PHP and Behat plugins are installed and enabled. The plugins are bundled with PhpStorm and activated by default. If the plugins are not activated, enable them on the Plugins page of the Settings / Preferences Dialog as described in Enabling and Disabling Plugins.
The dialog box consists of the following areas:
Test Runner
In this area, specify the scenarios to launch and the command line switches to be passed to Behat.
Item | Description |
---|---|
Test scope |
In this area, specify the location of scenarios or the configuration file where they are listed.
|
Command Line
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 |
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 ![]() 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. |
Toolbar
Common Options
Item | Description | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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. | ||||||||||||||||||||||||
Temporary configurations limit | Specify here the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list. | ||||||||||||||||||||||||
Share |
Select this check box to make the run/debug configuration available to other team members.
The shared run/debug configurations are kept in separate xml files under 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, PhpStorm 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.
|