Make requestedCapabilities better accessible

[christian-bromann]

Proposed changes

A lot of user have asked how to access their original capabilities from the browser object. So far we have given advise to access it via an un-documented way using: browser.options.requestedCapabilities.w3cCaps which we used internally to allow reloading the session with the same set of caps. This PR improves the access to this object by just calling browser.requestedCapabilities.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Checklist

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• I have added proper type definitions for new commands (if appropriate)

Further comments

n/a

Reviewers: @webdriverio/project-committers

[mgrybyk]

@christian-bromann browser.options.capabilities is the same as browser.requestedCapabilities ?

[christian-bromann]

browser.options.capabilities is the same as browser.requestedCapabilities ?

Yes. browser.options is the config object that you used to create the WebdriverIO session.

[mgrybyk]

So you think we need to have both options.capabilities and requestedCapabilities?

[mgrybyk]

Approving anyway as far as we can tackle questions above separately if needed.

Thank you