Documentation
Integrations

Integrations Guide

Connect AegisRunner with Jira, GitHub, Discord, Vercel, Netlify. Visual regression testing, API testing, and CI crawl pages for targeted testing during deployments.

Integrations Guide

AegisRunner integrates with your favorite development tools to streamline your testing workflow. Available on Pro and Business plans.

Plan Requirement: Integrations (Jira, GitHub, Discord, Vercel, Netlify, CI Crawl Pages) are available on Pro ($29/mo) and Business ($59/mo) plans.

Available Integrations

šŸ”µ
Jira
Auto-create issues for failed tests
⚫
GitHub
PR comments & commit statuses
🟣
Discord
Webhook notifications
ā–²
Vercel
Auto-test preview deploys
🟢
Netlify
Auto-test deploy previews
šŸ”
CI Crawl Pages
Targeted crawling in CI/CD

Discord Integration

Receive test results and failure alerts directly in your Discord server.

1
Create a Discord Webhook
  1. Open your Discord server
  2. Go to Server Settings → Integrations → Webhooks
  3. Click New Webhook
  4. Name it "AegisRunner" and select a channel
  5. Copy the Webhook URL
2
Add to AegisRunner
  1. Go to your project → Integrations → Discord
  2. Paste the webhook URL
  3. Click Test to verify
  4. Click Save Discord Settings

Jira Integration

Automatically create Jira issues when tests fail, keeping your bug tracking in sync.

Setup

1
Generate Jira API Token
  1. Go to id.atlassian.com
  2. Click Create API Token
  3. Name it "AegisRunner" and copy the token
2
Configure in AegisRunner
  1. Go to your project → Integrations → Jira
  2. Enable the integration
  3. Enter your Jira domain (e.g., your-team.atlassian.net)
  4. Enter your Jira email and API token
  5. Set the project key and issue type
  6. Optionally enable Auto-create issues
  7. Click Test Connection to verify
  8. Click Save Jira Settings

Configuration Options

SettingDescription
DomainYour Atlassian domain (e.g., myteam.atlassian.net)
EmailYour Jira account email
API TokenGenerated from Atlassian account settings
Project KeyThe Jira project key (e.g., PROJ)
Issue TypeBug, Task, or Story
Auto-createAutomatically create issues when tests fail

GitHub Integration

Post test results as PR comments and set commit status checks on your GitHub repository.

Setup

1
Create a Personal Access Token
  1. Go to github.com/settings/tokens
  2. Click Generate new token (classic)
  3. Select the repo scope
  4. Copy the token
2
Configure in AegisRunner
  1. Go to your project → Integrations → GitHub
  2. Enable the integration
  3. Enter your token, repository owner, and repository name
  4. Toggle Post PR comments and/or Post commit statuses
  5. Click Test Connection to verify
  6. Click Save GitHub Settings

What Gets Posted

  • PR Comments: A summary of test results (passed/failed/skipped) is posted as a comment on pull requests
  • Commit Status: A pass/fail status check appears on commits, blocking merges if tests fail

Vercel Integration

Automatically test your Vercel preview deployments when they go live.

Setup

  1. Go to your project → Integrations → Vercel
  2. Enable the integration
  3. Enter your Vercel access token (generate at vercel.com/account/tokens)
  4. Enter your Team ID (optional) and Vercel Project ID
  5. Enable Auto-test preview deployments
  6. Copy the webhook URL shown and add it to your Vercel project's webhook settings
  7. Click Save Vercel Settings
Tip: When a Vercel preview deployment completes, AegisRunner automatically crawls configured CI pages and runs your test suites against the preview URL.

Netlify Integration

Automatically test your Netlify deploy previews.

Setup

  1. Go to your project → Integrations → Netlify
  2. Enable the integration
  3. Enter your Netlify personal access token (generate at app.netlify.com)
  4. Enter your Site ID
  5. Enable Auto-test deploy previews
  6. Copy the webhook URL shown and add it as an outgoing webhook in Netlify under Deploy notifications
  7. Click Save Netlify Settings

CI Crawl Pages

Configure specific pages to crawl during CI/CD runs instead of crawling your entire site. This speeds up CI pipelines by focusing on the pages that matter most.

How It Works

  1. Go to your project → Integrations → CI Crawl
  2. Enable CI crawl pages
  3. Add page paths (e.g., /login, /dashboard, /pricing)
  4. Optionally enable Auto-generate AI tests for crawled pages
  5. Click Save CI Crawl Settings

Combining Pages

CI crawl pages can come from two sources that are automatically merged:

SourceDescription
Project SettingsPages configured in the CI Crawl tab (always crawled)
CI Trigger RequestAdditional pages passed in the crawlPages field of the trigger API request

Example: CI Trigger with Pages

curl -X POST https://aegisrunner.com/api/v1/ci/trigger \
  -H "Authorization: Bearer aegis_YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "crawlPages": ["/checkout", "/account"],
    "baseUrl": "https://preview-123.vercel.app",
    "generateTests": true
  }'
Base URL: When triggering from CI, you can pass a baseUrl to crawl against a preview deployment URL instead of your production site.


Visual Regression Testing

Visual regression testing is built into AegisRunner's test execution engine. Enable it when running tests to automatically compare screenshots against baselines.

  • Pixel-level diffs using pixelmatch
  • Three-panel view: baseline, current, and diff
  • Baseline management: accept or reject visual changes
  • Diff percentage scoring for each comparison

See Visual Regression Testing for setup and usage details.


API Testing

Test REST and GraphQL API endpoints alongside your UI tests using api-request steps.

  • HTTP methods: GET, POST, PUT, DELETE
  • Assertions: status codes, response bodies (JSON path), response times
  • No browser overhead: API steps run via Node.js fetch directly
  • Combined workflows: Mix UI and API steps in the same suite

See API Testing for setup and usage details.


Related Documentation

Need help?

Can't find what you're looking for? Our support team is here to help.