We've all been there. A test fails in CI. You open the logs, and all you get is:

Error: expected 'tomsmith' to be 'tomsmih'

No screenshot (maybe one at the end). No timeline. No idea what the browser was doing when it happened. Just a lonely assertion error and the slow realization that you'll be running this locally six times to reproduce it.

That's why we added trace mode to @wdio/devtools-service. It's like a black box recorder for your tests, with every navigation, click, keystroke, network request, console log, and DOM snapshot, written to disk so you can replay the whole run after the fact.

Yes, we know. Playwright has an MCP server. Appium has one too. We're not first to the party.

But if you're already using WebdriverIO for cross-platform testing, you know it handles both web and mobile in one framework. Why should your AI assistant need two separate MCP servers to do the same thing?

That's why we built @wdio/mcp. One server for browsers and mobile apps, built on the WebdriverIO you already know.

The whole Webdriverio development team is stoked and proud to release WebdriverIO v9 today!

This marks the beginning of a new exciting era for all projects using WebdriverIO as their test automation tool. With the great work of browser teams that are working on e.g. Chrome and Firefox, we now enter a new era that offers much greater automation capabilities than ever before thanks to the new WebDriver Bidi protocol. With WebdriverIO v9 we have been working to be at the forefront of adopters of this new era and allow you to leverage from the power of the protocol first.