For apps where a new user signs up and must enter a code, or click a link, from an email.
Your setup
- A web or mobile app with a sign-up form.
- The app sends a confirmation code or link by email.
- You want sign-up tested end to end, with a fresh account each time.
Say this to Certyn
Test our sign-up on staging. New users get a 6-digit code by email that they must enter.
What Certyn does
- Starts a run with the sign-up as its goal. It asks first.
- The run gets an email address of its own and signs up with it.
- The run waits for the email, reads the code or the link, and finishes the sign-up.
- It reports each step and what went wrong, if anything.
The same inbox works for invites and password resets that a run starts.
What you get
- A run report with each step, screenshots, and the result.
- One Certyn issue per real product bug, for example a code that never arrives or a link that does not work.
- A sign-up test you can save and run on a schedule or after each deploy.
Limits
- The inbox belongs to runs. The chat cannot show you its address, and the chat's Machine cannot read it. To test sign-up, let Certyn start a run.
- Your app must send email to outside addresses from the test environment. If staging sends no email, runs cannot get the code. A run waits up to 3 minutes for one email.
- An existing account that asks for an email code at each sign-in, or signs in with SSO, needs one of these:
- a test account that signs in with a password and no email code (best for scheduled runs), or
- a handoff: you sign in yourself on the chat's Machine, then Certyn goes on from there. Runs cannot sign in with that account on their own.