Every engineering team knows the tension. You ship fast, but testing can't keep up. Regression suites grow exponentially. Manual QA becomes a bottleneck. And somewhere between the PR and production, confidence starts to erode.
That's the problem we built O2 to solve. And today, we're making it even easier to adopt -
O2 is now available as a GitHub Action on the GitHub Marketplace.
If you have been paying attention to Anthropic's tooling ecosystem over the last 12 months, Claude's web testing capabilities are genuinely exciting. The Computer Use API, the Claude in Chrome extension, and Claude Code's browser integration represent a real shift in what an AI model can do inside a browser - and the instinct to build a testing layer on top of it is completely rational.
Write your test cases in plain English. Let Claude drive the browser, find the bugs, and report back - no selectors, no assertions, no framework to maintain.
Add up every hour your engineers spent last sprint writing test selectors, debugging flaky CI runs, and patching broken scripts after a routine UI refactor. What does that number look like ?
Modern Software development is no longer just about writing code. It is about shipping software/product features faster than others without any bugs. With the Incorporation of agile methodologies, CI/CD pipelines, and microservices architectures, the SDLC cycle has drastically reduced, thereby enabling faster releases.
You write code in VS Code. You debug in VS Code. You review PRs (Pull Requests) in VS Code. So why should you leave VS Code every time you need to run a test?
“The companies that win in modern software are not the ones that write the most code — they are the ones that ship reliable software the fastest.”
Above is a common perspective shared by many Silicon Valley CTOs.
Software development has evolved at an extraordinary pace over the past decade. Applications have become more complex, architectures more distributed, and codebases more interconnected than ever.
Yet, one timeless truth remains: bugs are inevitable. Even the most skilled developers ship code that doesn’t behave as expected. Debugging, therefore, becomes not just a required skill but a continuous, resource-heavy responsibility across all development teams.
The pace of software development in 2025 is unforgiving. Faster releases, more complex apps, and zero tolerance for bugs. It's a tough balancing act for QA teams.
Automation helped. But now, even automation is falling short.