The problem with modern testing tools
Modern testing tools like Playwright are designed to test a single web application, running in a single browser tab using selectors. However, selectors are often either unreliable or unavailable in complex scenarios, leading to brittle and flaky tests:| Challenge | Problem | Examples |
|---|---|---|
| Fast moving teams | Frequently change UI structure, breaking CSS/XPath selectors | Agile teams, startups, vibe-coders |
| Dynamic content | Cannot be targeted with selectors | AI chatbots, PDFs, images, videos |
| Software you donβt own | May lack proper accessibility attributes | Other websites, extensions, third-party applications |
| Multi-application workflows | Cannot be tested with web-only tools | Desktop apps, browser extensions, IDEs |
| Visual states | Impossible to verify with code-based selectors | Charts, graphs, videos, images, spelling errors, UI layout |
The TestDriver Solution
TestDriver is a complete testing platform built specifically for handling these scenarios. It consists of a Javascript SDK, hosted infrastructure, and debugging tools that make it easy to write, run, and maintain tests for your most difficult user flows.Javascript SDK
Here is an example of a TestDriver test that installs a production Chrome extension from the Chrome Web Store and verifies that it appears in the extensions menu:Installing Loom from the Chrome Web Store

