CI/CD Integration

VisualQ integrates with your CI/CD pipeline so visual tests run automatically on every deploy, pull request, or scheduled job.

Integration options

Both methods require an API key for authentication.

All CI methods support an optional environment parameter to target a specific environment (e.g., staging, production). When omitted, the project's default environment is used.

Typical CI workflow

Developer pushes code
       ↓
CI pipeline starts
       ↓
VisualQ runs visual tests
       ↓
Results posted to PR / Slack / webhook
       ↓
Team reviews diffs and approves or fixes

In this section

• API keys — create and manage authentication keys
• REST API — trigger runs and check status programmatically
• GitHub Action — official GitHub Action setup
• Other CI systems — Jenkins, GitLab CI, and more