Testing - lesson 6 | HackIndia Skills

Testing - lesson 6 | HackIndia Skills | HackIndia

Example

Node.js workflow

Create this file in your repo. Use it if your project has package.json and runs tests with npm test.

The workflow installs dependencies with npm ci, then runs your test script on every push and pull request.

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

on:
  push:
  pull_request:

jobs:
  test:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout code
        uses: actions/checkout@v4

      - name: Set up Node.js
        uses: actions/setup-node@v4
        with:
          node-version: 20

      - name: Install dependencies
        run: npm ci

      - name: Run tests
        run: npm test

Example

Python workflow

Use this version if your tests run with pytest. Keep a requirements.txt file in the repo, or change the install step to match your project.

If you use FastAPI, Flask, or Django, this same pattern still works. CI should run the command you already use locally.

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

on:
  push:
  pull_request:

jobs:
  test:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout code
        uses: actions/checkout@v4

      - name: Set up Python
        uses: actions/setup-python@v5
        with:
          python-version: "3.11"

      - name: Install dependencies
        run: pip install -r requirements.txt

      - name: Run tests
        run: pytest

Common mistake

Green by accident

A workflow can pass even when it did not run your real tests. This happens when npm test only prints a message, or when pytest finds zero tests.

Open the workflow log after the first run. Look for your test runner output and the number of tests. Fix the script if CI is only pretending to test.

// package.json
{
  "scripts": {
    "test": "jest"
  }
}

Run tests on every push

One proof signal

What CI does

Before you add CI

Node.js workflow

Python workflow

Use AI carefully

Green by accident

Do this now

Quick check