Free QA courses

Build proof you can defend.

Your certificate records the course. This workspace holds the test cases, reports, code, review notes, and automated checks that show how you think.

Download the portfolio workspaceBack to learner hub

Start private

This is your repository, not mine.

Create a private repository in your own GitHub account before you begin. Keep it private while you learn, make mistakes, and remove anything you would not show a recruiter.

After you create an empty private repository:

git init
git add .
git commit -m "Start QA course portfolio"
git branch -M main
git remote add origin YOUR_PRIVATE_REPOSITORY_URL
git push -u origin main

The finish line, made practical

Four steps from course work to evidence

  1. 01

    Set up the workspace

    Download the pack, make the repository private, and commit the clean starting point.

  2. 02

    Put each artifact where it belongs

    Save your test cases, bug reports, exploratory notes, release recommendation, automation code, AI review notes, screenshots, and traces in the matching folders.

  3. 03

    Run the evidence checks

    The included GitHub Actions workflow runs the safe AI test and the Playwright starter on every push. At the end, the local portfolio check refuses empty evidence files.

  4. 04

    Choose how to share it

    Make it public when it is safe and polished, or keep it private and share access only with a recruiter. Both choices are professional.

What someone can inspect

A certificate is not the main event.

A hiring manager should be able to open your README and find an honest test case, a reproducible bug report, a release decision, a small Playwright suite, a review of an AI-generated change, and the output that proves your checks ran.

  • QA Fundamentals: product risks, cases, reports, and release call
  • Automation: Playwright tests, page objects, CI run, and a truthful red
  • AI in QA: rules, prompt, evidence review, and human decision

Keep it safe to share

Never turn a portfolio into a leak.

Do not include workplace source code, customer details, credentials, internal tickets, or private screenshots. Use Tumble Kitchen and the safe Tallawah Billing demo pack. They are designed so you can show real QA thinking without exposing anyone else’s work.