On this page:
Before you start
- Make sure the Node.js runtime environment is installed on your computer.
- Install and enable the NodeJS, Cucumber.js, and Gherkin repository plugins on the Plugins page as described in Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins.
npm install cucumberfor local installation in your project.
npm install -g cucumberfor global installation.
npm install --save-dev cucumberto install Cucumber.js as a development dependency.
Cucumber.js tests are launched only through a run/debug configuration.
- Open the Run/Debug Configuration dialog box ( on the main menu).
- Click on the toolbar and select Cucumber.js from the list. The Run/Debug Configuration: Cucumber.js dialog box opens.
- In the Feature file or directory text box, specify the tests to run. Type the path to a specific
.featurefile or to a folder, if you want to run a bunch of features.
- In the Executable path text box, specify the location of the
cucumber-js.bat, or other depending on your operating system. The location depends on the installation mode.
- Optionally, specify the command line arguments to be passed to the executable file, such as
--tags TAG_EXPRESSION), or
--coffee. For details, see native built-in help available through the
- Select the Cucumber.js run/debug configuration from the list on the main toolbar and click to the right of the list.
- The test server starts automatically without any steps from your side. View and analyze messages from the test server in the Run tool window.
- Monitor test execution in the Test Runner tab of the Run tool window as described in Monitoring and Managing Tests.
With PhpStorm, you can jump between a file and the related test file. Navigation from a test result in the Test Runner Tab to the test is also supported.
To jump from a test result to the test
Select the test name in the Test Runner tab and choose Jump to Source on the context menu. The test file opens in the editor with the cursor placed at the test definition.