Three fields, three jobs
- What worries you most? — your scenarios. What must work, in your own words. Each one is checked on every run and answered in the verdict’s bottom line — working or not. One that could not be reached this run is named as such, never silently skipped.
- Scope — hard limits. Where CheckMyApp must not go and what it must not press. Followed to the letter.
- Notes — context. What is expected, what is intentional, what is fine to do.
Where to write them
- When you add your app— “What worries you most?” and “Scope & notes” on the form.
- In the app’s settings — Dashboard → your app → “What we check”. Changes apply from the next check.
- From your coding agent — tell it the scenarios when it adds the app, or ask it to update them later (
create_app,update_app). See Connect your coding agent. - For a single check — the home pagetakes notes under “Add login & notes”. Scenarios that should be checked every day belong on the app.
What a good scenario looks like
Write it the way you would brief a new colleague: what a user does and what they should see. One scenario per line. Concrete beats broad — “the app works” cannot fail; “a saved invoice shows up in the list” can.
Signed in, I can create a project, see it in the project list, rename it and delete it.
Choosing the Pro plan on /pricing shows $29/month and reaches the payment form.
Every YouTube link on the course pages plays.
Searching for “invoice” returns results, and each result opens its invoice.
The first example creates and deletes a record, so it needs a test account and “May we create test records?” switched on. Without that permission, CheckMyApp checks that the form is there and accepts input, and stops before saving.
Scope and notes, by example
Scope — the limits:
Don’t touch /admin. Never press “Delete account” or “Cancel subscription”.
Notes — the context:
The test account is on the free plan, so upgrade prompts are expected. Empty charts on a brand-new project are intentional.
what is never done, whatever you write
A new account is taken up to the final “Sign up” press and not created. No payment is made, no one is invited or messaged, nothing is published. A scenario that needs one of those is checked up to that point.
Keep passwords out of these fields — they are stored as written. Credentials go in the test login, which is encrypted.