For teams who want to know that production works, without test orders, users or messages in real data.
Your setup
- Your live app, for example
https://app.acme.com, as a Certyn environment. - A test account on production. Best: one that can only view.
- You want a check every morning, or every few hours.
Say this to Certyn
Check production every morning at 7:00 Berlin time. Look only: do not create, change or delete anything.
What Certyn does
- Uses your production environment, or creates it. You approve.
- Opens the sign-in form for the production test account. It saves
LOGIN_USERNAMEandLOGIN_PASSWORDon that environment only. - Adds a rule to the wiki's testing rules, with the production URL, for example: On https://app.acme.com: look only. Do not submit forms that create, change or delete data. Do not pay, sign up, or send emails or invites. Every run reads these rules when it starts.
- Creates the check (
app.process.create). Either:- an agent process whose goal lists the pages to open and repeats the read-only rule, or
- a Certyn suite of test cases tagged, for example,
prod-smoke, where each step only opens, searches and reads.
- Sets the schedule on the production environment (
app.process.trigger.set): cron0 7 * * *, time zoneEurope/Berlin. You approve. - Offers one run now (
app.process.run), so you can watch what it does.
What you get
- One run per schedule, with a run report.
- A Certyn issue with evidence for each real problem, such as a page that does not load or a broken search.
- No test data in production, as long as the rule holds (see Limits).
Limits
- Read-only is an instruction, not a lock. Runs follow the goal and the wiki rules, but nothing blocks a click. For a hard guarantee, use a production account that can only view.
- By default, runs treat production like any other environment. An exploratory run even checks saves and deletes first. Marking the environment as production only marks releases as shipped. Always state the rule in the goal or the test cases.
- A suite has no goal. Each test case must only read; the wiki rule applies too.
- A scheduled run of an agent process has 60 minutes. Keep the check short.
- Checks run only at the scheduled times. Between them, Certyn does not watch the site.
- A production account with 2FA needs its setup key. See App with 2FA from an Authenticator App.