Travis CI fails to run the unit tests and still ends with successful state

[mAiNiNfEcTiOn]

Thanks in advance for your contribution. Please follow the below steps in submitting an issue, as it will help us with addressing it quicker.

Before submitting a new issue, try searching for a similar one here: https://github.com/nightwatchjs/nightwatch/search?state=open&type=Issues.

• [x] Please do not ask for assistance in the Issues list. Use the Mailing List or StackOverflow to ask questions or seek help.
• [x] Use a meaningful title that would clearly and concisely explain the problem. For instance:
• not helpful: "Issue with tags"
• much better: "Tags don't work when combined with --skiptags option in some cases"
• [x] Include a sample test (for complex scenarios) which would reproduce the problem you're experiencing. The test should be against a public url. The test and other info should be posted inline, attachments will not be accepted;
• [x] Include the verbose output, if possible (run nightwatch with --verbose argument);
• [x] Also include: Nightwatch version, Node.js version, OS version and Selenium server version (including any driver version if applicable);
• [x] Please try to avoid sending issues you have with Selenium (e.g. works perfectly in ChromeDriver but not in Safari)

---

Problem

Travis CI fails to run the unit tests and still states that the build was successful.

Possible reason

We're using node 0.10 to run the tests... perhaps upgrade to a more recent version? Something like Node 6?

Expected output

A failing build

Actual output

A passing build

1.35s$ npm test
> nightwatch@0.9.16 test /home/travis/build/nightwatchjs/nightwatch
> mocha test/src
/home/travis/build/nightwatchjs/nightwatch/node_modules/xml2json/node_modules/joi/lib/index.js:5
const Hoek = require('hoek');
^^^^^
[SyntaxError: Use of const in strict mode.]
The command "npm test" exited with 0.

Example case:

Please check this build: https://travis-ci.org/nightwatchjs/nightwatch/builds/282196126

[beatfactor]

Thanks, this is fixed now. Sorry for not merging your PR, I ended up with just using node 6 for now, and we'll add node 8 support at a later stage.