Testing with Behat
Native support of Behat in IntelliJ IDEA includes:
Recognition of and coding assistance for feature scenario files and PHP scenario definition files.
Gherkin syntax support in feature files:
@thenannotations in definition files.
Setting correspondence between scenarios and their definitions through regular expressions in accordance with the PCRE standard for Behat 2.4 and PCRE+ for Behat 3.0. Turnip expressions are also welcome.
Before you start
Note that Behat 3 requires PHP 5.5 and later.
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.
Downloading and installing Behat
Before you start, make sure Composer is installed on your machine and initialized in the current project as described in Composer Dependency Manager.
Download Behat installation package manually
Download behat.phar from the Behat Downloads page and save it on your computer:
If you need full coding assistance in addition to the ability of running Behat tests, store behat.phar under the root of the project where Behat will be later used.
If you only need to run Behat tests and you do not need any coding assistance, you can save behat.phar outside the project.
Download and install Behat with Composer
From the context menu of composer.json, choose . Alternatively choose from the main menu.
In the Manage Composer Dependencies Dialog that opens, select the behat/behat package from the Available Packages list, possibly using the search field.
Learn more about installing Behat from Behat Official website.
Integrating Behat with IntelliJ IDEA in a project
Configure Behat automatically
Store the behat.yml or behat.yml.dist configuration file under the project root.
Configure Behat manually
On the Test Frameworks page that opens, click in the central pane and choose the configuration type from the list:
In local configurations, the default project PHP interpreter is used, see Default project CLI interpreters for details.
To use Behat with a remote PHP interpreter, choose one of the configurations in the dialog that opens:
In the Behat Library area, specify the location of the Behat executable file or behat.phar archive.Click next to the Path to Behat directory or phar file field. IntelliJ IDEA detects the version of Behat and displays it below the field.
In the Test Runner area, appoint the configuration YML file to use for launching and executing scenarios.
By default, Behat looks for a behat.yml configuration file in the project root folder or in the config folder. You can appoint a custom configuration file.
Clear the Default configuration file checkbox to have Behat use the behat.yml configuration file from the project root folder or from the config folder. If no such file is found, test execution fails, therefore it may be more reliable to specify the configuration file explicitly.
In the field, specify the location of the configuration file to use. Type the path manually or click and choose the file in the dialog that opens.
Running and debugging Behat tests
For information about writing Behat features, refer to the Behat Documentation.
Run or debug Behat tests
Save an automatically generated default configuration
Create a custom run/debug configuration
In the Project tool window, select the file or folder with the tests to run and choose Create run configuration from the context menu. Alternatively, choose from the main menu, then click and choose Behat from the list.
In the Run/Debug Configuration: Behat dialog that opens, specify the scenarios to run and customize the behavior of the current PHP interpreter by specifying the options and arguments to be passed to the PHP executable file.
Monitoring Behat test results
The tab is divided into 2 main areas:
The left-hand area lets you drill down through all unit tests to see the succeeded and failed ones. You can filter tests, export results, and use the context menu commands to run specific tests or navigate to the source code.
The right-hand area displays the raw Behat output.