Manual Testing Tutorial
Manual testing is how almost every QA career starts, and it stays useful for your
entire career even after you learn automation — a script can only check what someone already thought
to check, but a human tester notices the thing nobody thought of. This track covers
22 lessons: what testing actually is, the test case design techniques professional
testers use to find bugs on purpose instead of by luck, the full bug life cycle, and how to write test
plans and bug reports that make you look competent to a dev team. Throughout the track we test one
example app together — RecipeBox, a recipe-manager app — so every technique is
grounded in a real screen, a real form, a real bug, not an abstract example.
Why Manual Testing Still Matters
| Myth | Reality |
|---|
| "Automation will replace manual testing" | Automation only re-checks things a human already verified once. New features, UI/UX judgment, and exploratory bug-hunting still need a person. |
| "Manual testing is just clicking around" | Done properly it's a designed process: test case techniques, coverage tracking, and a documented bug life cycle — this track teaches exactly that process. |
| "You need to code to be a tester" | You don't, for this track. (You will for the Postman and Selenium tracks later, if you choose to go that route.) |
A Quick Look Ahead: Finding a Real Bug
Example: Testing RecipeBox's "Add Recipe" Prep-Time Field
Say the "Add Recipe" screen has a numeric "Prep Time (minutes)" field. Instead of just typing "20" and moving on, a trained tester tries values designed to break it:
| Input | Why a tester tries this | Expected vs actual |
|---|
| 0 | Boundary value — is 0 minutes valid? | Should probably be rejected; if RecipeBox accepts it, that's a bug |
| -5 | Invalid/negative input | Must be rejected with a clear error message |
| (empty) | Required-field check | Should block form submission |
| 99999 | Unrealistic upper boundary | Should probably be capped or flagged, not silently accepted |
Note: This is exactly what "Boundary Value Analysis" and "Equivalence Partitioning" formalize — you'll learn both by name, with more examples, a few lessons into this track.
What You'll Learn In This Track
| Area | Covered in |
|---|
| Foundations | What testing is, SDLC vs STLC, verification vs validation, levels of testing, black/white/grey box, manual vs automation |
| Test case design | Equivalence partitioning, boundary value analysis, decision tables, state transition testing, writing effective test cases |
| Testing in practice | Smoke vs sanity testing, regression testing, exploratory testing |
| Bug management | Bug life cycle, severity vs priority, writing a good bug report |
| Planning & documentation | Test plans & strategy, UAT, requirement traceability matrix |