nock@3.4.0 untested ⚠️

[greenkeeperio-bot]

Hello 👋

⚠️⚠️⚠️

nock just published its new version 3.4.0, which is covered by your current version range. No automated tests are configured for this project.

This means it’s now unclear whether your software still works. Manually check if that’s still the case
and close this pull request – if it broke, use this branch to work on adaptions and fixes.

_{Do you think getting a pull request for every single new version of your dependencies is too noisy? Configure continuous integration and you will only receive them when tests fail.} 

Happy fixing and merging 🌴

---

This pull request was created by greenkeeper.io.
It keeps your software, up to date, all the time.

_{Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster ⚡}

[germanattanasio]

looks like everything is working locally, I don't know why the tests were failing

[nfriedly]

@germanattanasio

> watson-developer-cloud@1.0.5 test /home/travis/build/watson-developer-cloud/node-sdk

> jshint --exclude ./node_modules/ && mocha --reporter spec --timeout 4000

/home/travis/build/watson-developer-cloud/node-sdk/lib/index.js:51

      throw new Error('Argument error: version was not specified');

I fixed something similar to this where the integration test was expecting auth.visual_recognintion.v1 and .v2, to be objects with credentials, but instead the encrypted auth.js just had a single set of credentials for v2 stored at auth.visual_recognition - and because it tried to create the service in the describe() block instead of in the it() block, it failed before the tests even started.

[nfriedly]

In general, this encrypted credentials business is turning out to be a bit of a PITA. Maybe we should look at storing them in env properties for travis and a .env file for local testing (?)

(Travis lets you add arbitrary private env in two places: at https://travis-ci.org/watson-developer-cloud/node-sdk/settings and storing them encrypted in .travis.yml)