Chapter 1 defines what the Test Analyst actually does inside the test process, and it is where the exam fixes the boundary of the role: business-facing testing at system, system integration and acceptance level, functional suitability together with the user-facing quality characteristics, and black-box and experience-based work rather than white-box. Eight of the 45 exam questions come from here, worth 9 of the 78 points — seven K2 and one K3.
Inside the chapter the syllabus narrows the seven Foundation-level activities down to four and goes deep on each: test analysis (checking the basis for completeness and testability, prioritising test conditions), test design, test implementation (procedures, suites, preconditions and postconditions, smoke tests) and test execution (session-based exploratory work, confirmation and regression testing, analysing anomalies and false positives). Around those sit high-level versus low-level test cases and the nine quality criteria a test case is judged against, test environment requirements and test doubles, the test oracle problem and the answers to it — pseudo-oracles, model-based, property-based and metamorphic testing, human oracles, assertions — plus test data concerns such as synthetic data, pseudonymisation and service virtualisation, and keyword-driven testing.
Most questions here are recognition and distinction questions rather than calculations, which makes them fast marks, but the distinctions are fine: high-level against low-level test cases, action against verification keywords, domain layer against test interface layer. The syllabus allocates 225 of its 1,215 training minutes to this chapter. Our practice pool for it holds 24 questions.
This chapter is covered most heavily (8 questions) in CTAL-TA — Mock Exam 1 (Test Design Techniques Deep Dive), CTAL-TA — Mock Exam 2 (Domain Partitioning, State Models & Risk-Based Test Design), CTAL-TA — Mock Exam 3 (Test Oracles, Combinatorial Design & Defect Metrics)