Credential Manager
Credential Manager stores login credentials for different user types so Pie can test authenticated areas of your application. Store credentials once, and Pie handles the rest: testing across multiple user roles without manual login intervention.
Understanding Credential Manager
What Is Credential Manager?
Credential Manager is a secure storage system for test account login details. Store credentials for different user types (admins, standard users, premium members) so Pie can test how your application behaves for each role.
Why Use Multiple Credentials?
Most applications have different user types with varying permissions. Testing with multiple credentials ensures:
- Role-Based Access Validation: Verify admins see management panels while standard users don’t
- Permission Testing: Confirm restricted features are properly locked for unauthorized users
- User Experience Coverage: Test how different account types experience your application
- Subscription Tier Testing: Validate feature availability across free, premium, and enterprise accounts
Common Use Cases
SaaS Platforms
For B2B software with role-based access, credentials enable testing across Admin, Manager, and Standard User roles to verify each sees appropriate dashboards and controls.
E-commerce Applications
Test customer accounts with different loyalty tiers, saved payment methods, or order histories to validate personalized experiences and checkout flows.
Healthcare & Financial Services
For applications with strict access controls, credentials allow testing that sensitive data is properly restricted based on user authorization levels.
Adding Credentials
Accessing Credential Manager
- Log in to your Pie dashboard
- Navigate to Settings from the left sidebar
- Select Credentials Manager
Adding a New Credential
- Click the + Add button
- Provide a descriptive Name (nickname) that indicates the user type or role
- Enter the Test Login (email, username, or phone number)
- Enter the Password / OTP / Magic Link
- Click Save
Managing Existing Credentials
To edit or delete a credential, click the three-dot menu (⋮) on the credential card and select the appropriate action.
Using Credentials in Test Cases
Once you’ve added credentials, you can select which credential to use when running custom test cases or editing existing tests. Each test case maintains its own credential assignment. Changing a credential for one test doesn’t affect other tests in your suite.
Running a Custom Test Case
- Open Pie Canvas from your project
- Enter your test case description in the prompt field
- After submitting, Pie displays the Confirm credentials dialog
- Select a credential from the dropdown (Default, or any saved credential)
- Click Continue to run the test with your selected credential
You can switch credentials between prompts. Each prompt submission can use a different credential if needed.
Editing an Existing Test Case
You can change credentials when editing or re-running an existing test case:
- Open the test case you want to edit from your list
- Click the Edit with Pie button to open the test in the assistant view
- In the left panel, locate the Choose Credentials dropdown
- Select the credentials you want to use for this test
- The test case details will update to show Logged in as: displaying your selected credential
When you change a credential for a test case, all subsequent runs of that test will use the new credential until you change it again.
Credential Options
The credential dropdown includes:
- Default: The credential provided during your first Discovery run
- Saved credentials: Any additional credentials you’ve added via Credential Manager
- No credential: Run the test without logging in (for testing public pages)
- + Add new: Quickly add a new credential without leaving the test flow
Best Practices
Naming Conventions
Use clear, descriptive names that indicate the user type, role, or access level. This makes selecting the right credential from the dropdown straightforward.
Examples:
admin-full-accessstandard-userpremium-customerguest-readonly
Account Configuration
Configure test accounts appropriately:
- Disable 2FA: Two-factor authentication blocks AI agents from completing login flows
- Use dedicated test accounts: Never use production accounts or real user credentials
- Maintain active status: Ensure accounts aren’t locked, expired, or pending verification
- Update passwords promptly: When credentials change, update them immediately to prevent test failures
Coverage Strategy
Store credentials for each distinct user role in your application. This enables comprehensive testing of permission boundaries and role-specific features.
For applications where the same flow behaves differently based on user type (like a dashboard that shows different data per role), create separate test cases for each credential to validate all variations.
Troubleshooting
Login Failures
If Pie can’t log in with stored credentials:
- Verify the username and password are correct
- Confirm the account is active and not locked
- Check that 2FA is disabled for the test account
- Ensure the password hasn’t expired or been changed
Wrong Credential Used
If Pie uses an unexpected credential:
- Check that you selected the correct credential from the dropdown before running the test
- Verify the Logged in as indicator shows the expected credential in the test case view
- If the credential was recently deleted, the test may have reverted to the default credential
Access Denied by Application
If your application blocks Pie’s login attempts:
- Check if bot detection or rate limiting is enabled
- Verify Pie’s IP addresses are whitelisted if required
- Contact your Pie account manager for infrastructure configuration
Related Features
Credential Manager works alongside other Pie features for comprehensive testing:
- Scripts: Fetch test data or create user profiles during test execution
- API Keys: Authenticates Pie’s access to your application
- Custom Test Cases: Uses credentials to test specific workflows
Need Help?
Contact your Pie support team with details about your use case and testing requirements.