Test Automation

TLDR; Selenium WebDriver Course course has been released to YouTube as a 16 hour video. And split into 8 smaller 1-4 hour video chunks

In January 2026, I was guest on the “How to Test This?” Podcast.

TLDR; Record and Playback is a notoriously bad way to automate. But what if we record, then have AI write code from the recording? Answer: it is a little better.

TLDR; OpenCode is a free and easy to use AI coding agent, it can be coupled with free models and MCP servers to create test automation code quickly and easily.

TLDR; a simple WebDriver Test is not production ready code, but when we refactor it to use JUnit effectively, add some Page Objects, Abstraction and a little bit of Synchronization and we have all the makings of quality execution code.

TLDR; The Deque Axe Core library works with WebDriver and Playwright to generate an automated accessibility report.

TLDR; I tried to objectively assess the web automation tool market. And as a new development team I’d probably choose Playwright, but as someone experienced in automating the web I’d still choose WebDriver.

In this podcast I discuss test automation biases and how to avoid them.

TLDR; Kerry McKeever explained and demonstrated his AG Grid automation plugin for Cypress, showing where to find the code and how to create custom commands for cypress.

TLDR; Can Test Automation mind defects? Yes, both regressions and new defects by adding more variation into the paths or data used.

Statements like “Test automation should-not/can-not/will-not find defects” do not completely match my experience. In my experience, Automated Execution can be used to help find defects and frequently does. Not just ‘regressions’ but ’new defects’ as well.