Add detailed error message (fixes issue #58) (#285)

* The mocked/unmocked tests do not exist anymore

* Fixes #58: Include additional information when something fails when connecting, to support easier debugging of connection issues

Author: gboer

CONTRIBUTING.md

@@ -25,13 +25,7 @@ Everyone is welcome to contribute with patches, bug-fixes and new features.
 7. Push to your branch `git push origin my_branch`
 8. Create a pull request
 
-To run tests, make sure you run `npm test` but also run tests without mocks:
-
-``` sh
-npm run unmocked
-npm run mocked
-npm test
-```
+To run tests, make sure you run `npm test`.
 
 Please fix all issues identified in the pre-commit hooks before sending your patch. if you don't, we will close the patch and ask you to re-open it once you have:
 

lib/nano.js

@@ -134,11 +134,11 @@ module.exports = exports = function dbScope (cfg) {
     if (!response.status) {
       log({ err: 'socket', body: body, headers: responseHeaders })
       if (reject) {
-        reject(new Error('error happened in your connection'))
+        reject(new Error(`error happened in your connection. Reason: ${response.message}`))
       }
       if (callback) {
         const returnError = {
-          message: 'error happened in your connection',
+          message: `error happened in your connection. Reason: ${response.message}`,
           scope: 'socket',
           errid: 'request'
         }

test/nano.timeout.test.js

@@ -38,7 +38,7 @@ test('check requests timeout - nano.request', async () => {
     db: 'db',
     qs: { a: 1, b: 2 }
   }
-  await expect(nano.request(req)).rejects.toThrow('error happened in your connection')
+  await expect(nano.request(req)).rejects.toThrow('error happened in your connection. Reason: timeout of 500ms exceeded')
 })
 
 test('check request timeout (callback) - nano.request', () => {