Run/Debug Configuration: Protractor
In this dialog box, create configurations for running and debugging AngularJS unit tests using the Protractor test runner.
On this page:
- Getting access to the Run/Debug Configuration: Protractor dialog
- Protractor-specific configuration settings
- Toolbar
- Common options
Getting access to the Run/Debug Configuration: Protractor dialog
- Install and enable the Node.js plugin. The plugin is not bundled with PhpStorm, but it can be installed from the JetBrains plugin repository as described in Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins.
- Download and install the Node.js runtime environment that contains the Node Package Manager(npm).
- Using the Node Package Manager, install the Protractor test framework as described in AngularJS.
- Make sure the AngularJS plugin is activated. The plugin is not bundled with PhpStorm, but it can be installed from the JetBrains plugin repository as described in Installing, Updating and Uninstalling Repository Plugins and Enabling and Disabling Plugins.
Protractor-specific configuration settings
Item | Description |
---|---|
Name | In this text box, specify the name of the run/debug configuration. |
Share | 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. |
Configuration file | In this field, specify the location of the Protractor configuration file. Normally, the file has the extensions protractor.conf.js |
Node interpreter | In this field, specify the Node.js interpreter to use. Choose one of the configured interpreters or click and configure a new one as described in Configuring Node.js Interpreters. If you have appointed one of the installations as default, the field displays the path to its executable file. |
Protractor package | In this field, specify the Protractor installation home /npm/node_modules/protractor . If you installed Protractor regularly through the Node Package Manager, PhpStorm detects the Protractor installation home itself. Alternatively, type the path to executable file manually, or click the Browse button and select the location in the dialog box, that opens. |
Environment variables | In this field, specify the environment variables for the Node.js executable file, if applicable. Click the Browse button to the right of the field and configure a list of variables in the Environment Variables dialog box, that opens:
The definitions of variables are displayed in the Environment variables read-only field with semicolons as separators. The acceptable variables are: |
Toolbar
Common options
Item | Description | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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. | ||||||||||||||||||||||||
Share | 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, PhpStorm 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 makes sense when the 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.
|