The CAST (Certified Associate in Software Testing) certification, awarded by ASTQB—the US National Board of ISTQB—validates your foundational knowledge of software testing principles. Whether you're prepping for your first attempt or brushing up before exam day, printing out practice questions is one of the most effective study methods around. This free CAST practice test PDF covers all the core exam domains so you can study anywhere, anytime—no Wi-Fi required.
Our downloadable PDF mirrors the structure of the real CAST examination: multiple-choice questions drawn from software testing fundamentals, the test process lifecycle, static testing, test design techniques, test management, and tool support. Work through the questions at your own pace, circle the ones you miss, and revisit them until the concepts stick.
Facts verified Oct 22, 2026 against PeopleCert. Dates that have passed are removed automatically.
Facts verified Oct 22, 2026 against PeopleCert. Dates that have passed are removed automatically.
| Item | Detail | Official source |
|---|---|---|
| Time limit | 75 minutes | PeopleCert |
| Passing score | 70% | PeopleCert |
| Eligibility | No formal prerequisites | PeopleCert |
Facts verified Oct 22, 2026 against PeopleCert. Dates that have passed are removed automatically.
The CAST syllabus is built around seven major knowledge areas. Understanding each one—not just memorizing definitions—is what separates passing candidates from those who fall short.
This domain establishes the "why" behind testing. You need to know the difference between defect prevention and defect detection, and be able to apply all seven testing principles: testing shows the presence of defects (not their absence), exhaustive testing is impossible, early testing saves time and money, defects cluster in a small number of modules, repeating the same tests eventually stops finding new bugs (the pesticide paradox), testing is context-dependent, and the absence-of-errors fallacy—shipping defect-free software that doesn't meet user needs is still a failure.
The CAST exam tests your understanding of the full testing lifecycle: test planning, test analysis, test design, test implementation, test execution, test reporting, and test completion activities. Each phase has specific entry and exit criteria, deliverables, and roles. Know what a test plan contains, how test cases are derived from test conditions, and how defect reports feed back into the process.
Candidates must understand testing in the context of different development models—the V-model (where each development phase has a corresponding test phase), waterfall (sequential, late testing), and agile (continuous testing, short iterations, whole-team quality approach). The principle: the earlier testing is involved, the cheaper defects are to fix.
Static testing finds defects without executing code. Review types include informal reviews (no formal process), walkthroughs (author-led, learning-focused), technical reviews (peer-led, defect finding), and inspections (most formal, metrics-driven, with a trained moderator). Static analysis tools—linters, code analyzers—detect issues like unreachable code, undefined variables, and security vulnerabilities at the source level.
This is one of the most heavily tested domains. Black-box techniques derive tests from specifications: equivalence partitioning (divide inputs into classes that behave the same), boundary value analysis (test at and just beyond the edges of valid ranges), decision table testing (combinations of conditions and actions), state transition testing (system behavior across states and events), and use case testing (realistic user scenarios). White-box techniques look inside the code: statement coverage (every line executed at least once) and decision/branch coverage (every branch taken). Experience-based techniques—error guessing, exploratory testing, checklist-based testing—rely on tester knowledge and creativity.
Test management covers test planning elements (scope, objectives, approach, resources, schedule, risks), risk-based testing (prioritizing tests based on likelihood and impact of failure), test estimation techniques (metrics-based, expert judgment), and test monitoring and control (tracking progress against the plan, taking corrective action).
Understand the categories of test tools: test management tools (tracking test cases, results, and defects), test automation tools (record/playback, scripted automation, CI/CD integration), performance testing tools, static analysis tools, and defect management tools. Know benefits and risks of test automation—automation doesn't replace exploratory testing and requires ongoing maintenance.
PDFs are great for offline review, but online practice tests let you simulate the real exam with timed sessions, instant scoring, and detailed answer explanations. Head over to our CAST practice test hub to access full-length timed exams and topic-by-topic quizzes covering every domain on the ASTQB syllabus. Use both formats together—print the PDF for your commute, then run timed online tests in the final week before your exam—to maximize your score.
Try these questions from our free Certified Associate in Software Testing practice tests. The correct answer and an explanation follow each question.
Which scenario would require a associate in software testing professional to escalate a test planning and execution concern?
Answer: D. Creating feedback mechanisms that encourage continuous improvement
Creating feedback mechanisms that encourage continuous improvement is the correct approach because effective test planning and execution in the associate in software testing field requires adherence to professional standards, evidence-based practices, and systematic methodology. This approach ensures consistent, high-quality outcomes while maintaining professional accountability.
What distinguishes an advanced associate in software testing practitioner's approach to professional ethics & standards from that of a novice?
Answer: B. Establishing cross-functional teams with clearly defined roles
Establishing cross-functional teams with clearly defined roles is the correct approach because effective professional ethics & standards in the associate in software testing field requires adherence to professional standards, evidence-based practices, and systematic methodology. This approach ensures consistent, high-quality outcomes while maintaining professional accountability.
When a test process is assessed using TMMi (Test Maturity Model integration), which level indicates that testing is defined and documented as a standard process?
Answer: C. Level 3 – Defined
TMMi Level 3 (Defined) means the test process is documented, standardized, and integrated across the organization.
What is a 'test bed' in software testing?
Answer: B. The complete environment — hardware, software, and tools — needed to run tests
A test bed refers to the complete setup including hardware, software, simulators, and tools needed for test execution.
Take the full Certified Associate in Software Testing practice test