GitHub Actions Basics for QA

GitHub Actions is one of the most common CI platforms for teams using GitHub, and QA engineers are expected to understand how to wire tests into its workflows. With just a few YAML files, you can make sure every push or pull request triggers the right automated checks.

Key GitHub Actions Concepts for Testers #

Workflows are YAML files stored in the .github/workflows/ folder, triggered by events such as pushes or pull requests, and composed of jobs and steps. Each job runs on a runner (like ubuntu-latest) and steps can use actions or run shell commands.

# .github/workflows/tests.yml
name: CI Tests

on:
  push:
    branches: [ main ]
  pull_request:
    branches: [ main ]

jobs:
  tests:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: 20
      - name: Install dependencies
        run: npm ci
      - name: Run tests
        run: npm test

Once you are comfortable reading existing workflows, you can propose improvements such as adding new jobs for API or UI tests.

Common Mistakes #

Mistake 1 — Treating workflows as “only DevOps code” #

This reduces QA influence.

❌ Wrong: Never opening the .github/workflows folder or learning YAML basics.

✅ Correct: Read and understand workflows so you can suggest changes that improve test coverage.

Mistake 2 — Using overly broad or missing triggers #

This causes noisy or missing runs.

❌ Wrong: Triggering heavy test workflows on every branch, including experimental ones.

✅ Correct: Configure on to match your needed branches and events, such as push and pull_request to main.