RE: Principles for emulation for new features in WPT tests

Actually we have some experiences on WebDriver integration for WPT tests, 
- Permissions API [1], this has been implemented in Chromium [2] and WPT testdriver.js [3].
- Reporting API [4].
- Generic Sensor API [5].

I am also working on WebDriver extension API definition for Remote Playback API test automation.


[1] https://w3c.github.io/permissions/#automation 
[2] https://chromium-review.googlesource.com/c/chromium/src/+/1958117 
[3] https://github.com/web-platform-tests/wpt/pull/20461  
[4] https://w3c.github.io/reporting/#automation 
[5] https://w3c.github.io/sensors/#automation

[6] https://github.com/Honry/remote-playback-test-automation/blob/master/webdriver-extension-api.md 

Thanks,
Wanming

> -----Original Message-----
> From: Marcos Caceres <marcos@marcosc.com>
> Sent: Sunday, March 8, 2020 12:16 PM
> To: David Burns <david.burns@theautomatedtester.co.uk>
> Cc: public-browser-tools-testing@w3.org; public-test-infra@w3.org; John
> Jansen <John.Jansen@microsoft.com>
> Subject: Re: Principles for emulation for new features in WPT tests
> 
> 
> 
> > 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 Monday, 9 March 2020 03:52:01 UTC