A QA teammate that playtests every pull request

by

I kept shipping small changes that quietly broke signup or checkout, the flows I never think to click again. Writing and babysitting end-to-end tests for them was its own job, so they never got written.

So I built VeriWasp. You describe a flow in plain English once, and it becomes a check on every PR. It installs as a GitHub App, runs a real browser against your preview deploy, blocks the merge if the flow breaks, and comments exactly where it fell over. No YAML, no Selenium, no secrets to wire up.

It is free to start: . Not trying to hard-sell, mostly want feedback from people who ship a lot.

What flow breaks most often in your app? Happy to help you set the first one up in the replies.

19 views

Add a comment

Replies

Be the first to comment