ISTQB CT-UT study plan

Define usability testing in your own words and contrast it with functional testing using three concrete examples

Map the usability evaluation methods (inspection, inquiry, formal usability testing, user observation) to when each is appropriate in a test strategy

Identify the inputs a usability test needs (representative users, tasks, environment, success criteria) and list what happens when each is missing

Draft an initial usability risk register with at least eight risks covering efficiency, effectiveness, satisfaction, and error tolerance

Explain how heuristic evaluation and cognitive walkthrough work, including the roles of evaluator and facilitator

Write task scenarios and success criteria for a fictional login-and-checkout flow that avoid leading the participant

Describe how to record, code, and prioritize observed usability defects by severity and frequency

Link each usability defect type back to a risk category in your register and update the register accordingly

Specify the physical and technical set-up for a moderated usability session, including room layout, recording, consent, and observer placement

Configure a test environment that mirrors production sufficiently (browser, device, network, data) and document the deviations you accept

Prepare test data and accounts that avoid exposing real personal data while still being realistic

Identify the UX factors (learnability, efficiency, memorability, error rate, satisfaction) that your set-up must be able to observe

Distinguish usability from user experience and explain how emotion, expectations, and context shape perceived quality

Define measurable UX metrics (task completion rate, time on task, error rate, satisfaction score) and state how each is collected

Draft a session moderation guide with neutral prompts, think-aloud instructions, and recovery tactics for a stuck participant

Run one pilot session with a colleague and revise the script and set-up checklist based on what broke

Explain the four WCAG principles (perceivable, operable, understandable, robust) and give one concrete failure example per principle

Map the WCAG conformance levels A, AA, and AAA to typical organizational policy decisions and state why AA is the common baseline

Test keyboard-only navigation, focus order, and visible focus on a sample page and record each barrier found

Check color contrast, text alternatives, and form labels against WCAG success criteria and log pass or fail with the criterion reference

Summarize the scope and purpose of ISO 9241-11 and ISO 9241-210 and explain how they frame usability and human-centred design in a test plan

Describe how WCAG 2.2 relates to other standards and to legal accessibility requirements, without overstating what any standard mandates

Compare assistive-technology testing (screen reader, magnification, voice control) with automated accessibility checks and state what each can and cannot catch

Write test conditions that trace from a standard requirement or success criterion to an executable check

Consolidate your usability risk register, re-score each risk, and map each to the test technique that would expose it

Identify risks that standards and accessibility requirements mitigate and note residual risk where no standard applies

Explain how usability risk feeds release decisions and how to report residual risk to stakeholders in business language

Review weak areas from weeks 1-6 and write targeted practice questions on the two domains you scored lowest

Rehearse the full exam scope by answering timed practice questions across all six domains and analyzing every wrong answer

Recite from memory the key definitions, WCAG principles and levels, and the purpose of each named standard

Walk through your own end-to-end usability test workflow from planning to reporting to confirm no step is missing

List your five weakest topics and close each with a written one-paragraph summary in your own words