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.
Available Integrations
Discord Integration
Receive test results and failure alerts directly in your Discord server.
- Open your Discord server
- Go to Server Settings ā Integrations ā Webhooks
- Click New Webhook
- Name it "AegisRunner" and select a channel
- Copy the Webhook URL
- Go to your project ā Integrations ā Discord
- Paste the webhook URL
- Click Test to verify
- Click Save Discord Settings
Jira Integration
Automatically create Jira issues when tests fail, keeping your bug tracking in sync.
Setup
- Go to id.atlassian.com
- Click Create API Token
- Name it "AegisRunner" and copy the token
- Go to your project ā Integrations ā Jira
- Enable the integration
- Enter your Jira domain (e.g.,
your-team.atlassian.net) - Enter your Jira email and API token
- Set the project key and issue type
- Optionally enable Auto-create issues
- Click Test Connection to verify
- Click Save Jira Settings
Configuration Options
| Setting | Description |
|---|---|
| Domain | Your Atlassian domain (e.g., myteam.atlassian.net) |
| Your Jira account email | |
| API Token | Generated from Atlassian account settings |
| Project Key | The Jira project key (e.g., PROJ) |
| Issue Type | Bug, Task, or Story |
| Auto-create | Automatically create issues when tests fail |
GitHub Integration
Post test results as PR comments and set commit status checks on your GitHub repository.
Setup
- Go to github.com/settings/tokens
- Click Generate new token (classic)
- Select the
reposcope - Copy the token
- Go to your project ā Integrations ā GitHub
- Enable the integration
- Enter your token, repository owner, and repository name
- Toggle Post PR comments and/or Post commit statuses
- Click Test Connection to verify
- 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
- Go to your project ā Integrations ā Vercel
- Enable the integration
- Enter your Vercel access token (generate at vercel.com/account/tokens)
- Enter your Team ID (optional) and Vercel Project ID
- Enable Auto-test preview deployments
- Copy the webhook URL shown and add it to your Vercel project's webhook settings
- Click Save Vercel Settings
Netlify Integration
Automatically test your Netlify deploy previews.
Setup
- Go to your project ā Integrations ā Netlify
- Enable the integration
- Enter your Netlify personal access token (generate at app.netlify.com)
- Enter your Site ID
- Enable Auto-test deploy previews
- Copy the webhook URL shown and add it as an outgoing webhook in Netlify under Deploy notifications
- 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
- Go to your project ā Integrations ā CI Crawl
- Enable CI crawl pages
- Add page paths (e.g.,
/login,/dashboard,/pricing) - Optionally enable Auto-generate AI tests for crawled pages
- Click Save CI Crawl Settings
Combining Pages
CI crawl pages can come from two sources that are automatically merged:
| Source | Description |
|---|---|
| Project Settings | Pages configured in the CI Crawl tab (always crawled) |
| CI Trigger Request | Additional 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
}'
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
- CI/CD Integration - Set up CI tokens and trigger test runs
- Slack Integration - Slack webhook notifications
- Scheduling Tests - Automate test runs on a schedule
- Subscription Plans - Plan features and limits