Shift left in this syllabus means one thing: getting testing thinking into the test basis before code exists. The chapter covers testware acting as living requirements, storyboarding and testboarding, example mapping as a structured conversation, the biases that distort early quality work, user story slicing, and the four requirements engineering activities that make shift left possible.
The costly misconception is equating shift left with running automated tests earlier in the pipeline. That is tooling; this chapter is about conversation, visualisation and rewriting the requirement until it is testable. The chapter also holds the one application-level objective of this part of the syllabus - user story slicing - and application questions weigh more than recall ones, so the six slicing dimensions and the rules about acceptance criteria have to be usable, not merely recognisable.
Practise it hands-on: take an oversized story, map it into rules, examples and open questions, then slice it and rewrite the acceptance criteria for each slice. Learning the card colours without ever slicing a story is how candidates fail this chapter.
Shift left as early influence on the test basis versus shift left as an earlier automated pipeline: the second is not what is examined.
Storyboarding visualises the user journey scene by scene (usability, transitions, personas); testboarding visualises what to test - main and alternative scenarios, priorities, shared terminology. Swapping the two is the classic distractor.
Example mapping cards: yellow is the user story, blue are business rules, green are examples that become test cases, red are open questions.
Many red cards mean too much is still unknown; many blue cards, or one rule with a swarm of green ones, mean the story is too big and needs slicing.
The six slicing dimensions - workflow, data complexity, interface, scenario, vertical slice, constraints - with testability as the deciding criterion.
Acceptance criteria are rewritten for each slice and never copy-pasted; one narrow user-visible outcome per slice, and the slices together must cover the original story.
A bias is a systematic deviation from neutrality or accuracy, not carelessness: confirmation bias, the anchoring effect and conformity bias, with the whole team approach increasing the risk.
The requirements validation criteria are correct, unambiguous, complete, consistent and testable - a fixed list, not a general appeal to clarity.
This chapter is covered most heavily (9 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)