For anyone who wants to see what Certyn does, or whose app has a sign-in step only a person can pass.
Your setup
- Your app has a captcha, company SSO, or a code sent to a phone.
- You test with Certyn in the chat, on its Machine, and with runs.
- You want to watch, help when Certyn is stuck, and stop a run that goes nowhere.
Say this to Certyn
Open staging on the Machine and sign in. I will do the SSO step myself.
What Certyn does
In the chat, on the Machine:
- Opens the app in the Machine's browser. With no Machine picked, it opens the
machineform first. - At a step only you can do, it stops and shows a Your turn on the Machine card with the exact step.
- You click Take control. The Machine's screen opens. You click and type in it like in your own browser.
- You click Done. Certyn checks the screen and goes on.
The Machine menu in the chat box has Remote desktop (open the screen at any time) and Stop machine.
In runs:
- A started run gets a live run link in the chat. Suite pages show Watch live while a run is active. The Runs icon at the top lists all runs.
- A run's live view is for watching only. You cannot click in it.
- To stop a run, say stop that run. Certyn asks first, then stops it (
app.execution.stop). Or cancel it on the Runs page.
What you get
- You see what Certyn sees, while it works.
- Sign-in steps that need a person, done on the Machine. Your password never goes into the chat.
- A wrong run stopped early. A run uses plan time for as long as it runs.
Limits
- Runs do not wait for a person. A step a run cannot pass is reported as blocked. For runs, use a test account without that step, an authenticator secret (
TOTP_SECRET), or the run's own inbox for sign-up email codes. - A sign-in you do on the chat's Machine stays there. A run starts its own browser and does not get it.
- To run a stopped run again, say retry that run.