Checks keep it working

08·Hands-on·9 min

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 a plan with checks, 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. The Checks card at the top of Features also covers the basics without anyone writing them: the app builds, every page loads, and each DontCode service it uses still responds.

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 can stop a build only once it has passed. A new check that fails is rewritten once from what the page actually showed; if it still fails, it waits under Needs your OK and stops no build. There, Rewrite tries it again on your live app and Stop checking retires it. A check that passed before and fails now shows why on its row under Built. If your app still does what it says, Rewrite finds another way to check the same thing on your live app; if that fails too, it moves to Needs your OK and stops no build until it passes again. A check for a feature Insight stopped building waits there too, 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, in the Checks card's More menu, writes a fresh set, at most once a day and again only after your app changes; each new check has to pass before it can stop a build.

See it as each kind of user

Open as, on the Checks card 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 on the Checks card rather than as checks you look after.

Check your understanding

  1. 1.A check reads "a visitor cannot open the staff page". Who does it run as?

  2. 2.On a plan with checks, a build fails one of its checks and the fix does not work. What do your visitors see?

  3. 3.A check describes a feature you removed on purpose. Who can stop it?

Your task

Insight Project

Send 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. If features are built but the project has no checks yet, Write checks on the Checks card works too. The check passes once a check is written for your project.