Be able to take a real feature, design a defensible set of tests, run them through the interface and the API, and file defect reports developers act on without a single follow-up question. Most beginner testing courses are a tour of tools: hours of clicking through a tracker and a REST client, with nothing you produce and nothing that tells you whether you got it right. This one is a method, and it is built to be checked.
You are starting in QA, or trying to get in. You have clicked around software and found things that looked wrong, but you have no system for deciding what to test, no vocabulary that survives a conversation with a developer, and nothing you could show a hiring manager. You are not a programmer, and you do not need to be one here.
Across sixty short lessons in eleven modules, you build one skill at a time: saying precisely what a passing test licenses you to claim, pulling testable conditions out of a vague user story, ranking them by risk when there is no time to run them all, writing a test case a colleague can run without asking you a question, and deriving tests with equivalence partitioning, boundary value analysis, decision tables and state models. Then you test a feature that has no specification at all, send requests to an API and assert on what comes back, and write defect reports that get fixed rather than triaged into silence.
