---
title: "How to test a sign-up form that goes over several screens · Proxy Mail QA"
description: "Test a sign-up that asks for more after Next: keep one test account across every screen, fill company and onboarding questions, and check the email at the end."
url: https://proxymail.qa/solve/multi-step-sign-up-testing
---

1. [Home](https://proxymail.qa/)
2. [What we solve](https://proxymail.qa/solve)

# How to test a sign-up form that goes over several screens

Many sign-ups ask for an email and a password, then for company details, a team size or onboarding questions on the screens after Next. Here's how to keep one test account across all of them, with an agent, in a test, or by hand.

Updated 13 November 2026

## Why sign-ups over several screens are awkward to test

- **The account has to carry over.** Screen 2 belongs to the account made on screen 1\. A new address there, or a name that doesn’t match, gives you an account no real person would have.
- **The later screens ask what only your app asks.** Company size, a role, “How did you hear about us?”, a plan. Typing the same answers on every run is slow, and each tester, test and agent makes up different ones.
- **Some screens come after the account exists.** Onboarding questions often appear once the account is made, after the verification email, so the test has to cover both the email and the screens around it.
- **The screens change.** Product teams move a question from one screen to another. A test that lists each screen’s fields goes stale.

## With your coding agent

`form_values` answers one screen at a time. Ask the agent to make the account on the first screen, then send each later screen’s fields with the same `address`, and that screen’s `site` and `page`:

1. “Sign up on staging.acme.dev with a new Proxy Mail QA account, and go through every screen of the sign-up.”
2. On each screen, the agent sends what the page says about its fields to `form_values`, with the page’s host and path (`site` and `page`), and types in what comes back. A password, date of birth or country a later screen asks for is made then, if the account has none yet.
3. Your app’s own fields come back with `kind: "custom"` when the project has a custom field for them, and with `kind: "guess"` when it doesn’t. The agent tells you which were guessed.
4. It presses Next itself, and at the end waits for the verification code or link.

When a screen asks something nothing fills, ask the agent to save a custom field for it with `save_custom_field`, and every later run fills it the same way. The `sign-up-form-setup` [skill](https://proxymail.qa/skills) goes through the whole form and proposes one for each field that would be guessed or left empty.

## In a Playwright test

With the [npm package](https://proxymail.qa/docs/node), call `formValues` on each screen with the account from the first:

TypeScript

```ts
const first = await qa.formValues({ fields: await readFields(form), site: 'staging.acme.dev', page: '/signup' });
await fill(form, first.values);
await form.getByRole('button', { name: 'Continue' }).click();

await page.waitForURL('**/signup/team');
const team = await qa.formValues({ fields: await readFields(form), address: first.address, site: 'staging.acme.dev', page: '/signup/team' });
await fill(form, team.values);

```

`readFields` describes each field as the page shows it, and `fill` types or picks each value: the [Node.js client](https://proxymail.qa/docs/node#custom-fields-and-screens-after-the-first) has both. The same account gets the same answers on every run, so a failure on screen 2 is about your app, not the data.

## By hand, with Proxy Mail QA for Chrome

From version 0.9.0, start the sign-up from the button in the email field as usual. On each later screen:

- **Fill this step**, a button in the screen’s first empty field, fills it with the same test account, its custom fields and guesses. The card says what went in, such as “Filled step 2 of 3”.
- **Alt+Shift+F** does the same, and **Fill this page** in the popup works there too, for a sign-up started from the page or from the popup.
- **Teach** beside a guessed or empty field saves what goes in it, for everyone on the project.

For a site whose sign-up always goes over several screens, choose **Keep this screen** when Proxy Mail QA for Chrome asks, after you press Next or Continue, whether the new screen is part of the sign-up. The button words are read in nine languages, and it never asks after **Create account** or on a payment screen. Where only leads change sites, Keep this screen asks your project’s leads first. Or switch on **Project settings → Sites → Sign-up goes over several screens**. Each new screen that appears after you press Next is then filled by itself, and the card opens so you can check it before you go on. It never presses Next or submits, never fills a form that appeared without a button press, and stops after 10 screens or 15 minutes without a fill.

## What to check

- Every screen of the sign-up belongs to the same account: the name on the last screen matches the first.
- A required question on a later screen can’t be skipped, and the app says so clearly.
- Back keeps what was typed, and Next after Back doesn’t make a second account.
- The verification email arrives once, whichever screen sends it: `count_emails` or `countEmails` catches a second one.
- Answers from the later screens are kept: they show on the account in the app, or in the welcome email that uses them.

[Custom fields](https://proxymail.qa/docs/custom-fields) explains how fields are recognised, what’s guessed and what’s never filled.

## Try it on your next sign-up test

Free plan, no credit card. Create an address and watch the code or link arrive.

[Create a free account](https://app.proxymail.qa/?mode=signup&from=site-solve-multi-step-sign-up-testing)

## Questions

### Does Proxy Mail QA press Next for me?

No. It fills the fields on each screen and leaves pressing Next, and submitting, to you, your agent or your test, so you choose what's tested on each screen.

### Do I have to tell it how many screens my sign-up has?

No. Custom fields and guesses find their field wherever it appears, and a custom field can be kept to one page. Proxy Mail QA for Chrome notices a new screen after you press a button, and reads a step indicator such as "Step 2 of 3" when the page has one. After you press Next or Continue, Proxy Mail QA for Chrome asks whether the new screen is part of the sign-up, and Keep this screen adds it to the sign-up screens of that site in **Project settings → Sites → Sign-up screens**.

### What if a screen asks something only my app asks?

Teach it once as a custom field: from the page, in Project settings, or by asking your agent. Every fill on the project then puts the same answer in it, for the same account every time.

### Does it fill onboarding questions after the account is made?

Yes, for 15 minutes after the sign-up: those screens count as part of it, including a screen that only asks you to accept the terms, and the page a confirmation link opens when you open it with Open on the email's card. The first screen with nothing left to do, such as the app itself, ends it.

### What about the save-password question in the extension?

On a site set to fill each screen by itself, it waits until the sign-up is finished, then uses the password the form held last. On other sites it asks as before, when the form with the email is sent.

## Related guides

- [Test sign-up and email verification](https://proxymail.qa/solve/email-verification-testing): A fresh, private address for every sign-up test, with the verification link or code ready the moment it lands.
- [Test OTP and one-time login codes](https://proxymail.qa/solve/otp-code-testing): Codes pulled out of the email with a Copy button and a countdown when the email says how long they last.
- [Test magic links and passwordless sign-in](https://proxymail.qa/solve/magic-link-testing): Single-use links that are never opened or prefetched on our side, so they still work when you click them.
- [Test password reset emails](https://proxymail.qa/solve/password-reset-testing): Request, receive and use reset links, and keep the new password saved next to the test account.
- [Stop sharing one Gmail inbox for QA](https://proxymail.qa/solve/shared-test-inbox): Private, disposable addresses for every tester instead of one shared mailbox and a pile of plus-addresses.
- [Stop using Gmail for test codes](https://proxymail.qa/solve/gmail-test-inbox): Why reading codes from Gmail over its API or IMAP keeps breaking your tests, and how one address per test removes the inbox from the problem.
- [Email limits in auth providers while you test](https://proxymail.qa/solve/auth-email-limits): Supabase's 2 an hour, Firebase's 5 email links a day, Auth0's 10 a minute and Clerk's 100 a month, and how to send your own.
- [Let test addresses through a disposable-email block](https://proxymail.qa/solve/disposable-email-blocks): Keep the block for real users and let your test domains through in development and staging, with one setting you can't ship by mistake.
- [CAPTCHA, Google and Apple sign-in in tests](https://proxymail.qa/solve/captcha-and-social-sign-in-tests): Published test keys for reCAPTCHA, hCaptcha and Turnstile, and what to test instead of automating Google and Apple sign-in.
- [Take QA notes by voice with Wispr Flow](https://proxymail.qa/solve/voice-notes-wispr-flow): Dictate what each test account is for, its state and what you found, straight into its notes, in seconds.
- [Test phone-first sign-up without real SMS](https://proxymail.qa/solve/phone-first-sign-up-testing): Test numbers with fixed codes, a test-mode code kept out of release builds, and why virtual numbers usually fail.
- [Test sign-up for people in China](https://proxymail.qa/solve/china-sign-up-testing): Real-name rules, a 姓名 field and province menus, a safe test code, and 身份证 numbers that can't be anyone's.
- [Test sign-up for people in Japan](https://proxymail.qa/solve/japan-sign-up-testing): Furigana fields, 全角 and 半角, postcode lookups and LINE sign-in, with test accounts that have Japanese names.
- [Made-up test accounts, not masked production data](https://proxymail.qa/solve/synthetic-test-data): A masked copy of production still holds real people. Test sign-up with made-up accounts that no one owns instead.
- [Test sign-up for people in India](https://proxymail.qa/solve/india-sign-up-testing): Test accounts with one name, PIN codes that agree with the city, phone-first sign-up, Hindi labels, ID fields and card mandates.
- [Test sign-up for people in Pakistan](https://proxymail.qa/solve/pakistan-sign-up-testing): Test accounts with Pakistani names in both scripts, CNIC fields that never hold a real number, and phone-first sign-up.
- [Fill phone and ID fields safely](https://proxymail.qa/solve/phone-id-and-tax-number-fields): Numbers set aside for fiction, your app's own test numbers, ID values that never match a real person, and KYC sandbox values, filled the same way by agents and tests.
- [Verification link points to localhost:3000](https://proxymail.qa/solve/localhost-links): Why emails from staging link to localhost, how to fix it in Supabase, Firebase and other stacks, and how we flag it.
- [Common Supabase sign-up and login problems](https://proxymail.qa/solve/supabase-auth-problems): Emails that never arrive, links that expire or sign nobody in, and sign-ups that fail, with the fix for each.
- [Common Firebase sign-up and login problems](https://proxymail.qa/solve/firebase-auth-problems): Missing verification and reset emails, verified users who still look unverified, failing links and sign-up limits, with the fix for each.
- [Sign-up and login problems in vibe-coded apps](https://proxymail.qa/solve/vibe-coded-login-problems): The login bugs AI-built apps usually ship with: emails only you receive, links to the preview, missing pages, and what to ask the builder.
- [Check that one user can't see another's data](https://proxymail.qa/solve/vibe-coded-app-data-leaks): A curl with the anon key for tables anyone can read, and two signed-up accounts for policies that let every user read every row.
- [Triage sign-up and login bug reports with an agent](https://proxymail.qa/solve/bug-report-triage): An agent signs up with a new test address, watches the inbox, and answers replicated, not replicated or inconclusive, with the evidence.
- [A self-improvement loop for agents that build sign-up](https://proxymail.qa/solve/agent-self-improvement-loop): The agent builds, signs up with a test address, reads what the email did, fixes its own work and runs again. Proxy Mail QA is the tool it checks with.
- [Test sign-up emails in Playwright](https://proxymail.qa/solve/playwright-email-tests): A complete Playwright test for sign-up codes and links, from a fresh inbox to the report on the pull request.
- [Test sign-up emails in Cypress](https://proxymail.qa/solve/cypress-email-tests): A complete Cypress test for sign-up links and codes, with the email waits running as Cypress tasks.
- [Test sign-up emails with pytest](https://proxymail.qa/solve/pytest-email-tests): A complete pytest test for sign-up codes and links, with Playwright for Python or Selenium and a one-file helper.
- [Test coupon codes and welcome offers](https://proxymail.qa/solve/coupon-code-testing): The coupon with its discount, end date and arrival time, what checkout did with it, and a failure when an expired or reused one is accepted.
- [Test unsubscribe links and one-click unsubscribe](https://proxymail.qa/solve/unsubscribe-testing): The unsubscribe headers and link checked on every marketing email, and a watch that flags any marketing after unsubscribing, with no time limit.
- [Test that a welcome offer can't be claimed twice](https://proxymail.qa/solve/welcome-offer-abuse): Versions of one address that reach the same inbox, and a check that fails when the same person got the offer more than once.
- [AI sign-up page review](https://proxymail.qa/solve/ai-sign-up-page-review): Let an agent check the sign-up through to the email: delivery, the link, how it was sent, and that only one arrives.
- [AI registration page review](https://proxymail.qa/solve/ai-registration-page-review): An agent tries every field with values made for it, then finishes the registration through the email.
- [Review a sign-up page by hand](https://proxymail.qa/solve/how-to-review-my-sign-up-page): A checklist for your browser and phone, in the order that finds the most problems.
- [Review a simple sign-up form](https://proxymail.qa/solve/review-a-simple-sign-up-form): 12 checks for a form with an email, a password and perhaps a name.
- [Review a multi-page sign-up form](https://proxymail.qa/solve/review-a-multi-page-sign-up-form): One test account across every screen, and the verification email wherever it comes.
- [Review a financial sign-up form](https://proxymail.qa/solve/review-a-financial-website-sign-up-form): The emails, age and country rules and awkward values in a financial sign-up, and what needs other tools.
- [An email address for testing registration](https://proxymail.qa/solve/email-for-checking-my-registration-form): A new, real address for every registration try, with the code or link ready to use.
- [An email address for testing sign-in](https://proxymail.qa/solve/email-for-checking-my-sign-in-form): Test accounts with saved passwords and an inbox for codes, magic links and resets.
- [How long should a password be?](https://proxymail.qa/solve/how-long-should-my-registration-form-password-be): NIST's numbers for password length and rules, and test passwords to check yours.
- [No error for a password that breaks the rules](https://proxymail.qa/solve/why-is-my-registration-form-not-showing-password-errors): The eight usual causes of a silent password field, and how to tell which one it is.
- [Help me check my website](https://proxymail.qa/solve/help-me-check-my-website): A whole-site check in an afternoon, in the order that finds the costliest problems first.
- [Tools to build and check a website](https://proxymail.qa/solve/tools-to-help-build-and-check-my-website): A toolkit by area, most of it free and none of it ours, except for account emails.
- [What tools do I need for a website?](https://proxymail.qa/solve/what-tools-do-i-need-when-building-a-website): The full list, then which parts a simple site can skip.

[Built your app with an AI tool? Pick yours](https://proxymail.qa/built-with)
