Thanks for raising the PR.

I think this is an issue with the docs. The user is suppose to use calls to receive these information. matches is more an internal object for this.

Thanks for raising the PR.

I think this is an issue with the docs. The user is suppose to use calls to receive these information. matches is more an internal object for this.

Ok, i will update the docs in this PR. Also, about mocks: i need an ability to check if mock (spy) has some pending requests. Will you approve a feature, which emits something like onRequest, onResponse on request and response accordingly? (i see how it can be done with devtools mock, but not with webdriver one)

Will you approve a feature, which emits something like onRequest, onResponse on request and response accordingly?

Seems like a reasonable feature request. Yeah totally!

(i see how it can be done with devtools mock, but not with webdriver one)

For WebDriver we will have to use the new WebDriver Bidi features which have not landed yet. While you can already get request information, it is not yet possible to mock/replace requests and responses. So we can ignore this for now and have it throw an Not yet implemented error. Note that the WebDriver part of the mocking feature currently only runs when using Sauce Labs.

Also, do you mind if i add documentation about WDIO_LOG_LEVEL environment variable? It looks like a part of public api (because here it assumes, it can be set from the outside) but is not being documented. I want to use this env variable in my code (i already asked about this in gitter, but didn't got the answer to my question), but i'm scared of using undocumented variables

Also, do you mind if i add documentation about WDIO_LOG_LEVEL environment variable?

Good call, let's add it to https://webdriver.io/docs/api/environment