How Git and GitHub Help You Land a QA Tester Job Faster

#!/usr/bin/env bash
set -euo pipefail
git switch main
git pull --rebase
git switch -c add-login-tests

# ... write or update tests ...

git status
git add tests/test_login.py
git commit -m "Add tests for login with invalid password"
git pull --rebase origin main
git push -u origin add-login-tests
# Then open a pull request on GitHub

#!/usr/bin/env bash
# Inspect history and changes before committing
git log --oneline --graph -n 10     # recent history
git diff                            # unstaged changes
git diff --staged                   # what will be committed
git blame tests/test_login.py | head   # who changed each line
git restore tests/test_login.py     # undo local changes to a file

#!/usr/bin/env bash
# Test a pull request branch locally (replace 42 with the PR number)
set -euo pipefail
git fetch origin pull/42/head:pr-42
git switch pr-42
python -m pip install -r requirements.txt
python -m pytest -q
# Or with the GitHub CLI:
# gh pr checkout 42 && python -m pytest -q

Tested on branch pr-42 (Chrome, local env).

Works:
- Login with valid email and password
- Error shown for wrong password

Issue found:
- Submitting an empty email shows a server error (500) instead of
  a validation message.
  Steps: open /login -> leave email empty -> click Sign in
  Expected: 'Email is required' | Actual: 500 page

Suggest adding a test for the empty email case.

# .github/workflows/tests.yml
name: tests
on: [push, pull_request]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with: { python-version: "3.12" }
      - run: pip install -r requirements.txt pytest pytest-html
      - run: pytest -q --html=report.html --self-contained-html
      - if: always()
        uses: actions/upload-artifact@v4
        with:
          name: test-report
          path: report.html

# tests/test_discount.py
import pytest

def discount(total: float) -> float:
    if total < 0:
        raise ValueError("total cannot be negative")
    return round(total * 0.9, 2) if total >= 1000 else total

@pytest.mark.parametrize("total,expected", [(999, 999), (1000, 900.0), (1500, 1350.0)])
def test_discount_boundaries(total, expected):
    assert discount(total) == expected

def test_negative_total_rejected():
    with pytest.raises(ValueError):
        discount(-1)

Repo 1: manual-testing-samples
  - test plan, test cases (CSV or Markdown), bug reports with screenshots
Repo 2: api-tests
  - pytest + requests tests for a public practice API, CI workflow
Repo 3: ui-tests
  - Playwright or Selenium tests for a practice site, reports as artefacts

Each repo: README, how to run, sample report, CI badge

# API Tests for a Practice API

## What is tested
- Status codes, response fields, error handling

## How to run
pip install -r requirements.txt
pytest -q

## CI
Tests run on every push via GitHub Actions; reports are uploaded as artefacts.

## What I learned
- Boundary value tests
- Keeping tests independent

Week 1  Git basics: clone, branch, commit, push, pull requests
Week 2  Write pytest tests; add a GitHub Actions workflow
Week 3  Practise PR reviews with a friend; polish READMEs