​

Test Round Triggers

​

Access Paths

​

Trigger Concept

​

What is a Trigger?

• When to trigger (trigger conditions)
• What to do (create test round)
• Which template to use (test round template)

​

Use Cases

• Automatically execute tests after code commits
• Execute regression tests on schedule
• Automatically verify after deployment
• Trigger tests via API calls

​

Creating a Trigger

​

Accessing Creation Page

1. Navigate to trigger management page /test-rounds/triggers
2. Click the ”+ Create Trigger” button
3. Or directly visit /test-rounds/triggers/create

​

Configuration Steps

​

Step 1: Basic Information

​

Step 2: Trigger Settings

​

Complete Creation

1. Confirm all settings are correct
2. Click “Create” to create trigger
3. System will display Webhook URL and Secret Token
4. Important: Please save this information securely

​

Webhook Integration

​

Webhook URL

<host>/webhook/trigger/{trigger_id}

​

Calling Method

curl -X POST \
  <host>/webhook/trigger/{trigger_id} \
  -H "Authorization: Bearer {secret_token}" \
  -H "Content-Type: application/json" \
  -d '{
    "source": "ci-pipeline",
    "ref": "main",
    "commit": "abc123"
  }'

​

Request Parameters

​

Response Format

{
  "success": true,
  "data": {
    "round_id": "xxx-xxx-xxx",
    "status": "pending"
  }
}

​

CI/CD Integration Examples

​

GitHub Actions

- name: Trigger Test Round
  run: |
    curl -X POST \
      ${{ secrets.QAPTLY_WEBHOOK_URL }} \
      -H "Authorization: Bearer ${{ secrets.QAPTLY_TOKEN }}" \
      -H "Content-Type: application/json" \
      -d '{
        "source": "github-actions",
        "ref": "${{ github.ref }}",
        "commit": "${{ github.sha }}"
      }'

​

GitLab CI

trigger_test:
  stage: test
  script:
    - |
      curl -X POST \
        $QAPTLY_WEBHOOK_URL \
        -H "Authorization: Bearer $QAPTLY_TOKEN" \
        -H "Content-Type: application/json" \
        -d "{\"source\": \"gitlab-ci\", \"ref\": \"$CI_COMMIT_REF_NAME\"}"

​

Jenkins

stage('Trigger Test') {
    steps {
        sh '''
            curl -X POST \
              ${QAPTLY_WEBHOOK_URL} \
              -H "Authorization: Bearer ${QAPTLY_TOKEN}" \
              -H "Content-Type: application/json" \
              -d '{"source": "jenkins"}'
        '''
    }
}

​

Managing Triggers

​

Viewing Trigger List

• Trigger name
• Associated template
• Status (enabled/disabled)
• Last trigger time
• Trigger count

​

Editing Triggers

1. Find the target trigger
2. Click the “Edit” button
3. Modify required settings
4. Save changes

​

Disable/Enable Triggers

• Click “Disable” to temporarily disable trigger
• Webhook calls will be ignored when disabled
• Click “Enable” to re-enable

​

Deleting Triggers

1. Click the “Delete” button
2. Confirm delete operation
3. Webhook URL will become invalid after deletion

​

Security Recommendations

​

Protecting Secret Token

• Do not commit Token to code repository
• Use CI/CD’s Secret management feature
• Regularly rotate Token

​

IP Whitelist

​

Monitoring & Alerts

• Monitor trigger call frequency
• Set up anomaly alerts
• Regularly review trigger logs

​

Related Features

• Test Round Templates
• Test Round List