You can't test everything, so the skill is choosing which tests to run. Test design techniques turn a requirement into a small, sharp set of test cases that find the most bugs for the least effort.
You'll start with the black-box techniques every tester uses: equivalence partitioning and boundary value analysis for inputs, then decision tables and state transition testing for rules and workflows. Then you'll see how exploratory testing finds the bugs scripted tests miss, and how smoke, sanity, and regression testing keep a product stable as it changes.
With a toolkit for designing tests, you'll be ready for the next module, Test Management & Bug Reporting, where you plan, track, and report on that work.
How to split inputs into groups that behave alike, test one value from each, and then focus on the edges where bugs tend to hide.
Two techniques for systems with rules: tables that cover every combination of conditions, and state diagrams that cover valid and invalid moves between states.
What exploratory testing is, how it differs from scripted testing, and a worked example of learning and testing the product at the same time.
When to use each one, how they differ in scope, and how they fit together into a regression strategy as your product changes.