fix(launcher) workers fail to launch after tunnel

In some environments, the process which establishes the tunnel can
report that it is operational significantly before the tunnel is
actually established. This will cause subsequent calls to create a
worker to fail.

This change waits a short interval after the tunnel process has
reported itself started to allow it to actually finish establishing
the tunnel before attempting to create any workers.

Fixes #42

index.js

@@ -38,14 +38,16 @@ var createBrowserStackTunnel = function (logger, config, emitter) {
       log.error('Can not establish the tunnel.\n%s', error.toString())
       deferred.reject(error)
     } else {
-      log.debug('Tunnel established.')
-      deferred.resolve()
+      setTimeout(function() {
+        log.debug('Tunnel established.')
+        deferred.resolve()
+      }, 2000) // Give the tunnel time to become actually established
     }
   })
 
   emitter.on('exit', function (done) {
     log.debug('Shutting down the tunnel.')
-    tunnel.stop(function (error) {
+    tunnel.stop(function(error) {
       if (error) {
         log.error(error)
       }