Run/Debug Configuration: Cucumber.js
On this page:
- Getting Access to the Run/Debug Configuration: Cucumber.js Dialog Box
- Cucumber.js-Specific Configuration Settings
- Common Options
Getting Access to the Run/Debug Configuration: Cucumber.js Dialog Box
- Make sure the Node.js plugin is enabled. The plugin is bundled with WebStorm and activated by default. If not, enable it on the Plugins page of the Settings dialog box as described in Enabling and Disabling Plugins.
- Download and install the NodeJS framework that contains the Node Package Manager(npm).
- Using the Node Package Manager, install the Cucumber.js as described in Preparing to Use Cucumber.Js Test Runner.
- Make sure the Cucumber.js and Gherkin plugins are enabled. The plugins are bundled with WebStorm and activated by default. If not, enable them on the Plugins page of the Settings dialog box as described in Enabling and Disabling Plugins.
Cucumber.js-Specific Configuration Settings
|Feature file or directory||
In this text box, specify the tests to run.
Cucumber.js runs tests that are called features
and are written in the Gherkin language. Each feature is described in a separate file
with the extension |
In this text box,
specify the command line arguments to be passed to the Cucumber.js executable file, such as |
In this text box,
specify the location of the cucumber executable file, |
Type the path manually or click the Browse button and choose the file in the dialog box that opens.
|Alt+Insert||Click this button to add a new configuration to the list.|
|Alt+Delete||Click this button to remove the selected configuration from the list.|
|Ctrl+D||Click this button to create a copy of the selected configuration.|
|Edit defaults||Click this button to edit the default configuration templates. The defaults are used for newly created configurations.|
|or||Alt+Up or Alt+Down||Use these buttons to move the selected configuration or folder up and down in the list.
The order of configurations or folders in the list defines the order in which configurations appear in the Run/Debug drop-down list on the main toolbar.
|Sort configurations||Click this button to sort configurations in alphabetical order.|
|Name||In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations.|
|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.|
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, WebStorm 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 make sense, when 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.