Skip to main content
Test the action your users came to complete. A page that looks correct can still have a form that does not save or a permission rule that does not protect its records.

​
Run the main journey

  1. Open the app and complete its main action with a synthetic record.
  2. Confirm the expected success message and resulting record.
  3. Refresh the page and confirm that the record remains.
  4. Leave and reopen the app, then repeat the check.
  5. Edit and delete a disposable test record if the workflow supports it.
Tell Fabricate exactly which step failed and what you expected. Avoid including passwords or real customer information in a bug report.

​
Test accounts and permissions

Create two test accounts if your app has sign-in. Add a record as user A, then sign in as user B in a separate browser session. User B should see only the records the product rules allow. Hiding a button is not an access check. For apps containing private information, review server routes and test whether a user can read or change another user’s record by changing its identifier. See Roles and record access.

​
Test failure states

Try a blank required field, invalid input, a repeated submission, and a failed network request. The app should explain the problem without losing the user’s work or creating duplicate records. Check loading and empty states as well as the happy path.

​
Check different screens

Try the main journey on a narrow mobile screen and a desktop. Confirm forms, navigation, and dialogs remain usable. Use the keyboard to reach controls and submit forms; labels should explain what each field needs.

​
Check the published version separately

Preview and published apps have separate databases. Preview test records do not prove the live database is working. Environment secrets apply when publishing and are not available in preview, so test secret-dependent integrations on a published app with the provider’s test credentials. Publishing includes checks for a running, visible app. Those checks do not replace your workflow, permission, payment, or data-retention testing. Continue with the launch checklist.