Jobs

Jobs let you group tests together and run them automatically on a schedule or trigger them from your CI/CD pipeline. Use jobs to automate regression testing, smoke tests, and continuous validation of your applications.

What Jobs Do

A job is a collection of tests that run together. When a job executes:

1. All selected tests run in sequence
2. Results are collected and aggregated
3. Alerts are sent if any test fails
4. Reports are generated with full details

Use jobs for:

• Scheduled regression tests — Run nightly or hourly to catch issues early
• Smoke tests — Quick validation after deployments
• CI/CD integration — Trigger tests from your build pipeline
• Monitoring — Regular checks of critical user flows

Creating a Job

Step 1: Basic Information

1. Go to Create → Job
2. Enter a descriptive name (e.g., "Nightly Regression Suite")
3. Add an optional description explaining what the job tests

Step 2: Select Tests

Choose which tests to include in the job. You can select any combination of:

• Browser tests (Playwright)
• API tests
• Database tests
• Custom tests

Step 3: Configure Schedule

Choose when and how the job runs:

Common cron examples:

Step 4: Configure Alerts

Set up notifications for job results:

Parallel Execution

Run multiple jobs or tests simultaneously to reduce total execution time. The parallel execution panel in the header shows real-time status of all running and queued executions across your organization.

How it works:

• Jobs are queued and processed by available workers
• Multiple jobs can run in parallel up to your plan's capacity limit
• View all running executions across your organization in real-time
• Cancel any running job if needed

Capacity limits by plan:

CI/CD Integration

Trigger jobs from your CI/CD pipeline to run tests after every deployment.

Setting Up API Triggers

1. Open the job you want to trigger
2. Go to the CI/CD tab
3. Click Generate API Key

4. Copy the trigger URL and API key

Triggering from CI/CD

Basic trigger:

curl -X POST https://your-instance.com/api/jobs/{jobId}/trigger \
  -H "Authorization: Bearer YOUR_API_KEY"

GitHub Actions example:

- name: Run Supercheck Tests
  run: |
    curl -X POST ${{ secrets.SUPERCHECK_TRIGGER_URL }} \
      -H "Authorization: Bearer ${{ secrets.SUPERCHECK_API_KEY }}"

GitLab CI example:

test:
  script:
    - curl -X POST $SUPERCHECK_TRIGGER_URL -H "Authorization: Bearer $SUPERCHECK_API_KEY"

API Key Security

• Generate unique keys for each CI/CD pipeline
• Store keys as secrets in your CI/CD platform
• Rotate keys periodically for security
• Revoke keys when no longer needed

Job Execution

Running Jobs Manually

1. Go to Jobs list
2. Click the Run button on any job
3. View real-time progress in the execution dialog
4. Results appear when complete

Canceling Jobs

You can cancel a running job at any time:

1. Click the Cancel button on the running job
2. Confirm the cancellation
3. All running tests are stopped immediately
4. Partial results are saved

Viewing Results

After a job completes:

• Summary — Pass/fail status, duration, test count
• Test Results — Individual test outcomes with details
• Reports — Screenshots, traces, and logs for each test
• History — Previous runs for comparison

Job Notifications

Jobs send notifications through your configured alert channels:

Failure Notifications

When a job fails, notifications include:

• Job name and project
• Which tests failed
• Error summary
• Link to full report
• Execution duration

Success Notifications (Optional)

When enabled, success notifications include:

• Job name and project
• All tests passed confirmation
• Execution duration
• Link to report

Timeout Notifications

If a job exceeds the maximum execution time:

• Job is automatically stopped
• Timeout notification is sent
• Partial results are saved

Best Practices

Job Organization

• Group related tests — Put tests for the same feature or flow in one job
• Keep jobs focused — Smaller jobs are easier to debug when they fail
• Use descriptive names — Include what the job tests (e.g., "Checkout Flow - Production")

Scheduling

• Stagger schedules — Don't run all jobs at the same time
• Match frequency to risk — Critical paths need more frequent testing
• Consider time zones — Schedule during low-traffic periods for load-sensitive tests

Alerts

• Always enable failure alerts for production jobs
• Use multiple channels for critical jobs (Slack + email)
• Set up escalation — Different channels for different severity levels

CI/CD Integration

• Run after deployments — Trigger jobs in your deployment pipeline
• Block deployments on failure — Use job results as deployment gates
• Keep API keys secure — Store in CI/CD secrets, never in code