WebStorm 2024.2 Help

Protractor

Protractor is a test framework for Angular and AngularJS applications. Protractor executes tests against your application running in a real browser, which ensures correctness and trustworthiness of test results. WebStorm integrates with Protractor, so you can run and debug your tests from inside the IDE. You can see the test results in a treeview and easily navigate to the test source from there.

Before you start

  1. Make sure you have Node.js on your computer.

  2. Make sure the Angular and AngularJS plugin is enabled in the settings. Press Ctrl+Alt+S to open settings and then select Plugins. Click the Installed tab. In the search field, type Angular and AngularJS. For more information about plugins, refer to Managing plugins.

Install Protractor

You can install Protractor locally, in your project, or globally. Global installation is preferable.

Install Protractor globally

  1. In the embedded Terminal (Alt+F12) , type:

    npm install -g protractor

  2. To download the necessary binaries, type webdriver-manager update. See also Getting Started on the Protractor official website.

Run tests

Protractor tests are launched only through a run/debug configuration.

Create a Protractor run configuration

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

  2. Specify the Node.js interpreter to use.

    If you choose the Project alias, WebStorm will automatically use the project default interpreter from the Node interpreter field on the Node.js page . In most cases, WebStorm detects the project default interpreter and fills in the field itself.

    You can also choose another configured local or remote interpreter or click the Browse button and configure a new one.

    For more information, refer to Configuring remote Node.js interpreters, Configuring a local Node.js interpreter, and Using Node.js on Windows Subsystem for Linux.

  3. Specify the location of the protractor package and the path to the protractor.conf.js configuration file. If you followed the standard installation, WebStorm detects all these paths and displays them in the corresponding fields.

  4. Specify the tests to run. This can be a specific test or suite, an entire test file, or a folder with test files.

Run tests via a run configuration

  1. Start the Selenium Server manually or configure it to start automatically in protractor.conf.js. For more information, refer to the Protractor official website.

  2. Select the Protractor run/debug configuration from the list of configurations and click the Run icon   in the list or on the toolbar.

    Select run/debug configuration
  3. View and analyze messages from the server in the <current_run_configuration_name> tab of the Run tool window.

Navigation

With WebStorm, you can jump between a file and the related test file or from a test result in the Test Runner Tab to the test.

  • To jump between a test and its subject or vice versa, 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 test result to the test definition, click the test name in the Test Runner tab twice, or select Jump to Source from the context menu, or just press F4. The test file opens in the editor with the caret placed at the test definition.

Debug tests

A debugging session for Protractor tests is started only through a run/debug configuration.

To start debugging tests

  1. Create a Protractor run/debug configuration as described above.

  2. Select the Protractor run/debug configuration from the list of configurations and click Run with Coverage   in the list or on the toolbar.

    Select run/debug configuration
  3. In the Debug tool window that opens, proceed as usual: step through the tests, stop and resume test execution, examine the test when suspended, run JavaScript code snippets in the Console, and so on.

Last modified: 25 June 2024