For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Discord
DocsAPI Reference
DocsAPI Reference
  • Get Started
    • Welcome
    • Introduction
    • Quick Start
  • Run
    • Run Videos
    • Run Mode
    • Viewport Size
    • Preparation Test
    • Pull Request Testing
    • Production Monitoring
    • Group Webhooks
    • Run Troubleshooting
  • Auth
    • Test Credentials
    • API Keys
    • Agent Mail Inboxes
    • HTTP Basic Auth
    • Auth Troubleshooting
  • Mobile
    • Overview
    • App Uploads
    • Expo EAS
    • GitHub Actions
  • Integrations
    • Vercel
    • Coolify
    • Custom Infrastructure
    • Slack
    • Discord
    • Email
  • Guides
    • Testing Staging Environment
  • CLI
    • Getting Started
    • Local Development
    • Agentic Usage
  • AI
    • LLMs
LogoLogo
Discord
On this page
  • Adding credentials
  • Custom auth
Auth

Test Credentials

||View as Markdown|
Was this page helpful?
Edit this page
Previous

Run Troubleshooting

Next

API Keys

Built with

Save login credentials in your project so the AI agent can authenticate automatically during test runs. No passwords in test prompts.

Adding credentials

  1. Go to Project → Test Accounts
  2. Click Add Credential
  3. Choose an auth method and fill in the required fields:
    • Label - identifies the credential (e.g., “admin”, “viewer”)
    • Username - email or username
    • Password - stored encrypted
    • Login instructions - required only for custom auth
  4. Click Save

You can add multiple credentials per project for different roles (admin, regular user, read-only viewer, etc.). You can also add credentials for Google and GitHub OAuth flows.

If a saved credential is missing or rejected during a run, see Auth Troubleshooting.

Custom auth

Use Custom when your app has an auth flow TesterArmy does not handle directly, such as:

  • A staging bypass link or test-only route
  • Unsupported SSO
  • An extra access-code step before the normal login form
  • A multi-step flow that needs app-specific instructions

Write clear login instructions for the agent, for example: “Open /staging-login, click the test-only bypass link, enter the access code shown on the page, then continue to the dashboard.”

Custom instructions are encrypted at rest, but they are sent to the AI agent during a run and may appear in run traces and logs. Use the username/password auth method when you need to store reusable login secrets, and never put production credentials in custom instructions.