…d "sessionSubscribe" as no Bidi session was established. Make sure you enable it by setting "webSocketUrl: true" in your capabilities and verify that your environment and browser supports it.' being printed to stdout when user deactivated Bidi protocol with "bidiProtocol" : false in Webdriver config.

Motivation/Description of the PR

Situation:

• I use "WebDriver" against Selenoid
• Selenoid does not support Bidi protocol, because of reasons
• Since Bidi protocol active became the new default behavior in CodeceptJS recently, my tests time out when executed against Selenoid 😕
• Applying workaround "bidiProtocol" : "false" in WebDriver helper enables me to still run my test against Selenoid 🙂

Problem:

• BUT, you always see this annoying error in STDOUT and you don't have the power to prevent it: 😕
  ❌ "Error: Failed to execute WebDriver Bidi command "sessionSubscribe" as no Bidi session was established. Make sure you enable it by setting "webSocketUrl: true" in your capabilities and verify that your environment and browser supports it."

Solution presented in the pull-request:

• before

await this.browser.sessionSubscribe({ events: ['log.entryAdded'] })

• after

    // Check for Bidi, because "sessionSubscribe" is an exclusive Bidi protocol feature. Otherwise, error will be thrown.
    if (this.browser.capabilities && this.browser.capabilities.webSocketUrl) {
      await this.browser.sessionSubscribe({ events: ['log.entryAdded'] })
    }

Applicable helpers:

• Playwright
• Puppeteer
• WebDriver
• REST
• FileHelper
• Appium
• TestCafe

Type of change

• 🔥 Breaking changes
• 🚀 New functionality
• 🐛 Bug fix
• 🧹 Chore
• 📋 Documentation changes/updates
• ♨️ Hot fix
• 🔨 Markdown files fix - not related to source code
• 💅 Polish code

Checklist:

• Tests have been added
• Documentation has been added (Run npm run docs)
• Lint checking (Run npm run lint)
• Local tests are passed (Run npm test)