Manual Testing Learning Path: Start Here
In short: you learn manual testing in 6 milestones. Each one has a practice project on a free shop with real, deliberate bugs, and an answer key, so you always know how much you found. At the end you run a full test cycle and write the report a manager would read.
Read this page once to see the plan. Then, for each milestone, follow the same four steps: learn → test → check → save. Come back here whenever you're unsure what to do next.
The pages in this learning path
In short: each page has one job, so nothing is explained twice.
| Page | What it's for | When to open it |
|---|---|---|
| This roadmap | The plan: what each milestone covers and how to check yourself | At the start of each milestone |
| Manual testing cheat sheet | Learn each idea: short explanation, example, exercise | The "learn" step of every milestone |
| Milestones & Mini-Projects | A project and an answer key for each milestone | The "test" and "check" steps |
| Quick Reference | Templates, technique chooser, test-idea checklists | Any time you're testing |
| Best Practices | Habits that make testing sharper and more trusted | After Milestone 3, then before every sign-off |
| Manual & functional testing guide | Every testing type in depth | When you want the deeper "why" |
The milestones
In short: do them in order — each uses what the one before taught.
| Milestone | You learn | You work on | Rough time |
|---|---|---|---|
| 1 | Expected results, test cases, checklists | Login test suite | 1 week |
| 2 | Bug reports, severity, comparing with a reference | Bug hunt: problem_user | 1 week |
| 3 | Partitions, boundaries, decision tables, states | Test design from a spec | 1–2 weeks |
| 4 | Exploratory testing, charters, DevTools, oracles | Sessions on three buggy users | 1 week |
| 5 | Risk, smoke and regression, compatibility | Risk table + regression pack | 1 week |
| 6 | Requirements review, test plan, coverage, reporting | Full test cycle + summary report | 1–2 weeks |
Times assume about 5 hours a week.
For each milestone:
- Learn — read the cheat-sheet sections listed below.
- Test — do the project in Milestones & Mini-Projects, on the practice app.
- Check — compare your results with the expected results. Only then open the answer key, and note what you missed and why.
- Save — keep your work in a folder (or a Git repo) — it becomes your portfolio:
manual-testing-portfolio/
├── m1-login/test-cases.md
├── m2-bug-hunt/bug-reports.md
├── m3-test-design/design.md
├── m4-exploratory/session-notes.md
├── m5-regression/risk-and-regression.md
└── m6-full-cycle/plan.md, summary-report.md
Milestone 1: Test cases & checklists
Learn: What testing is · Errors, defects & failures · Expected vs actual · Test cases · Checklists
Work on: Login test suite
Check yourself:
- Why write the expected result before running the step?
- What makes a test case repeatable by someone else?
- When is a checklist better than a detailed test case?
Milestone 2: Bug reports
Learn: Bug reports · Severity & priority · Quick Reference: Bug report template
Work on: Bug hunt: problem_user
Check yourself:
- What goes in a good bug title?
- Who usually sets severity, and who sets priority?
- Why compare
problem_userwithstandard_userbefore reporting?
Milestone 3: Test design techniques
Learn: Equivalence partitioning · Boundary values · Decision tables · State transitions · Pairwise · Quick Reference: Which technique?
Work on: Test design from a spec
Then read: Best Practices, sections 1–5.
Check yourself:
- Why test invalid values one at a time?
- Which six values do you test for a range of 1 to 10?
- Why are forbidden state transitions worth testing?
Milestone 4: Exploratory testing
Learn: User journeys · Error guessing · Exploratory testing · DevTools for testers · Test oracles · Quick Reference: Heuristics
Work on: Sessions on three buggy users
Check yourself:
- What are the three parts of a charter?
- Name three oracles you can use when there is no spec.
- Where do you look when the screen shows no error but something failed?
Milestone 5: Risk & regression
Learn: Test levels · Test types · Smoke & regression · Risk-based testing
Work on: Risk table + regression pack
Check yourself:
- What two numbers make a risk score?
- What's the difference between re-testing and regression testing?
- Which regression checks would you automate first, and why?
Milestone 6: Plan, cover, report
Learn: Reviewing requirements · Strategy & plan · Coverage & traceability · QA metrics · Quick Reference: Test summary template
Work on: Full test cycle
Then read: Best Practices, sections 6–12.
Check yourself:
- What goes in the first line of a test summary?
- Why report what was not tested?
- How do you calculate defect removal efficiency?
When you get stuck
| Problem | What to do |
|---|---|
| "I can't find any bugs" | Compare with standard_user screen by screen; open DevTools → Console; try the input ideas |
| "Is this a bug or a feature?" | Name your oracle (spec, consistency, user expectation). If still unsure, log it as a question, not a bug |
| "The app behaves differently now" | Side menu → Reset App State, log out and in again, or use a private window |
| "My report feels too long" | Keep title, steps, expected, actual, evidence. Move everything else to Notes |
What's next
- Automate your regression pack: Test automation learning path.
- Test beneath the screen: API testing learning path.
- See the whole service: QA Services Delivery Playbook.
Good books to read alongside: Explore It! (Elisabeth Hendrickson) for exploratory testing, and Lessons Learned in Software Testing (Kaner, Bach, Pettichord) for 293 short, practical lessons. The ISTQB Foundation Level syllabus (free on istqb.org) covers the standard vocabulary.