TesterArmyTesterArmy
TesterArmyTesterArmy
WelcomeIntroductionQuick Start
Run ModePull Request TestingProduction MonitoringGroup Webhooks
Test CredentialsAgent Mail InboxesHTTP Basic Auth
OverviewApp UploadsGitHub Actions
VercelCoolifyCoolifySlack
Testing Staging EnvironmentTesting PRs
Getting StartedLocal Development
Run

Pull Request Testing

PR Testing runs AI-powered tests against every preview deployment. It reads the PR context, generates a targeted test plan, executes it in a real browser, and posts results as a GitHub comment.

How it works

  1. A preview deployment completes (Vercel or Coolify).
  2. Our agent reads the PR title, description, and changed files.
  3. It generates a test plan targeting the affected areas.
  4. Tests run against the live preview URL.
  5. Results are posted as a comment on the pull request.

Supported providers

  • Vercel - automatic via GitHub deployment status events. No webhook needed.
  • Coolify - via webhook configured in Coolify notifications.
  • Custom infrastructure - via group webhooks with commitSha. See Testing Staging Environment.

Prerequisites

Run Mode

Previous Page

Production Monitoring

Next Page

On this page

How it worksSupported providersPrerequisitesWhat gets tested?
  • GitHub App installed and connected to the repository.
  • Deployment provider configured - see Vercel or Coolify setup guides.

    • What gets tested?

    The agent builds a test plan tailored to each PR. It considers:

    • PR title and description - understands intent.
    • Changed files - focuses on affected areas.
    • Application context - project memory, test accounts, uploaded files.

    The plan covers functional checks, visual verification, and edge cases relevant to the changes.