Nightwatch not writing XML files to output_folder

[Abigail Watson]

Hi all,

Got a problem that I don't know how to diagnose/analyze.  

Here's the background:   I've been running Nightwatch tests against Meteor apps for the past 6 months or so, no problems.  We've been experimenting with continuous integration, and have tried four different configurations.  One with Jenkins (failed), one with Velocity (failed), one with Jenkins (succeeded), one with Velocity (succeeded).  So, our CI environment is not completely set up, which is what we're trying to do; but we're not starting at square 1 either.  We've had some success.  

The problem:  the past month has been very hectic, and somewhere along the way, Nightwatch stopped writing it's jUnit XML files.  The last time it worked was around December 21st with Nightwatch 0.5.35.  Now, when we run Nightwatch nothing is written to the output_folder.  

What we've tried:  We know that the json configuration file is being read, because it parses the src_folders field, reads the tests, and runs them correctly.  We know that Selenium and Firefox and everything else is installed because the tests are running.   We also tried manually specifying the output_folder with the --output flag, but got nothing.  We've tried the --verbose flag, and again nothing.  We've chmodded 777 the entire project, and chowned it to myusername:wheel.  So, it doesn't seem to be file permissions.  

If the output_folder doesn't exist, Nightwatch will create it.  So that's interesting, and possibly an important clue.  I seem to remember it producing an error message in the past, that the directory doesn't exist.  But the last time I got that error, we were using Nightwatch 0.5.3.

So, yeah.  Uh, help?  How do I even diagnose this?  We're not getting any error messages, and it's just failing silently, and not writing any output files.  Is there any way we can peek at the jUnit XML subsystem and monitor it?  Any way to enable a debugging mode?  Etc?

Thanks much!

Abigail

[Andrei Rusu]

Here's a guide on how to debug with Webstorm:
https://github.com/beatfactor/nightwatch/wiki/Debugging-Nightwatch-tests-in-WebStorm.

Version 0.5.36 downgraded the ejs (templating engine) version to the
last one which was compatible with nightwatch. See here:
https://github.com/beatfactor/nightwatch/commit/c1894e0904869d2523ab7cb85a6bb4a0f9e6d5b9

Your problems are probably related. As a temporary fix you can install
the last working version with npm install night...@0.5.35.

> --
> 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/d516996b-715d-4528-9f3b-36eabe965fd8%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Abigail Watson]

Thank you for the suggestions, Andrei! We'll give Webstorm a try, and see what we can find! :)

[Andrei Rusu]

You might also try deleting the ejs folder from your node_modules and
do another npm install nightwatch.

On Wed, Jan 21, 2015 at 3:12 PM, Abigail Watson <awats...@gmail.com> wrote:
> Thank you for the suggestions, Andrei! We'll give Webstorm a try, and see what we can find! :)
>

> --
> 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/07983b71-da91-4a04-a7d3-20a2a7297fe0%40googlegroups.com.

[Abigail Watson]

Thanks for all the help!  We got it working!  The Meteor Velocity project requires a bridge to the Nightwatch libraries, and we had an outdated dependency buried in a file.  We're now on the latest 0.5.36, and everything is humming along smoothly.  :)