QAI CAST study guide
QAI CAST · Work through your exam, one topic at a time.
The Certified Associate in Software Testing (CAST) is a credential offered by QAI Global Institute, a training and certification organization. It is designed for professionals who are new to software testing or who want to establish a foundational understanding of testing principles and practices. The QAI CAST study guide has 5 sections and about 2,225 words.
01Software Testing Fundamentals
Software Testing Fundamentals tests whether you understand what testing is for and where it sits among quality activities. CAST questions in this domain are conceptual: definitions, the defect chain, test levels, and the principles that explain why exhaustive testing is impossible and why risk must drive coverage.
481 words, about 2 min02Test Planning and Design
Test Planning and Design covers how you decide what to test, how much, and with which techniques. CAST expects you to know a test plan's components, measurable entry and exit criteria, risk-based prioritisation, and the black-box techniques that turn requirements into concrete test cases.
437 words, about 2 min03Test Execution and Defect Management
Test Execution and Defect Management is the operational core of testing: running cases from a controlled baseline, recording results honestly, and turning failures into actionable, trackable defects. CAST questions focus on the defect life cycle, the distinction between severity and priority, and the discipline that makes a defect report useful to a developer.
451 words, about 2 min04Test Measurement and Metrics
Test Measurement and Metrics asks whether testing is effective and whether you can prove it. CAST tests the meaning and arithmetic of common measures, plus the judgement to use them without distorting behaviour.
431 words, about 2 min05Testing Tools and Automation Basics
Testing Tools and Automation Basics covers the tool landscape and the economics of automation. CAST expects you to categorise tools by purpose, know what record/playback can and cannot do, understand the main automation frameworks, and reason about when automation pays back rather than assuming it always does.
425 words, about 2 min