Send INIT eagerly

There is no benefit of queuing the INIT message and it makes error handling
trickier.

Author: pontusmelke

src/v1/internal/connector.js

@@ -323,6 +323,7 @@ class Connection {
     this._packer.packStruct( INIT, [this._packable(clientName), this._packable(token)],
       (err) => this._handleFatalError(err) );
     this._chunker.messageBoundary();
+    this.sync();
   }
 
   /** Queue a RUN-message to be sent to the database */

test/v1/driver.test.js

@@ -47,4 +47,19 @@ describe('driver', function() {
     // When
     driver.session();
   });
+
+  it('should fail early on wrong credentials', function(done) {
+    // Given
+    var driver = neo4j.driver("bolt://localhost", neo4j.auth.basic("neo4j", "who would use such a password"));
+
+    // Expect
+    driver.onError = function (err) {
+      //the error message is different whether in browser or node
+      expect(err.fields[0].code).toEqual('Neo.ClientError.Security.Unauthorized');
+      done();
+    };
+
+    // When
+    driver.session();
+  });
 });