Skip to main content
Bugster integrates seamlessly with your CI/CD pipeline to automatically run tests against preview deployments on every pull request. This ensures your application works correctly before merging changes.
Currently supported deployment platforms: Vercel, Railway, and Netlify.

​
Prerequisites

Before setting up CI/CD integration, ensure you have:
  • A Bugster organization and project configured
  • A GitHub repository with your application code
  • Your application deployed on Vercel, Railway, or Netlify
  • Admin access to your GitHub repository and deployment platform project

​
Integration Steps

1

Install GitHub App

Install the Bugster GitHub App in your organization to enable repository access and pull request integration.
  1. Navigate to your Bugster organization settings
  2. Go to Integrations → GitHub
  3. Click Install GitHub App
  4. Select your organization and repositories
  5. Complete the installation process
Verify the GitHub App appears in your organization’s installed apps.
2

Integrate GitHub Repository

Connect your GitHub repository to your Bugster project to enable automated test execution.
  1. In your Bugster project dashboard, go to Settings → Integrations
  2. Click Connect Repository
  3. Select your GitHub repository from the list
  4. Confirm the integration
Ensure the GitHub repository matches the one where you installed the Bugster GitHub App.
3

Configure Platform Integration

Set up your deployment platform integration based on where your application is hosted:
  • Vercel
  • Railway
  • Netlify
Enable Bugster to access your Vercel preview deployments using Protection Bypass:
  1. In Vercel, navigate to your project’s Deployment Protection settings
  2. Navigate to Protection Bypass for Automation
  3. Click Add Secret to generate a bypass token
  4. Copy the generated secret
  5. In Bugster, go to Project Settings → Config YAML
  6. Add the secret to your configuration:
vercel:
  protection_bypass: "your-generated-secret-here"

Detailed Vercel Setup

Complete Vercel integration guide with troubleshooting
4

Test the Integration

Verify everything works by creating a test pull request.
  1. Create a new branch in your repository
  2. Make a small change to your application
  3. Open a pull request
  4. Wait for Bugster to automatically run tests
  5. Check the PR for Bugster results and status updates
You should see Bugster test results appear as a check in your pull request within a few minutes.

​
Advanced Configuration

​
Organization Preferences

Configure how Bugster behaves across your organization and projects:
Control whether Bugster’s destructive agent runs on pull requests:
  1. Go to Organization Settings → General
  2. Find Bugster Destructive option
  3. Toggle to enable/disable destructive testing on PRs
The destructive agent tests edge cases and error scenarios that might break your application.
Choose when Bugster runs tests on your pull requests:Available options:
  • On every commit (default): Runs tests each time you push changes
  • Once per PR: Runs tests only when the PR is first opened
Configure in Organization Settings → General → Run on Every PR Deployment
Select which environments Bugster should test:
  1. Navigate to Organization Settings → General
  2. Find Run on Environments
  3. Choose from:
    • Production only
    • Preview only
    • Both environments

​
Email Notifications

Get notified when tests fail in your deployments:
  1. Go to Organization Settings → General
  2. Enable Send Email Alerts for Failed Tests
  3. Configure recipient preferences

​
Troubleshooting

Possible causes:
  • GitHub App not installed or missing repository permissions
  • Repository not connected to Bugster project
  • Platform integration not configured properly
Solutions:
  • Verify GitHub App installation and permissions
  • Re-connect repository in project settings
  • Check platform-specific configuration:
    • Vercel: Verify protection bypass configuration
    • Railway: Ensure preview deployments are enabled
    • Netlify: Check webhook notifications are configured
Possible causes:
  • Platform authentication blocking access
  • Invalid configuration settings
  • Preview deployment not ready or failed
Solutions:
  • Vercel: Verify protection bypass secret is correct
  • Railway: Check deployment status and environment variables
  • Netlify: Verify webhook URL is configured and deployments are successful
  • Ensure preview URL is accessible and deployment completed
Possible causes:
  • Tests not configured in Bugster project
  • Test generation failed
  • CI/CD pipeline issues
Solutions:
  • Verify tests exist in your Bugster project
  • Check Bugster logs for errors
  • Review GitHub Actions/deployment logs

​
Next Steps

With CI/CD integration complete, you can:
⌘I