Login/Register
How to debug angular protractor tests in WebStorm
Asked Answered
Solved javascriptangularjsnode.jsprotractorwebstorm
E

7

30

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

Edmiston answered 22/11, 2013 at 4:37 Comment(0)
E
53
  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

Edmiston answered 22/11, 2013 at 4:37 Comment(8)
Hmm.. may be few steps didn't clear? Please give more info, I'll try to help you – Edmiston
yeah, didn't work for me either; posted at length about it here- https://mcmap.net/q/472351/-debugging-protactor-with-without-webstorm/537913 – Gordan
In my case it doesn't start the tests if I use "Debug" (bug icon) and it starts the tests if I use "Run" (play icon), but it doesn't stop anywhere. – Variform
Looks like with doing the "Debug" option (bug icon), it adds --debug-brk=62532 --nolazy to the node command line. – Variform
An additional thing, in this video (youtube.com/watch?v=VLMyI7QKcwg) looks like web storm identifies the breakpoint with the usual "tick" inside, whereas in my case, it doesn't. – Variform
I think it should be protractor.conf.js not protractor-conf.js. – Botanize
In my case - it "runs" fine. while debugging, it gives error "Process finished with exit code 139" I am on Mac. – Diabetic
In my case the javascript file is the following: node_modules/protractor/bin/protractor – Guipure
D
15

It works! Here are my settings

enter image description here

Dilettante answered 1/10, 2015 at 9:12 Comment(4)
this only works for me if I add '--harmony' to Node parameters – Lucaslucca
Path is now node_modules/protractor/built/cli.js – Poynter
The full path on my Mac was /usr/local/lib/node_modules/protractor/built/cli.js – Botanize
Also make sure to keep the ng serve running, the web storm just runs the protractor test doesn't starts the server unlike command line. – Needless
C
3

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
Cerecloth answered 8/5, 2014 at 12:26 Comment(0)
M
2

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

Madelle answered 9/8, 2016 at 11:25 Comment(0)
M
1

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

Moss answered 1/4, 2014 at 16:28 Comment(0)
K
1

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.

Kunlun answered 24/8, 2015 at 13:0 Comment(0)
B
1

By the way if you need to pass additional parameters here is the configuration you need

  • Select ‘Node.js’ configuration from the list
  • Name: ‘Protractor’
  • Node interpreter: ‘C:\Program Files\nodejs\node.exe’
  • Node parameters: ‘’
  • Working directory:
  • JavaScript file: ‘~\AppData\Roaming\npm\node_modules\protractor\built\cli.js’
  • Application parameters, this is where you specify path to your conf, relatively to working directory^ and then parameters like this: ‘e2e/settings/configs/protractor.custom.conf.js --baseUrl="https://stage.mysite.com" --params.login="testuser" --params.password="test_USER00"’
  • Environment variables: ‘’

This config works great in my project, where we solely rely on async/await syntax

Bordy answered 14/12, 2018 at 15:57 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.