Manual QA Professional

By the end you’ll be able to

• Write a test plan that fits on one page and survives contact with a deadline
• Rank work by risk and say out loud what you are not covering
• Run a chartered exploratory session and produce evidence from it
• Test an API directly, and verify results in the database
• Report status in terms a product owner acts on

1. 01Test planning that fits on one pageScope, risks, environments, entry and exit criteria — without the 40-page template.Hands-on14 min
2. 02Risk-based testingImpact × likelihood, and how to defend what you chose not to test.12 min
3. 03Exploratory and session-based testingCharters, timeboxes, note-taking, and why unscripted testing finds what scripts can't.Hands-on14 min
4. 04Test oracles: how do you know it's wrong?Requirements, comparable products, history, and heuristics for when there is no spec.10 min
5. 05HTTP and browser dev tools for testersStatus codes, headers, the network tab, and reading a failed request like a developer.12 min
6. 06API testing with PostmanRequests, environments, chaining, assertions, and testing the API a UI hides.Hands-on15 min
7. 07SQL for verificationSELECT, JOIN and GROUP BY — enough to prove what the screen is claiming.14 min
8. 08Cross-browser and mobile testingBuilding a device matrix from analytics instead of superstition.11 min
9. 09Accessibility basicsKeyboard, contrast, labels, screen readers — the checks that take ten minutes.12 min
10. 10Non-functional testing you can do todayCheap first checks for performance, security and reliability.12 min
11. 11Metrics that mean somethingPass-rate theatre, escape rate, and what to put on a dashboard.Hands-on11 min
12. 12Reporting to stakeholdersTurning results into a decision, in five sentences.10 min