Browser automation used to be easier to describe.
A test opened a page, filled in a form, clicked a button, and checked the result. The hardest parts were usually selectors, waits, and browser compatibility.
Those problems still exist, but the surface area has expanded.
Today, browser tests may need to handle streaming interfaces, MFA, AI-generated content, multiple operating systems, preview deployments, canary releases, and code changes proposed by AI assistants. The challenge is no longer just writing a script that passes.
The challenge is building a testing system that remains understandable and affordable after hundreds of tests and thousands of CI runs.
