This action integrates your GitHub workflow with QA.tech, triggering test runs automatically when configured events occur.

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

jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: QAdottech/run-action@v1
        with:
          project_id: 'your-project-id'
          api_token: ${{ secrets.QATECH_API_TOKEN }}
          test_plan_short_id: 'jgbinp'

You can find your project ID and generate an API token in your QA.tech project settings.

Specify which test plan to run by providing its ID in the test_plan_short_id input. To run multiple test plans, simply use the GitHub Action multiple times in your workflow.

For example:

- uses: QAdottech/run-action@v2
  with:
    project_id: 'your-project-id'
    api_token: ${{ secrets.QATECH_API_TOKEN }}
    test_plan_short_id: 'jgbinp'

The action supports a blocking mode that will wait for the test run to complete before proceeding. When enabled, the action will:

1. Create the test run
2. Poll the run status until completion
3. Set additional outputs with the final status and result
4. Fail the GitHub Action if the test run fails

To enable blocking mode, set the blocking input to true:

- uses: QAdottech/run-action@v2
  with:
    project_id: 'your-project-id'
    api_token: ${{ secrets.QATECH_API_TOKEN }}
    blocking: true

When blocking is enabled, the action provides additional outputs:

• run_status: The final status of the run (INITIATED, RUNNING, COMPLETED, ERROR, or CANCELLED)
• run_result: The test execution result (PASSED, FAILED, or SKIPPED)

You can override application environments for specific runs using the applications_config input. This is useful for testing against preview deployments or specific environment URLs.

The input expects a JSON string with the following format:

{
  "applications": {
    "appId": {
      "environment": {
        "url": "https://preview-123.vercel.app",
        "name": "Preview Environment"
      }
    }
  }
}

- uses: QAdottech/run-action@v2
  with:
    project_id: 'your-project-id'
    api_token: ${{ secrets.QATECH_API_TOKEN }}
    test_plan_short_id: 'jgbinp'
    applications_config: |
      {
        "applications": {
          "short-id-1": {
            "environment": {
              "url": "https://preview-123-hackoffice.vercel.app"
            }
          }
        }
      }

You can override multiple applications in a single run:

Note: Check on app.qa.tech under Test Plans → API Integration to see which applications are connected to your test plan.

applications_config: |
  {
    "applications": {
      "short-id-2": {
        "environment": {
          "url": "https://preview-123-hackoffice.vercel.app",
          "name": "PR-123"
        }
      },
      "short-id-2": {
        "environment": {
          "url": "https://preview-123-saas.vercel.app",
          "name": "PR-123"
        }
      }
    }
  }

# Install dependencies
pnpm install

# Run tests
pnpm test

# Build
pnpm build

# Lint
pnpm lint

MIT