Test an app in FileMaker

Browser preview verifies the development build and live bridge. After Deploy to FileMaker, test the app inside its FileMaker Web Viewer because that environment supplies a different JavaScript context, window lifecycle, and user session.

Open the app in FileMaker

Navigate to the layout created for the app and confirm the expected app name loads from persistent data. Test with a FileMaker account that represents the people who will use the app, not only a Full Access development account.

Verify the main workflow

Check at least:

• Initial rendering and loading states

• Record reads, finds, creates, edits, and deletes used by the app

• Calls to FileMaker scripts, including parameters, results, and error display

• Navigation between app routes and FileMaker layouts or windows

• Portals, value lists, container fields, and file interactions used by the workflow

• Empty results, validation failures, and permission-denied states

• Closing and reopening the FileMaker window

Confirm that a write reaches the intended file, layout, and record. Use disposable test data when a workflow creates or deletes records.

Compare with browser preview

Browser preview reaches FileMaker through the development bridge. Inside FileMaker, the Web Viewer receives FileMaker's native JavaScript interface and runs with the current FileMaker session. A feature that passes in one environment can fail in the other because of timing, permissions, navigation, or Web Viewer restrictions.

Collect the browser console and the FileMaker-side error when behavior differs. See Build and runtime problems.

Test supported platforms

Test every FileMaker client and operating system your users rely on. Web rendering, focus, scrolling, keyboard behavior, native dialogs, and container interactions can vary by platform even when the application code is identical.

Record the FileMaker version, operating system, account privilege set, and failing workflow with each result.