What to test in a Base44 app
- Sign-up and sign-in emails. Whether your app sends a link or a code, check it arrives quickly, comes from a name your users will recognise, and works.
- Invites. If you invite people to a private app, check the invite arrives, the link opens your app and the invited user lands in the right place.
- Roles and permissions. An admin and a regular user should see different things. You need a separate account per role to check.
- Your app’s own emails. Notifications, confirmations and reminders built into your app deserve the same check.
A test account for every role
- Create a small batch of addresses in Proxy Mail QA, each with a generated name and username, one per role you want to test.
- Invite them from your app, or sign up with each one.
- Open each invite or sign-in email from its row. Links become one button named for what they do; codes get a Copy button.
- Sign in as each role and check what they can see and do.
- Tag each address with its role (admin, member, viewer) and save its password, so anyone on your team can sign in as that user later.
Keep your test accounts tidy
Addresses last 1 to 7 days and are then deleted with their mail, so test users don’t pile up in someone’s inbox. Their names are never reissued, so nobody else can receive email meant for your test accounts. Use a project per app, with your app’s address linked so it’s one click away.