CI/CD Integration
Run Bug0 tests automatically as part of your deployment pipeline to catch bugs before they reach production.
Overview
Bug0 integrates with your CI/CD workflow to:
- Run tests on every pull request
- Validate preview deployments
- Post results to PRs and Slack
- Block merges on test failures
Integration Options
GitHub Actions
Use our GitHub Actions workflow to trigger tests on PR events.
API Endpoint
Call the /api/run-tests endpoint directly from any CI/CD system.
Webhooks from Hosting Providers
Connect Vercel, Netlify, or other hosting providers to trigger tests automatically.
Typical Workflow
1. Developer creates PR
2. Preview deployment created (Vercel/Netlify)
3. Bug0 tests triggered with preview URL
4. Tests execute against preview
5. Results posted to PR as comment
6. Commit status updated (pass/fail)
7. Developer fixes any failures
8. Tests pass → PR ready for merge
What Gets Tested
When tests run via CI/CD:
- Published steps are executed (not draft)
- Published assertions are checked
- Login suites run first
- Cleanup suites run last
- Results are sent to configured channels
Dynamic URLs
For preview deployments, pass the preview URL:
# Example: Test against Vercel preview URL
curl -X POST https://app.bug0.com/api/run-tests \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"projectId": "...",
"url": "https://your-app-git-branch.vercel.app"
}'
The URL overrides the project's base URL for this run.
Test Results
GitHub PR Comments
When GitHub is connected:
🤖 Bug0 QA Agent
✅ All tests passed
- Tests completed in 2m 34s
- 12 tests across 3 suites
[View full report](https://reports.bug0.com/...)
Commit Status
GitHub commit status shows pass/fail:
- ✅
Bug0 QA Agent - All tests passing! - ❌
Bug0 QA Agent - 2 tests failed
Email Notifications
If email is configured, receive a report link after each run.
Slack Notifications
If Slack is connected, receive a summary message.