Your learner hub

Learn it. Do it. Keep the proof.

Your emails are the daily nudge. This is the permanent home for every lesson, download, practice task, and piece of evidence you build along the way. Progress saves in this browser.

Lesson checks stay on this device. Keep the work itself in your private portfolio workspace.

The full path

Three courses, one growing portfolio

Take them in order if you are new. Experienced testers can enter at the course that matches the work they need to do next.

Start here

QA Fundamentals

Ten days to think and work like a tester

Finish with test cases, two bug reports, an exploratory charter, and a release recommendation.

Time
20 to 30 minutes most days, 90 minutes for the capstone
Prerequisites
None. You only need a browser and somewhere to keep your work.
Progress0 of 11 lessons
What you will have at the end
  • Product promise list
  • Five sign-in test cases
  • Boundary-value results table
  • Two reproducible bug reports
  • Exploratory charter and debrief
  • Release recommendation
Course 2

Test Automation Basics

21 days from your first locator to a small suite that tells the truth

Finish with a Playwright suite, page objects, API checks, CI, and a red test that found a real bug.

Time
30 to 45 minutes a day. Keep one catch-up day each week.
Prerequisites
Comfort with manual testing. The first course is recommended, but not required.
Progress0 of 21 lessons
What you will have at the end
  • Local Playwright project
  • Reliable locator inventory
  • Page object and test suite
  • API contract checks
  • Failure report and trace
  • CI workflow and one-page strategy
Course 3

AI in QA

Ten days to put an AI agent to work on real QA, with every decision still yours

Finish with a rules file, evidence-first prompts, a reviewed diff, and a human release decision.

Time
30 to 45 minutes a day, with a longer capstone
Prerequisites
Working QA knowledge. Repo-aware AI access helps, but the safe demo pack works without workplace data.
Progress0 of 11 lessons
What you will have at the end
  • Access and context map
  • Evidence-first bug prompt
  • Repository rules file
  • Risk-first test plan
  • AI output review checklist
  • Release recommendation

Make the work visible when it is ready

Your certificate is the receipt. Your portfolio is the proof.

Start a private repository before you begin. Keep your evidence there, run the automated checks, then decide whether to make it public or share it privately with a recruiter.

Open the portfolio workspace