​
GitHub Integration

Automate your QA process by integrating QA.tech with your GitHub workflows. You can trigger test runs automatically after deployments, on pull requests, or any other GitHub event.

1

Configure Secrets

Add the following secrets to your GitHub repository:

  • QATECH_API_TOKEN - Your QA.tech API token
  • QATECH_PROJECT_ID - Your QA.tech project ID

You can find these values in your project settings.

Learn more about creating secrets in GitHub Actions.

2

Basic Setup

Create a new workflow file in your repository at .github/workflows/qatech.yml:

name: QA.tech Tests
on:
  push:
    branches:
      - main

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: QAdottech/run-action@v1
        with:
          project_id: ${{ secrets.QATECH_PROJECT_ID }}
          api_token: ${{ secrets.QATECH_API_TOKEN }}
          blocking: true

This will run all tests in your project whenever code is pushed to the main branch, and the blocking option will make it wait for the result of the run before completing the workflow.

3

Advanced Setup

For more control, you can:

  1. Run specific test plans by adding their IDs:
- uses: QAdottech/run-action@v1
  with:
    project_id: ${{ secrets.QATECH_PROJECT_ID }}
    api_token: ${{ secrets.QATECH_API_TOKEN }}
    test_plan_short_ids: 'abc123,def456'
    blocking: true
  1. Trigger tests after deployment:
name: 'Deploy and Test'
jobs:
  deploy:
    # Your deployment steps here

  qatech-tests:
    needs: deploy
    runs-on: ubuntu-latest
    steps:
      - uses: QAdottech/run-action@v1
        with:
          project_id: ${{ secrets.QATECH_PROJECT_ID }}
          api_token: ${{ secrets.QATECH_API_TOKEN }}
          blocking: true

For more information about our API and other integration options, check out our API Reference.

Email InboxEnvoyer