# Test your app
Test your application from a customer’s perspective before sharing it.
## What you’ll have at the end
A repeatable check of your app’s main task, API persistence, smaller-screen layout and customer access.
Source: https://docs.rumata.dev/guides/testing
Reviewed: 2026-11-01
## Test your application like a real user
Now that your application is built, it's time to make sure everything works as expected!
While Rumata's AI agent tests your application during development, we recommend trying it yourself to make sure it works the way you envisioned.
1. Open Preview Mode in your factory workspace.
2. Choose an important task your users should be able to complete, such as signing up, submitting a form, or creating a new record.
3. Go through the process just as a real user would, checking that buttons, forms, and navigation work correctly.
4. If your application saves information, refresh the page or reopen the record to make sure your changes were saved.
5. If your application connects to external services, verify that the expected action happened there too.
6. If something doesn't work as expected, describe the issue to Rumata's AI agent and ask it to fix it. Then test the feature again.
> **Example**
> If you've built a customer management app, try adding a new customer, saving their details, and finding them again using the search feature.
> **Check your result**
> You should be able to complete your application's main task from start to finish without unexpected errors.
If everything works as expected, you're ready to continue improving your app or prepare it for deployment.
> **Tip**
> Use test accounts and sample data. Preview can call real services and share the bound database or storage with production; confirm the target before deleting data, running migrations, sending messages or starting paid work.
Learn more: [Build and improve your app](https://docs.rumata.dev/guides/prompting#review-change)
## Check a smaller screen
Make sure customers can use your application on a phone too.
Use the device-size control in the preview toolbar to check different screen sizes. It shows [Full](https://docs.rumata.dev/guides/controls-preview#navigation) when the preview is at full width.
1. Open the preview size control and choose Mobile.
2. Repeat the same main task, including any menus, forms, or dialogs it requires.
3. Check for clipped text, unreachable buttons, or horizontal scrolling, then return to Full.
> **Optional example**
> For a portfolio, check that project images fit and the navigation and contact links remain easy to use.
> **Check your result**
> The whole task remains usable at the smaller width. If it fails, report the screen size and failing control in chat and retest after the fix. Check on a real phone before launch too.
Learn more: [Preview sizes](https://docs.rumata.dev/guides/controls-preview)
Reference capture from the separate Sabai Talk Thai application (September 8, 2026). Open the size selector, then choose [Mobile](https://docs.rumata.dev/guides/controls-preview#navigation) to check the narrow layout.
Reference capture from the separate Sabai Talk Thai application (September 8, 2026). Check that text and controls remain usable at the selected width. Return to [Full](https://docs.rumata.dev/guides/controls-preview#navigation) when you finish.
## Test user access and permissions
Make sure your application protects private information and gives each user access to the right features.
If your application includes user accounts, private pages, or different permission levels, it's important to test that everything works as expected.
1. Test without signing in: Open your application as a visitor. Make sure public pages are accessible and private features require users to sign in.
2. Test different user roles: If your application has roles such as Admin, Team Member, or Customer, sign in with a test account for each role. Check that each user can access only the features and actions intended for them.
3. Check private information: Create two separate test accounts and verify that users cannot view or modify each other's private information unless sharing is intentionally allowed.
4. Test restricted actions: Try accessing a private page directly or performing an action your test account shouldn't be allowed to complete. Confirm that access is denied.
5. Fix and retest: If something doesn't work as expected, describe the issue to Rumata's AI agent, request a fix, and test it again.
> **Example**
> If you've built a customer portal, a customer should be able to view their own orders but not another customer's orders. An administrator, however, may need access to all orders.
> **Check your result**
> Each type of user should be able to access the information and features intended for them, while restricted information and actions remain protected.
> **Good to know**
> Your application's user accounts are separate from your Rumata account. If your application is fully public and doesn't require sign-in, focus on testing the experience for visitors.
> **Important**
> Preview testing helps identify access issues, but it doesn't replace a full security review. Before launching an application that handles sensitive information, verify that permissions are enforced by the backend, not just hidden in the interface.
## Report a problem and retest
Give Rumata a specific problem it can reproduce.
Use the chat beside the preview to report the issue.
1. Send a bug report with the page, exact actions, actual result, and expected result.
2. Wait for the fix to finish.
3. Repeat the failed steps and the complete main task, recording the observed outcome.
Optional wording you can adapt:
```text
On [page], I [actions taken]. I expected [result], but [actual result]. Please identify and fix the cause, then verify these steps and check that [related functionality] still works.
```
> **Check your result**
> Once the main task works, continue to [Publish your app](https://docs.rumata.dev/guides/publishing). If a preview connection or platform error blocks testing, follow the troubleshooting reference.
Learn more: [Troubleshooting](https://docs.rumata.dev/guides/troubleshooting)
## Related guides
- [Preview, network, and console controls](https://docs.rumata.dev/guides/controls-preview)
- [Troubleshoot with a clear next step](https://docs.rumata.dev/guides/troubleshooting)