Updates integration tests to not run locally

Since the repo doesn't contain auth.js by default, this re-arranges the
integration test file to not run if the file isn't present, which
should make it easier for new developers to get up and running: Rather
than needing to always comment out the integration test file, the
project will just work.

Author: mfulgo

CONTRIBUTING.md

@@ -28,8 +28,8 @@ If you want to contribute to the repository, follow these steps:
 
 1. Fork the repo.
 1. Develop and test your code changes: `npm install -d && npm test`. Make sure you work in the `dev` branch. PLEASE don't do your work in `master`.
-1. In order to run the tests locally you should comment out `test.integration-all-services.js` because the integration tests require you to have service credentials for all the services.
-Travis will run the integration tests for all services once the changes are merged in.
+1. Travis-CI will run the integration tests for all services once your changes are merged.
+If you wish to run integration tests locally you must provide service credentials for all the services. See `test/test.integration-all-services.js`.
 1. Add a test for your changes. Only refactoring and documentation changes require no new tests.
 1. Make the test pass.
 1. Commit your changes.

test/test.integration-all-services.js

@@ -1,9 +1,12 @@
 'use strict';
 
+var fs = require('fs');
+
+if (fs.existsSync(__dirname + '/resources/auth.js')) {
+
 var nock = require('nock');
 var watson = require('../lib/index');
 var auth = require('./resources/auth');
-var fs = require('fs');
 var assert = require('assert');
 
 var mobydick = fs.readFileSync(__dirname + '/resources/mobydick.txt', 'utf8');
@@ -14,8 +17,6 @@ var TEN_SECONDS = 10000;
 var FIVE_SECONDS = 5000;
 var TWO_SECONDS = 2000;
 
-if (fs.existsSync(__dirname + '/resources/auth.js')) {
-
 describe('integration-all-services', function() {
 
   this.slow(TWO_SECONDS); // this controls when the tests get a colored warning for taking too long