Vibe Testing done right

You paste a URL. We test your site.

We visit the page, explore it, and generate test scenarios written as readable steps.

Tests as readable steps

Each test describes what a user does and what they expect to see. The format is called Gherkin. It reads like instructions, not code.

Scenario: User logs in

When I set field "Email" to "user@example.com"

And I set field "Password" to "password123"

And I click button "Login"

Then I'm on page "/dashboard"

And I see that the page contains text "Welcome"

The test expresses intent. Playwright runs underneath, but the logic is clear without reading code.

Test generation

We explore your page and suggest Gherkin scenarios based on what we observe. These are starting points, not final tests. You can review them and decide what is useful.

You can generate additional scenarios later, either by re-running exploration or by giving specific instructions. This lets you stay in control of what gets tested and when.

LetsRunIt does not auto-update tests when your UI changes. Instead, it helps you understand what failed, so you can choose whether the code or the test should change.

Sign up for GitHub

Enter an email in the hero field and click "Sign up for GitHub" to create an account.

Start a free Copilot trial

Click "Try Github Copilot free" to open the Copilot Pro trial flow for AI-assisted coding across supported IDEs.

Subscribe to email updates

Enter your email address in the footer form and press "Subscribe" to receive product news and resources.

Failure explanations

When a test fails, we analyze the difference and explain what changed in plain language. You see exactly what broke and whether it's a code issue or the test needs updating.

Update required

A new checkbox labeled "I agree to the terms & conditions" has been added to the registration form. This checkbox is required and must be checked before the form can be submitted.

Update your test to check this box before clicking "Register".

Possible regression

The "Proceed to payment" button was removed from the cart page. With this button gone, there's no clear way for users to continue to payment from the cart.

This appears to be a regression. The button should be restored, or the checkout flow has fundamentally changed.

How tests run

Generated tests run with Cucumber. Install the package, add the step definitions we provide, and run the tests like any other Cucumber suite.

$ npm install @cucumber/cucumber

$ npx letsrunit init

$ npx cucumber-js features/ --format progress --format @letsrunit/reporter

The tests integrate into existing CI without special setup. This is not a new test ecosystem. It's standard Gherkin running on standard tooling.

Standard tooling

Cucumber.js executes the scenarios. No custom runners or proprietary formats.

CI ready

Run in GitHub Actions, Jenkins, or any CI. The tests are files in your repo.

Run tracking

Test results stream to letsrunit. View test history, screenshots, and failure explanations in one place.