Re: WPT meeting at TPAC!

On Wed, Oct 11, 2017 at 9:10 PM Andreas Tolfsen <ato@sny.no> wrote:

> Also sprach Geoffrey Sneddon:
>
> > Proposed agenda:
>
> […]
>
> Thanks for drafting an agenda!  It looks very good to me.
>
> > Feel free to let me know if there's anything else people want to
> > discuss.
>
> I would like to briefly talk about the current thinking around
> exposing a standard set of privileged APIs in web content to aid in
> automation.  Whether this is a WebDriver-esque API or something else
> based around CDP is subordinate.
>
> It would also be great if we could avoid hacky workarounds such
> as the proposal in [1].  If this means we need to define a
> disabled-by-default WebIDL interface for automation, so be it.
>
> I have talked to Blink developers about this in the past and
> there seemed to be shared interest in have something available to
> testharness.js tests that would allow for automation of currently
> “unautomatable” web features guarded behind permissions or
> limited by lack of UA instrumentation.
>
> The reason I want to briefly cover this is that it will have direct
> impact on the agenda for the Browser Tools- and Testing WG that is
> rechartering and meets the following day.
>
>   [1]
> https://github.com/w3c/web-platform-tests/issues/2161#issuecomment-140107936


Yep, let's make sure to present on the current trends in automation.

Hacky or not, https://github.com/w3c/web-platform-tests/pull/6897 is the
most promising direction right now, and it will allow for the APIs to
bypass WebDriver when imported into Chromium's LayoutTests/external/wpt.

There's also the mojo mocking approach used in
https://github.com/w3c/web-platform-tests/tree/master/webusb where the
testing API is rather complex.

For permissions, there's https://github.com/w3c/permissions/pull/151