Test users
What are test users?
Test users are saved credentials that Buildprint's AI agent uses to log in to your app during testing. Each test user has a name, and optionally an email, password, and description to help the agent understand which account to use for different scenarios.
Make passwords random and unique to each account, rather than passwords you use for other services, as these account credentials can be seen by the Buildprint agent.
Managing test users
You can add, edit, and delete test users from your project's Tests > Users page. Any project member, project admin, or workspace admin can manage test users — guests cannot.
Adding a test user
Click Add test user and fill in:
Name (required) — a descriptive name like "Admin user" or "Free tier user"
Email — the login email for this account
Password — the login password (stored securely, masked in the UI)
Description — notes about what this user is for, e.g. "Has all permissions" or "New user with empty workspace"
Editing and deleting
Use the menu on each test user row to edit their details or delete them.
How test users work in conversations
When you start a conversation with Buildprint, the agent loads a snapshot of your test users at that point in time. This means:
Test users available to the agent are fixed at conversation start
If you add, edit, or remove test users while a conversation is in progress, those changes will not be reflected until you start a new conversation (though you can still manually provide it test credentials)
This ensures consistent behavior throughout a testing session
Using test users
Once test users are configured, simply ask Buildprint to test your app. The agent will use the appropriate test user credentials to log in. For example:
"Log in as the admin user and check the dashboard"
"Sign in with the free tier account and verify the upgrade prompt appears"
The agent selects the most appropriate test user based on your request and the user descriptions you've provided.