I got tired of writing E2E tests, so I built an AI that runs them for me

QA is unavoidable… but painful

Whether you’re building side projects or working professionally, one thing never goes away:

Quality Assurance.

No matter how great your product is, users won’t trust it if it’s full of bugs.

But here’s the reality:

• In side projects, we barely have time to build features — QA gets skipped.


• In companies, QA is mandatory — but it slows everything down.

The cycle becomes:

Fix → QA → Fix → Re-QA → Repeat forever

At some point I started wondering:

Why is ensuring quality still so expensive?

Why is QA still so manual?

The moment everything clicked

While thinking about this problem, I discovered an open-source project called


Browser Use.

It lets AI control a real browser.

That’s when the idea hit me:

What if we could write tests in plain English and let AI do the QA?

So I built it.

Meet Test Pilot

Instead of writing test code, you simply describe what you want to verify.

For example:

• Verify that a user can log in


• Check that a product can be added to the cart


• Ensure the purchase completion screen appears

That’s it.

The AI performs the steps and verifies the results.

Why natural language?

Because writing tests is expensive.

Test code requires:

• Technical knowledge


• Maintenance


• Constant updates after UI changes

And eventually…

Tests become the thing teams postpone.

Natural language removes that barrier.

You can write tests the same way you write product specs.

This also makes tests accessible to:

• PMs
  


• Designers
  


• Non-engineers
  

Now the whole team can understand what is being tested.

Record once, turn it into QA

We also built a browser extension that records your actions.

Instead of writing tests, you can:

1. Open your app
   


2. Click through a flow once
   


3. Save it as a test
   

No code. No scripting.


Just record and run.

This dramatically lowers the barrier to starting QA.

Run tests in the cloud or locally

Tests can run in:

• Cloud (quick and easy)
  


• Local Runner (Mac)

Local execution is especially useful when:

• You need logged-in sessions
  


• Your app is behind a firewall
  


• You’re testing internal tools
  

This makes the tool usable from side projects to production teams.

Under the hood

Here’s the high-level stack:

Frontend

• Next.js

Backend

• Python / FastAPI

Browser Automation

• Browser Use (Playwright-based)

Cloud Execution

• Celery for async test runs

Nothing magical — just technology chosen to reduce the barrier to QA.

The real goal

This started as a tool I wanted for myself.

But it grew into the largest product I’ve ever built.

There’s still a lot to improve, and it’s far from perfect.

But if you’ve ever felt that QA is heavy, slow, or constantly postponed…

I hope this can help.

Try it

If this sounds interesting, I’d love your feedback.

https://test-pilot.dev