How to debug angular protractor tests in WebStorm


There is a way to run and debug protractor web-tests in WebStorm. I just want to share this answer here

Problem courtesy of: Sergey Panfilov


  1. Get the node path (Type which node in your terminal)
  2. In the WebStorm: Click on "Edit configurations" - the dropdown to the left of the "Run" button (green arrow like a "play" button)
  3. Click on the "Add button" (green +) to add a new Node configuration. Select "Node.js"
  4. Fill the params:

Node interpreter: Full path to Node.js (from step 1)

Working directory: home directory for the protractor tests.

Javascript file: Full path to node_modules/protractor/lib/cli.js

Application parameters: Full path to protractor-conf.js

Now you be able to run and debug tests by clicking on "Run" or "Debug" buttons on the top of IDE

Solution courtesy of: Sergey Panfilov


I was experiencing the same problems described by comments to S.Panfilov's answer, i.e., running protractor in WebStorm worked fine, but the debugging process got stuck somewhere.

The issue is described here. It was occurring under Mac OS X with version 0.20.1 of protractor, and node v0.10.26.

The problem is solved in version 0.22.

  • Update protractor to the latest version (>= 0.22) using npm
  • Run again: node_modules/protractor/bin/webdriver-manager update
  • In WebStorm configure 'Your Protractor Conf' as described by S.Panfilov in his answer
  • Set breakpoints in your protractor test file (watch this video first)
  • Launch "Run > Debug 'Your Protractor Conf'" from WebStorm
  • Enjoy debugging
Discussion courtesy of: guidoman

For mac OSX: enter image description here on the left you can see tests folder structure

Discussion courtesy of: abrasadera

Worked for me. It was looking for the protractor.conf.js in the wrong folder. Had to look up a couple dirs.

Application parameters: ../../protractor.conf.js

Discussion courtesy of: Chester Rivas

Like some of the other responses here, I found that I could run in release but couldn't run in Debug and it would just hang at some point. I found that I had the conf file set to target two browsers and it seems that this was too much for the debugger and it would hang without any more info. Targeting only a single browser fixed this issue for me.

Discussion courtesy of: Andrew

It works! Here are my settings

enter image description here

Discussion courtesy of: David Dehghan

This recipe can be found in it's original form on Stack Over Flow.