Yeah I meant to reply its actually good, I tried to do it the other way and
it was a no go, might lower the interval though
On Mar 1, 2014 9:55 AM, "Dale Harvey" <notifications@github.com> wrote:

> In bin/test-browser.js:
>
> > -  client = wd.promiseChainRemote();
> > -  client
> > -    .init({browserName: browser})
> > -    .get(testUrl)
> > -    .setAsyncScriptTimeout(testTimeout)
> > -    .executeAsync(script)
> > -    .then(testComplete, testError);
> > +  var opts = {
> > +    browserName: browser,
> > +    tunnelTimeout: testTimeout,
> > +    'max-duration': 60 * 30,
> > +    'command-timeout': 599,
> > +    'idle-timeout': 599
> > +  };
> > +
> > +  client.init(opts).get(testUrl, function () {
>
> The interval is on purpose, saucelabs / browserstack will often kill
> sessions due to inactivity, there are timeouts to configure sometimes, but
> the behaviour is unreliable and polling it just safer
>
> (also its nice to get the progress)
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/daleharvey/pouchdb/pull/1544/files#r10191007>
> .
>