Test design
Choosing what to test and why, so coverage reflects risk and requirement intent rather than the shape of the code.
Requirements change impact analysis
How to analyse the impact of a requirement change: what to trace, which tests to review, how to reassess earlier results, plus a worked example and a template.
Use case template and alternate flows
A use case template, a refund example with alternate and exception flows traced to criteria and tests, use case vs user story, and how ReqLens generates them.
Generating test cases from requirements
How to generate test cases from requirements, step by step: a worked refund example from acceptance criteria to linked test cases, review and approval.
Running a test cycle: a TestExecute guide
Why blocked is a first-class result rather than a kind of failure, what a run record needs to stay meaningful, and how execution feeds readiness.
What a QA Engineer actually does
QA is not the last step before release. It is the discipline of deciding what evidence would prove a requirement was met, and gathering it.