Re: Principles for emulation for new features in WPT tests from Marcos Caceres on 2020-03-08 (public-browser-tools-testing@w3.org from January to March 2020)

From: Marcos Caceres <marcos@marcosc.com>
Date: Sun, 8 Mar 2020 15:16:22 +1100
To: David Burns <david.burns@theautomatedtester.co.uk>
Cc: "public-browser-tools-testing@w3.org" <public-browser-tools-testing@w3.org>, "public-test-infra@w3.org" <public-test-infra@w3.org>, John Jansen <John.Jansen@microsoft.com>
Message-Id: <31CEE16B-7F75-4806-9BD1-D2E7A672CAAE@marcosc.com>

> On Mar 7, 2020, at 6:36 PM, David Burns <david.burns@theautomatedtester.co.uk> wrote:
> 
> There isn’t a real set that I am aware of. We have historically left the adding of the WebDriver APIs to the spec that is adding the features and then we would be called in for wider reviews to make sure it sticks to the values of WebDriver.

I'd also be interested in defining something... or some process we should follow for getting things added to Web Driver (or contributing, while also spec'ing out how things can be tested). 

I'm wondering which specs have done this already, and how was it done? Any you would consider "best practice"™️.

Received on Sunday, 8 March 2020 04:16:40 UTC