Flow checks
A sign-up test that waits for the code and enters it proves the happy path. The bugs people meet are elsewhere: a code that works twice, an old reset link that still sets a password, a magic link a mail scanner uses up, a second account that can read the first one’s data. Proxy Mail QA lists the checks for each flow, with the steps to run them and what the app should do.
Where to get them
Section titled “Where to get them”- An agent:
get_flow_checkson the MCP server, withflowset tosign_up,password_resetormagic_link. The agent runs each check with its browser or app tools and reports passed, failed or skipped. - A test:
qa.flowChecks('sign_up')in the npm package,flow_checks("sign_up")in the Python helper, orGET /v1/flow-checks?flow=sign_upon the REST API.
Each check comes with id (a stable name, such as code_works_once), checks (what it checks), steps, expect (what the app should do) and why (what goes wrong for people when it doesn’t). A check that can’t always run has needs: what it needs, and when to skip it and say so.
The Proxy Mail QA parts of the steps are the usual ones: create a new address, note the time just before you submit, wait for the code or link with since set to that time, and count the emails or expect none.
Sign-up
Section titled “Sign-up”| Check | What should happen |
|---|---|
| One confirmation email arrives | Exactly one email, with a code or link, within a minute |
| A wrong code is refused | Each wrong code is refused with a message, and after a few tries the app stops taking codes or asks for a new one |
| The code works only once | Entering the same code again after confirming is refused |
| An expired code is refused | Once the time the email states has passed, the code is refused with a way to get a new one |
| After a resend, the newest code works | The newest code works and the first one is refused. If the app accepts both, note it |
| An unconfirmed account can’t use the app | The app asks for the email to be confirmed first and offers to send it again |
| Confirming signs the person in | The person lands signed in and stays signed in after a reload, or reaches sign-in with a message saying the email is confirmed. Not a blank page, an error or a login loop |
| Signing up again with the same address makes no second account | The first password still works and the second doesn’t. The app says the address is taken, or shows the usual message and emails the owner |
| A second person can’t see the first one’s data | Signed in as a second account, opening the first account’s private item gives “not found” or “not allowed”, and it appears nowhere in lists or search |
Password reset
Section titled “Password reset”| Check | What should happen |
|---|---|
| There is a way to reset a password | The sign-in page offers a reset, and one reset email arrives within a minute |
| A reset for an unknown address gives nothing away | The page shows the same message as for a real account, and no reset link arrives |
| The new password works and the old one doesn’t | After the reset, the old password is refused and the new one works |
| The reset link works only once | Opening the link again after setting a password is refused, with an offer to send a new one |
| Only the newest reset link works | After asking twice, the first link is refused and the newest one works |
| An expired reset link is refused | Once the time the email states has passed, the link is refused with a way to ask for a new one |
| The reset link works in another browser | The reset works there, or the page says clearly to open the link in the browser it was asked from |
Magic-link sign-in
Section titled “Magic-link sign-in”| Check | What should happen |
|---|---|
| The link signs the person in | Signed in, and still signed in after a reload |
| The link fails on its second use | Opened again in another browser, it signs no one in and says it has been used |
| A mail scanner opening the link first doesn’t use it up | After a plain request to the link, as a scanner makes, the browser still signs in: the link opens a page with a button, or the email also has a code |
| Only the newest link works | After asking twice, the first link is refused and the newest one signs in |
| An expired link is refused | Once the time the email states has passed, the link is refused with a way to ask for a new one |
| The link works in another browser | Signed in there, or a clear message to open the link in the browser it was asked from |
Proxy Mail QA never opens the links in your emails, so its own checks can’t use one up. The mail-scanner check copies what a work email scanner does; When a mail scanner opens the link first explains why it matters and how apps get past it.
Running them
Section titled “Running them”- Use a new address for each check, so no earlier email can match and one check’s account can’t affect the next.
- Note the time before each submit and pass it as
since, so a wait after a resend or a second request finds the newest email, not the first. - Skip what can’t run, and say why. An expiry of an hour is too long for most test runs: skip the expiry check and report it as skipped. Never change the app’s settings, such as shortening the expiry or turning off email confirmation, to make a check pass.
- Through the app only. The two-user check opens pages and repeats requests the app itself makes, signed in as the second account. It never reads the app’s database.
- Record them in a run. In a run, an agent adds each check to the report with
add_run_note, marked failed when it failed, so the report for the pull request lists every check.
Precautions
Section titled “Precautions”- Test your own app, on development or staging. Each check signs up new accounts.
- The two-user check is a quick check of the pages you try, not a security audit. Passing it doesn’t mean every page is protected.
- Wrong-code checks can lock a test account after too many tries; that’s the check working.