This is the largest chapter of the syllabus in both study time and exam presence, and the most practical. It covers exploratory testing end to end - test heuristics, test mnemonics, test tours, test charter creation and running timeboxed sessions - then assisted testing in its three forms (mob testing, pair testing and the new, still unstandardised vibe testing), and finally test smells as a way to judge the quality of test cases.
Two habits sink candidates here. The first is learning mnemonics as lists to be recited: they are idea generators aimed at a purpose, and a question will describe a situation and expect you to pick the mnemonic whose purpose matches it. The second is confusing a test smell with a defect - a smell is a property of the test, and it is a risk signal rather than an automatic fault. The chapter also carries an analysis-level objective, deriving test charters from user stories and epics, and those questions weigh more than recall ones.
Study by doing: write a charter with a mission and a scope, run a short session, then review the charter against reality.
A mnemonic as a generator of test ideas versus a mnemonic as a checklist to tick off; each of the five named ones has a purpose - regression, mobile, oracles, coverage of a product, automation success factors.
A test charter needs only a mission or test objectives and a scope; actor, setup, data, priority and oracle notes are optional additions.
A charter is a testable hypothesis about a session, not a test case with steps and expected results.
Acceptance criteria give lightweight test oracle notes but are never exhaustive oracles; missing or vague criteria are themselves a reason to explore.
A test smell is a symptom of a poorly designed test, not a product defect and not necessarily a problem - it signals risk and rising maintenance cost.
Know the smell categories, not only the individual names: dependency and complexity, expected results, test steps, level of detail, lack, excess, format and language.
Tours are districts of a product, and the seedy district is where negative testing, error guessing and fault attacks live.
Mob testing rotates roles on a short cadence around a moderator who never takes the driver role; pair testing is two people and fails differently, through cost, dominance and mental fatigue.
Vibe testing is intent-first validation of what the application should do in the real world, not an impressionistic look at generated code.
This chapter is covered most heavily (12 questions) in CTAL-AT — Mock Exam 1 (Fintech, Delivery and Booking Platforms), CTAL-AT — Mock Exam 2 (Telemedicine, Online Learning and Logistics Scenarios), CTAL-AT — Mock Exam 3 (Legacy Cores, Distributed Teams and Multi-Channel Services)