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:
- “Sign up on staging.acme.dev with a new Proxy Mail QA account, and go through every screen of the sign-up.”
- On each screen, the agent sends what the page says about its fields to
form_values, with the page’s host and path (siteandpage), 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. - Your app’s own fields come back with
kind: "custom"when the project has a custom field for them, and withkind: "guess"when it doesn’t. The agent tells you which were guessed. - 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 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, call formValues on each screen with the account from the first:
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 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_emailsorcountEmailscatches 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 explains how fields are recognised, what’s guessed and what’s never filled.