What IDE do you use?

1,396 views
Skip to first unread message

Radu Amaritei

unread,
Apr 6, 2014, 7:00:28 PM4/6/14
to nightw...@googlegroups.com
  Is there an IDE with auto complete option for nightwish commands?

Thank you!

Dan Sabin

unread,
Apr 7, 2014, 5:19:33 PM4/7/14
to nightw...@googlegroups.com
I use IntelliJ (Ultimate with NodeJs plug-in)

I bring in nightwatch as a dependency in my package.json for the project. 

Vivian Ho

unread,
May 9, 2014, 5:38:58 PM5/9/14
to nightw...@googlegroups.com
I'm using WebStorm which is working fine but I don't know how to set up a debug environment for nightwatch.  Anyone using WebStorm out there?  Is it possible to debug nightwatch through IntelliJ with NodeJs plug-in, can you share?  Thanks.


On Sunday, April 6, 2014 4:00:28 PM UTC-7, Radu Amaritei wrote:

steve.calvert

unread,
May 12, 2014, 12:22:09 PM5/12/14
to nightw...@googlegroups.com
Hi Vivian,

You can indeed setup Nightwatch to debug through WebStorm!

To setup:
  1. Click Run in the main toolbar
  2. Edit Configurations
  3. On the top left of the Run/Debug Configurations dialog, click the + sign.
  4. Choose Node.js
  5. Name the new configuration "Nightwatch"
  6. WebStorm should detect your node interpreter (probably in /usr/local/bin/node)
  7. Under 'JavaScript file' enter node_modules/nightwatch/bin/runner.js
  8. Under 'Application parameters' enter the config switch with the path to your nightwatch.json, i.e. '-c tests/integration/nightwatch.json'
  9. Click Apply
To run:
  1. Click Run
  2. Debug 'Nightwatch'
Hope this helps!


On Sunday, April 6, 2014 4:00:28 PM UTC-7, Radu Amaritei wrote:

Vivian Ho

unread,
May 12, 2014, 11:19:29 PM5/12/14
to nightw...@googlegroups.com
This works, thanks so much Steve.  Very helpful.

Andrei Rusu

unread,
May 16, 2014, 8:59:28 AM5/16/14
to nightw...@googlegroups.com
Nice one! I think there was someone on Github who was asking for a WebStorm/IntelliJ runner. Maybe you would like to submit this on the nightwatch wiki?
Message has been deleted

Mary Ann May-Pumphrey

unread,
May 29, 2014, 3:07:06 PM5/29/14
to nightw...@googlegroups.com

These steps aren't working for me, possibly because I'm totally new to WebStorm. I get the following message at the bottom of the Edit configuration window after running via debug mode:

      Error: Please specify path to App JS File correctly.

I assume that it's talking about the relative path in the "JavaScript file" field, in which I have exactly what the instructions below said to use. My "Node interpreter" value is /usr/local/bin/node.

Any ideas?

--Mary Ann


On Monday, May 12, 2014 9:22:09 AM UTC-7, steve.calvert wrote:

Vivian Ho

unread,
May 30, 2014, 4:32:45 PM5/30/14
to nightw...@googlegroups.com
I have my test js files in a folder called tests, under the root folder:
root->tests->*.js

In my Application parameters I have:
-c nightwatch.json -e default -t tests/test.js

Mary Ann May-Pumphrey

unread,
Jun 24, 2014, 2:32:09 PM6/24/14
to nightw...@googlegroups.com

The error message I was experiencing when trying to run tests within WebStorm turned out to be about my "JavaScript file" value. Steve's step #7 didn't work for me because I had installed nightwatch with -g so my runner.js was elsewhere.

I can now execute tests from within WebStorm. However, I cannot do a *debug* run. If I set a breakpoint at the "signUp.goToSignUp();" line in the trivial test below, the debugger stops there, but the Firefox browser hasn't even appeared yet! If I step through to the end (still with no browser visible), the browser then pops up and the entire test runs to completion without stopping at any breakpoints.

I'm guessing this problem is due to my lack of callbacks in the tests, but I'm hoping to be proven wrong on this! I'd love it if this was another config issue.  :-)

Any ideas?

--Mary Ann

====================================================================================

var SignUpPage = require('../pages/SignUpPage')
var TermsOfUsePage = require('../pages/TermsOfUsePage')
var PrivacyPolicyPage = require('../pages/PrivacyPolicyPage')
var LoginPage = require('../pages/LoginPage')

module.exports = {
 
'SignUp Page - miscellaneous links': function(browser) { 

  var signUp = new SignUpPage(browser);

// Check functionality of each link
  signUp.goToSignUp();
  signUp.clickUserAgreementLink()
  var tos = new TermsOfUsePage(browser)
  tos.verifyPage()
 
  signUp.goToSignUp();
  signUp.clickPrivacyPolicyLink()
  var pp = new PrivacyPolicyPage(browser)
  pp.verifyPage()

  signUp.goToSignUp();
  signUp.clickAlreadyHaveAccountLink()
  var login = new LoginPage(browser)
  login.verifyPage()

  }

}

Derrick Schmidt

unread,
Jun 25, 2014, 4:57:01 PM6/25/14
to nightw...@googlegroups.com
@Mary-Ann what does your .goToSignUp() function look like? Do you do your test setup in that function?


On Sunday, April 6, 2014 4:00:28 PM UTC-7, Radu Amaritei wrote:

David Linse

unread,
Jun 25, 2014, 5:09:35 PM6/25/14
to nightw...@googlegroups.com

You should split these three tests into three separate nightwatch tests like

module.exports
 

--
You received this message because you are subscribed to the Google Groups "NightwatchJs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nightwatchjs...@googlegroups.com.
To post to this group, send email to nightw...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nightwatchjs/71d96e83-103f-4b7d-9008-a153316751ca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

David Linse

unread,
Jun 25, 2014, 5:47:36 PM6/25/14
to nightw...@googlegroups.com
Note to myself: Stop anwering mails from mobile when walking with your dog.. ;)

What i would like to write was:
Did you try to split up your three scenarios into
three separate nightwatch tests like:

module.exports = {

  'SignUp Page - TermsOfUsePage': function(browser) {  

    var signUp = new SignUpPage(browser);

    // Check functionality of each link 
    signUp.goToSignUp();
    signUp.clickUserAgreementLink()
    var tos = new TermsOfUsePage(browser)
    tos.verifyPage();
  }

  'SignUp Page - PrivacyPolicyPage': function(browser) {  

    var signUp = new SignUpPage(browser);

    signUp.goToSignUp();
    signUp.clickPrivacyPolicyLink()
    var pp = new PrivacyPolicyPage(browser)
    pp.verifyPage();
  }

  'SignUp Page - LoginPage': function(browser) {  

    var signUp = new SignUpPage(browser);

    signUp.goToSignUp();
    signUp.clickAlreadyHaveAccountLink()
    var login = new LoginPage(browser)
    login.verifyPage();
  }

  'Finally': function (browser) {
    browser.end();
  }

  // Notes:
  // maybe use globalSetup
  // to init 'signUp' (?)
}

What do you think ?

regards
~david

Satyajit Malugu

unread,
Aug 3, 2015, 10:42:11 PM8/3/15
to NightwatchJs
I changed the title of that wiki to 'Running' https://github.com/nightwatchjs/nightwatch/wiki/Running-Nightwatch-tests-in-WebStorm

Because I do not have the ability to put a break point in IDE and run to that point. If any one disagrees, it would be great! I would like to know those steps :)

Andrei Rusu

unread,
Aug 6, 2015, 6:54:13 PM8/6/15
to nightw...@googlegroups.com
Sure you can! Just add a breakpoint as you would normally do in Webstorm (refer to the Webstorm docs) and the click Debug.

--
You received this message because you are subscribed to the Google Groups "NightwatchJs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nightwatchjs...@googlegroups.com.
To post to this group, send email to nightw...@googlegroups.com.

Pete

unread,
Aug 7, 2015, 10:14:33 AM8/7/15
to NightwatchJs
Agree; I was doing this exact thing just yesterday when I wanted to be able to do some testing on my cases.

Make sure you're running in debug mode.

Abigail Watson

unread,
Aug 7, 2015, 11:38:39 AM8/7/15
to NightwatchJs
Atom.io!  We have Nightwatch set up to use Chrome, and since Atom is built in Chrome, we have a nice isomorphism between our testing, client browser, and development environment.  

It's maybe not quite as useful as Meteor's isomorphism between client/database/server; but it sure is convenient to be able to leverage existing knowledge when you want to hack on the IDE itself or the testing browser.
Reply all
Reply to author
Forward
0 new messages