08·Hands-on·9 min
Checks keep it working
A new feature should never quietly break an old one. Checks are how DontCode makes sure of that.
What a check is
A short sentence about one thing your app does, written by Insight as each feature is built: "a customer can book a free time slot", "a visitor cannot open the staff page". You find them under each built feature on the Features page. Every check names who it runs as: one of your app's user roles, or a visitor who is not signed in. That is how a check can say what someone must not be able to do, not only what they can.
When checks run
On Pro, every build is checked before it goes live, in a test copy of your app filled with sample data. If a check fails, Insight tries to fix it. If it still fails, the change stops before Live, your app stays exactly as it was, and History shows which check failed on the Checked step. Above the list, Always checked covers the basics without anyone writing them: the app builds, every page loads, and each DontCode service it uses still answers.
On other plans checks are still written as features are built, but builds go live without them. Nothing is lost, and upgrading turns them on from the next build.
You decide what stops being checked
Insight cannot remove or change a check; only a person can. A check that fails the very first time it runs, or belongs to a feature Insight stopped building, waits under Needs your OK and stays checked until you press Keep or Stop checking. Stopping asks why, and your reason stays on the retired list. If the checks no longer describe your app after big changes, Rewrite checks writes a fresh set, once a day; each new check is confirmed on the next build before it can stop one.
See it as each kind of user
Open as, in the Features header and above the app on Home, opens your app in that same test copy, signed in as any of your roles or as a signed-out visitor. Click around freely: nothing there reaches real customers or real data, and what you see is exactly what the checks see.
Where DontCode fits
Checks cover what your app's own pages do. Sign-in, payments and email are DontCode services, so they appear as connected under Always checked rather than as checks you look after.
Go deeper
Check your understanding
1.A check reads "a visitor cannot open the staff page". Who does it run as?
2.On Pro, a build fails one of its checks and the fix does not work. What do your visitors see?
3.A check describes a feature you removed on purpose. Who can stop it?
Your task
Insight ProjectSend a build (select a planned feature on Features, or ask Insight for a small change). When it finishes, open Features: the feature lists its new checks and who each one runs as. A built feature with No checks yet has Write checks, which works too. The check passes once a check is written for your project.