From Christian Bromann: WebdriverIO with v6 uses Puppeteer to allow running tests on the devtools protocol (using FF Nightly), e.g.: https://gist.github.com/christian-bromann/b09411155c8c4fae5955ea780432e6df

Please note that right now we support all the features as used by webdriverIO. So nothing to do for us here, unless some edge cases are getting reported.

I started working on various high level interfaces that leverage the capabilities of the DevTools interface, particularly in the network area. It will use Puppeteer to build a secondary socket connection to the browser. You can follow the effort here: https://github.com/webdriverio/webdriverio/projects/13#card-39771208. At the same time I am extending our internal driver at Sauce Labs to support these primitives on our platform using WebDriver extensions. The internal driver is a wrapper around Chrome/Geckodriver that also connects to the DevTools interface via Puppeteer.

The features are:

• network throttling (https://github.com/webdriverio/webdriverio/pull/5472) via "Network.emulateNetworkConditions" - Note: there is a bug in Firefox which causes an error if you switch to offline mode and try to open a page - I haven't tried this on a PWA yet but the idea is to be able to test PWAs that have an offline ready version
• network mocking (https://github.com/webdriverio/webdriverio/pull/5471) via "Fetch.enable", "Fetch.requestPaused", "Fetch.fulfillRequest", "Fetch.failRequest" and "Fetch.continueRequest"

(In reply to Christian Bromann from comment #2)

• network throttling (https://github.com/webdriverio/webdriverio/pull/5472) via "Network.emulateNetworkConditions" - Note: there is a bug in Firefox which causes an error if you switch to offline mode and try to open a page - I haven't tried this on a PWA yet but the idea is to be able to test PWAs that have an offline ready version

Note that network throttling will be implemented via bug 1633831. Offline mode was implemented via bug 1553849 but it's global for now, which means it affects all the tab targets. There is a follow-up bug to make it specific to the current target.

• network mocking (https://github.com/webdriverio/webdriverio/pull/5471) via "Fetch.enable", "Fetch.requestPaused", "Fetch.fulfillRequest", "Fetch.failRequest" and "Fetch.continueRequest"

We are still working on network events and the basic ones for navigation (requestWillBeSent, and responseReceived) are implemented. We may need more before we can get started with the Fetch domain. Initial work will be done on bug 1591389.

There is nothing that we will do here for CDP. Instead WebDriver IO will make use of WebDriver BiDi.