Behat
for Windows and Linux
for OS X
Ctrl+Alt+S
This page is available only when 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.
Before you start, make sure the PHP interpreter is configured in PhpStorm on the PHP page, as described in Enabling PHP support.
On this page, configure installations of the Behat framework available through configured local and remote PHP interpreters and thus enable behaviour-driven development in PhpStorm. The page consists of two panes:
PHP interpreters
The central pane of the page shows a list of configured PHP interpreters that are associated with Behat installations. The list contains at least one item (Local) which cannot be removed.
- To add a remote interpreter to the list, click on the toolbar of the pane and choose the relevant interpreter in the Behat by remote interpreter dialog that opens. Then specify the details of the Behat installation to use with this interpreter.
- To remove a remote interpreter from the list, select the relevant interpreter and click . The Behat configuration associated with the interpreter is also removed.
See Configuring Remote PHP Interpreters for details.
Behat configuration
Item | Description |
---|---|
CLI Interpreter |
In this area,
PhpStorm displays the remote PHP interpreter to use Behat with
and the path mappings configured for this interpreter. If the selected remote PHP interpreter is running
on a Docker container or in a Vagrant instance, PhpStorm also displays the path to this container or
the Vagrant instance folder which points at the environment you are going to use.
See Configuring Remote PHP Interpreters for details.
The field is read-only, to update the chosen interpreter configuration or create a new one, click the whereupon PhpStorm brings you to the Interpreters dialog box. |
Behat Library |
In this area, specify the Behat installation to use.
|
Test Runner |
In this area,
appoint the configuration .yml file to use for launching and executing scenarios.
By default, Behat looks for a
|