Testing should be boring.
Shipping should be fun.
We're the team behind TestForge. We believe CI is load-bearing infrastructure, and that engineers deserve tools that respect their time.
To make end-to-end testing something teams actually want to do.
Every engineering team we've worked with has the same CI story: it started clean, grew organically, and now everyone avoids touching it. Runs take forever. Flakes get ignored. Coverage drifts.
TestForge is what we wished existed when we were shipping features under a CI pipeline we didn't trust. It writes tests as your codebase changes, runs them in real browsers on clean machines, catches flakes before humans see them, and proposes fixes for failures — so the CI status check stays green and meaningful.
We're building for the engineer who has a PR to merge by end of day and doesn't want to think about test infrastructure once.
Four principles we actually hold each other to.
Boring infrastructure, sharp product
CI is load-bearing. We obsess over reliability and backwards compatibility — the interesting part is what the product does on top.
Default to shipping
We prototype in prod-shaped environments and dogfood daily. Our own test suite runs on TestForge. Every merge deploys.
Write it down
Decisions live in RFCs, not Slack threads. If it’s not written, it didn’t happen — and new hires can’t read your memory.
Respect the engineer’s time
Every feature earns its keep in seconds saved per day. We’re allergic to noise, gatekeeping toolchains, and meetings that should have been PRs.
The people running the show.
Priya Raman
Previously ran CI infra at a growth-stage infra company. Has opinions about flake detection.
Marco Oduya
Ten years on distributed systems and browser automation. Owns the runners.
Dana Willems
Built the ergonomic testing workflows you’ll recognize from two previous DevTools companies.
Lee Yamashita
Leads our AI test-gen team. Was doing LLM-for-code when it was still uncool.