- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Tue, 17 Sep 2013 16:20:27 +0200
- To: James Graham <james@hoppipolla.co.uk>
- Cc: "public-test-infra@w3.org" <public-test-infra@w3.org>
* James Graham wrote: >In previous discussions there has been some contention about how to set >up the timeout in the first place, and how much author control there >should be. At the moment there is full author control — i.e. a precise >timeout in ms — via the setup() function in testharness.js. This >approach has one critical disadvantage; it is hard for external tools to >read the timeout. Since you might hang the whole browser it certainly >needs to be possible for the test runner to kill the whole process after >a suitable delay that must be at least as long as the test timeout. It seems strange to bother authors with this. I would expect the system to use data from past runs to detect and deal with abnormalities. In a system that also tests for performance issues you would do that anyway. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Tuesday, 17 September 2013 14:21:02 UTC