Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is Protractor debugging possible in WebStorm? #133

Closed
Buthrakaur opened this issue Oct 1, 2013 · 4 comments
Closed

Is Protractor debugging possible in WebStorm? #133

Buthrakaur opened this issue Oct 1, 2013 · 4 comments

Comments

@Buthrakaur
Copy link
Contributor

Is it possible to configure WebStorm for Protractor test debugging? I was UTFG and trying different Node.js debugger options in WebStorm, but wasn't successful. I must admin that I'm total WebStorm/Node.js noob so I may be missing something very obvious..

@juliemr
Copy link
Member

juliemr commented Oct 1, 2013

I don't use webstorm so this response may be useless but - it might be worth trying by running directly from the lib/cli.js node script in the Webstorm node.js run/debug configuration, so that it effectively runs:

node debug ./lib/cli.js <conf.js>

@Buthrakaur
Copy link
Contributor Author

This unfortunately doesn't seem to work.

@andresdominguez
Copy link
Contributor

This is my config:

  1. Get the node path. Type: $which node in your terminal
  2. Click on Run > edit configurations (the dropdown to the left of the green play button)
  3. Click on the + button to add a new Node configuration. Select Node.js
  4. Under configuration enter the following:

Path to Node (node interpreter on version 7): the path from step 1
Working directory: home directory for the protractor tests. The same as the node_modules directory.
Path to Node App JS File (Javascript file on version 7): node_modules/protractor/lib/cli.js
Application parameters: protractor-conf.js

Click OK
Add a breakpoint and run debug.

@Buthrakaur
Copy link
Contributor Author

Thanks a lot - I just got it working. I was using additional Node parameter debug which was causing the troubles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants