Re: Test timeouts

On 16/09/13 18:37, James Graham wrote:

> Good question. The easiest (hacky) way is to regenerate the local
> testharnessreport.js file for the testrun. However that only works if
> the multiplier (or equivalent) is fixed for the entire run. Supporting
> per-test overrides in this way would work in the absence of
> parallelisation, or with one test server per instance, but neither of
> those sound ideal. However the only way I can think of to pass in the
> timeout so that it is avaliable before any script has loaded is via a
> query parameter, which is something that I have traditionally resisted
> commandeering. All the other approaches I can think of, e.g.
> postMessaging the information in, suffer from not being able to
> guarantee that the message is received at the right time i.e. after the
> page has started loading but before the timeout is set. Suggestions are
> welcome.

Thinking about it, there are a couple of other things that would work. 
But in fact I think the best option is to make it possible to disable 
the timeout entirely in testharnessreport.js and let the external 
harness deal with all cases where the timeout is reached.

Received on Tuesday, 17 September 2013 08:56:38 UTC