Cucumber.js

1. Download and install Node.js.

2. Install the Cucumber.js and Gherkin repository plugins on the Plugins page as described in Managing plugins.

• In the embedded Terminal (Alt+F12), type one of the following commands:

  • npm install cucumber for local installation in your project.

  • npm install -g cucumber for global installation.

  • npm install --save-dev cucumber to install Cucumber.js as a development dependency.

  See also Cucumber.js demo on the Cucumber.js official website.

1. Place the cursor at the step without a definition, press Alt+Enter, and select Create step definition or Create all step definitions.

   

   Alternatively, hover the mouse over the step and use the links in the popup.

   

2. In the dialog that opens, specify the name for the new file, the language to write the definitions in, and the version of Cucumber.js.

   

   If such file already exists, IntelliJ IDEA displays a popup where you have to select a file to add the definition to or choose to create a new file.

   

Create a Cucumber.js run configuration

1. Open the Run/Debug Configuration dialog (Run | Edit Configurations on the main menu), click in the left-hand pane, and select Cucumber.js from the list. The Run/Debug Configuration: Cucumber.js dialog opens.

2. In the Feature file or directory field, specify the tests to run. Type the path to a specific .feature file or to a folder, if you want to run a bunch of features.

3. Specify the Node.js interpreter to use. This can be a local Node.js interpreter or a Node.js on Windows Subsystem for Linux.

4. In the Cucumber package field, specify the path to the folder where the cucumber package is stored.

5. Specify the working directory of the application. By default, the Working directory field shows the project root folder. To change this predefined setting, specify the path to the desired folder or choose a previously used folder from the list.

6. Optionally:

   • In the Name Filter field, type the name of a specific scenario to run instead of all the scenarios from the feature file or directory.

   • Specify the command line arguments to be passed to the executable file, such as -r (--require LIBRARY|DIR), -t (--tags TAG_EXPRESSION), or --coffee. For details, see native built-in help available through the cucumber-js --help command.

Run tests via a run configuration

1. Select the Cucumber.js run/debug configuration from the list on the main toolbar and click  to the right of the list.

2. The test server starts automatically without any steps from your side. View and analyze messages from the test server in the Run tool window.

3. Monitor test execution in the Test Runner tab of the Run tool window.

Run and debug tests from a test file

• To run or debug a single test, open the test file in the editor, place the cursor at the scenario to run or debug, and then select Run Scenario: <scenario name> or Debug Scenario: <scenario name> from the context menu.

• To run or debug all tests from a single test file, open the test file in the editor or select it in the Project tool window and choose Run <test file name> or Debug <test file name> from the context menu.

In either case, IntelliJ IDEA creates a run/debug configuration which you can save and use later.

• Open the file in the editor and select Go To | Test or Go To | Test Subject from the context menu, or just press Ctrl+Shift+T.

• To jump from a step in a .feature file to the step definition, press and hold Ctrl (or Cmd for macOS), hover over the step, and click the step when it turns into a link.

  

• To jump from a test result to the test, select the test name in the Test Runner tab and choose Jump to Source from the context menu. The test file opens in the editor with the cursor placed at the test definition.