Use case · Sign-up & onboarding

Sign-up and onboarding testing without writing code

Describe how a new user creates an account and takes their first steps. BuniOD tests it in a real browser every day — including the emails your app sends.

When sign-up breaks, nothing errors — growth just stops

Nobody re-registers after every release, so a broken sign-up form or a missing welcome email can go unnoticed for days.

  • A broken sign-up form shows no error to your team — just fewer new users.
  • Emails and multi-step onboarding are tedious to click through by hand.
  • Testing on production fills it with fake accounts.

Check the first-run experience every day, on staging

Write the first-run steps

Write the steps a new user takes and what they should see at the end. BuniOD matches each step to your pages; a test identity supplies the email and its own inbox.

Check the emails too

Test identities have their own inbox, so a scenario can check the welcome or verification email your app sends.

Keep production clean

Point BuniOD at a staging environment; signed-in areas use HTTP basic auth or a test identity.

See the step that failed

Every run keeps step results, screenshots and console and network logs, with an explanation of any failure.

Example

From written steps to a runnable test

Prompt: the steps you write

// Sign up 1. Click on the "Create account" button 2. Fill in "Email" and "Password" with the email and password from "New Customer" 3. Click on "Sign up" and wait for 10 seconds 4. Open the newest email in the inbox of "New Customer" and click on "Confirm email" // Add an address 5. Click on "Profile", then on the "Addresses" tab 6. Click on "Add address" 7. Fill in "Street" with "12 Test Street" and "City" with "Tashkent" 8. Click on "Save" 9. Confirm you see "12 Test Street, Tashkent" in the address list // Clean up, so the test can run again tomorrow 10. Open "Settings", click on "Delete account" and then on "Delete"

Expected result

The page shows “Your account was deleted”, and a welcome email is in the inbox of “New Customer”.

Steps matched on the page

  1. Click “Create account” in the header
  2. Type the test identity’s email and password and click “Sign up”
  3. Open the confirmation email in the test inbox and click “Confirm email”
  4. Open “Profile” → “Addresses” and click “Add address”
  5. Type the street and city and click “Save”
  6. Open “Settings”, click “Delete account”, then “Delete”

Checks

  • The confirmation email arrives in the test inbox
  • “12 Test Street, Tashkent” is in the address list (step 9)
  • A welcome email is in the test inbox
  • The page shows “Your account was deleted”

Demo data: Acme Shop — Staging. Your scenario follows your own pages.

How it works

Three steps to a daily check

01

Connect your site

Add your staging URL. Public pages need nothing else; signed-in areas use HTTP basic auth or a test identity.

02

Write the steps

Write the test steps and the expected result in plain language, the way you would brief a tester. BuniOD matches each step to your page and adds the checks.

03

Review, then run daily

Confirm the scenario, run it on demand or once a day, and see the failed step with a screenshot and logs.

Pricing

Free plan with 500K tokens a month · Pro $39/mo · Scale $59/mo · unlimited projects and scenarios on every plan.

See pricing

Questions

Won’t this create fake accounts?

Scenarios act like a real user, so they do create accounts. Run them on a staging environment and use test identities.

How does BuniOD check emails?

Each test identity has its own inbox. A scenario that signs up with that address can check the emails your app sends to it.

Our sign-up form has a CAPTCHA. Will it work?

A CAPTCHA can block runs. Use a staging environment with CAPTCHA disabled or your CAPTCHA provider’s test key.

Make sure every new user gets in — every day.