W3C home > Mailing lists > Public > public-test-infra@w3.org > January to March 2017

Re: Storage clearing

From: James Graham <james@hoppipolla.co.uk>
Date: Thu, 23 Mar 2017 19:04:05 +0000
To: Quinten Yearsley <qyearsley@chromium.org>, Dirk Pranke <dpranke@chromium.org>
Cc: Philip J├Ągenstedt <foolip@google.com>, public-test-infra <public-test-infra@w3.org>, Jeff Carpenter <jeffcarp@chromium.org>, Joshua Bell <jsbell@chromium.org>
Message-ID: <5fa47453-4c14-d801-fb5b-512c25f8b0e9@hoppipolla.co.uk>
On 23/03/17 19:00, Quinten Yearsley wrote:
 > +jsbell since this is relevant to previous conversations
 >
 > Original message for context:
 > 
https://lists.w3.org/Archives/Public/public-test-infra/2017JanMar/0040.html
 >
 > I'm not opposed to the proposal of explicitly marking tests as requiring
 > storage to be cleared; implicit in this proposal is the idea that 
generally
 > most tests should not depend on have storage cleared, and if they do
 > require that, then they should explicitly say so. Is that right?
 >
 > I know previously there was some discussion about whether storage should
 > always be cleared before the start of every test, but maybe that's not
 > necessary and would be slow?
 >
 > Anyway, I'm not exactly sure now how we would implement it for Blink, but
 > I'm confident that we could, and the proposal sounds OK to me :-)

At least the way it works for gecko seems not-obviously-fast so I'm 
reluctant to try clearing storage after every test always, although I 
agree it's the morally correct thing to do :)

In the meantime, I'll go ahead and implement this in the manifest/wptrunner.
Received on Thursday, 23 March 2017 19:04:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:34:13 UTC