Open Orbit

Review an app before launch

Test an app's main task and saved data, record failed tests, and identify access checks that must precede launch.

Test your app's main task and saved data before you make it public. Test access rules separately before you use private information.

Before you start

Open your app in an environment where you can enter test data and refresh the page. This guide covers test cases, not preview setup or deployment.

The example uses the reading tracker from Build your first app. That guide asks Orbit to create a book list, a detail page, and a status for each book. Your generated app can use different controls.

Use test information instead of real customer data. For this example, the task is to add a book, change its status, and find the saved change after a refresh.

Test the main task

  1. Add a book titled Launch test book with an author of your choice.
  2. Complete the app's save action, if required.
  3. Open the book list.
  4. Confirm that Launch test book appears.
  5. Open the book's detail page.
  6. Change its status to Reading.
  7. Complete the app's save action again, if required.
  8. Refresh the detail page.
  9. Confirm that the title, author, and new status remain.

Use your app's own names and actions if you built a different app. A page that looks correct does not prove that the app saves a change.

Test missing information

  1. List the information your app must require before it saves a record.
  2. Try to save a new record without one required value.
  3. Check that the app explains what you must supply.
  4. Supply that value and try again.
  5. Confirm that the record appears once, with the information you entered.

If you have not defined which values are required, define your data model before you treat this test as complete.

Record access requirements

Write the access rule your app needs. For example, a personal reading tracker means each person sees only their own books.

Before launch, you need evidence that your app enforces that rule for reading and changing records. An app that saves data correctly can still expose private information.

This guide does not configure sign-in or verify access isolation. Do not treat the tests above as proof of either. Do not launch with private information until you test access rules with separate user sessions.

Fix and repeat

For each failed test, record the action, expected result, and actual result. Ask Orbit Agent for one specific correction. For example:

In the reading tracker, the book status returns to its old value after refresh. Make the status change persist. Keep the book title and author unchanged.

Use Edit a mockup for the Orbit Agent controls. If the problem concerns stored information, also check Define a data model.

Repeat the failed test after the correction. Then repeat the main task to check that the correction did not break it.

Keep the test results

Record which environment you tested, each test result, and each unresolved problem. A test before deployment does not prove that the deployed app works.

After deployment, repeat the main task at the live address with test information. Do not launch if the app loses saved changes or you lack evidence for its access rules.