Checks: Test your app automatically

To know your app works, you need to test it by clicking through each flow. Doing that by hand for every flow, every time your app changes, takes a long time. Checks do this for you. A check is an automated test of one flow in your app. When you run it, Biscuit acts as a user, goes through the flow step by step, and tells you whether it works.

​

Where to find checks

1. Open your app.
2. Click the menu.
3. Select Checks. The Checks screen lists every check for the app, shows how many are passing and failing, and when each one last ran.
   

​

Checks Biscuit creates for you

When Biscuit builds your app for the first time, it also creates checks for the app’s most important flows. You can run them straight away to see if your app is working correctly. You will see checks that are passing and failing each time you run them. A failing check means something in that flow isn’t working.

​

Running checks

• To run one check, click Run next to it.
  
• To run every check at once, click Run all. Biscuit’s tester goes through each flow the way a user would. You can open a check to watch the run as it happens.
  

Biscuit also runs checks on its own. Whenever Biscuit’s AI changes your app, it reruns the checks that cover what it changed before it says the work is done.

​

Checks never touch your live app data

Every run gets its own private, throwaway test copy of your app, so you can run checks as often as you like.

• Your latest version: the test copy uses the version you’re working on, including changes you haven’t published yet.
• Test data only: the copy starts with the check’s own Starting data, which you can see in the check’s sidebar. Your real records aren’t in it.
• Nothing reaches the live app: anything the check creates, such as an invited member, an order or a new row, exists only in the test copy.
• No real emails: emails aren’t sent. Biscuit keeps a record of each email inside the test copy, so nobody receives a real invite.

​

Seeing why a check failed

Open a check to see each step the tester took and where it stopped. If something went wrong, the check shows the error, for example a console error that stopped the flow from finishing.

​

Fixing a failed check

You don’t need to work out the problem yourself. Ask Biscuit to fix it.

1. Open your app and click Edit.
2. Tell Biscuit which check failed, for example: “There’s an error in the Manage team access check. Can you take a look and fix it?”
3. Press Enter. Biscuit finds the check, reads its logs, works out what went wrong and fixes it. Like any change to your app, this creates a task. Review the fix and click Approve and Publish to put it live.

Then run the check again to confirm the fix worked. When it passes, it turns green.

​

Creating your own check

Add a check for any flow you want to test regularly.

1. On the Checks screen, describe the flow in plain words, for example “Make sure the invite new member flow works.”
2. Click Create check. The new check appears in the list. Click Run whenever you want to test that flow.

​

FAQ

​

Up next