ISTQB CTAL-TA study materials
ISTQB CTAL-TA study resources

ISTQB CTAL-TA study plan

ISTQB CTAL-TA · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

The Test Analyst's Tasks in Risk-Based Testing

  • Map every risk-based testing task the syllabus assigns to the test analyst onto one concrete activity you perform on a real or imagined project

  • Write 12 product-risk statements in cause–event–impact form and rank them by likelihood multiplied by impact

  • Separate product risk from project risk across 10 given project situations and write a one-line justification for each classification

  • Explain in writing how risk level drives test effort, test depth, level of detail in documentation and choice of test design technique

  • Describe how risk-based testing changes when a project is agile versus sequential

Your checkpoint

A one-page risk register containing 12 ranked product risks, each traced to at least one planned test activity, plus two written exam-style answers on risk mitigation through testing (300 words each).

Week 2

The Test Analyst's Tasks in Risk-Based Testing & Test Analysis and Design

  • Derive test conditions and test cases directly from the three highest-ranked risks in your register

  • Sequence a set of 20 test cases by risk and justify the execution order in a short written rationale

  • Explain how risk analysis outputs feed test analysis, test design and test prioritisation in the test process

  • Select a candidate test design technique for three short specifications and state why it is the best fit

  • Identify which risk-based testing tasks belong to the test analyst versus the test manager

Your checkpoint

A risk-to-test traceability table covering 3 risks, at least 10 test conditions and 15 test cases, plus a scored set of 30 practice questions on domains 1 and 2 with a written cause note for every incorrect answer.

Week 3

Test Analysis and Design

  • Write test cases for three small specifications using equivalence partitioning, boundary value analysis, decision tables and state transition testing, and calculate the coverage achieved for each

  • Derive statement-coverage and decision-coverage test cases from a short piece of pseudocode you write yourself

  • Compare error guessing, exploratory testing and checklist-based testing and state the situation where each is most appropriate

  • Distinguish test analysis from test design and list the work products each produces

  • Critique a deliberately poor set of 10 test cases, name the defect in each and rewrite them

Your checkpoint

A technique portfolio with one fully worked example for each of six techniques, including the test cases and the coverage figure calculated for each, plus a timed 20-question quiz scored at 75% or above.

Week 4

Test Analysis and Design & Testing Software Quality Characteristics

  • Explain how test analysis and design outputs feed test implementation and the traceability matrix

  • Apply a specification-based technique to a non-functional requirement and show how the resulting test conditions differ from functional ones

  • Name the quality characteristics of the ISO/IEC 25010 product quality model and give one test condition for each

  • Classify 15 given requirements under the correct quality characteristic and flag those that are untestable as written

Your checkpoint

A timed 40-question mock covering domains 1 and 2 with a written root-cause note for every missed question, plus a requirements-to-characteristic classification table for 15 requirements.

Week 5

Testing Software Quality Characteristics

  • Describe the test analyst's specific responsibilities for usability, performance efficiency, security, reliability, compatibility, maintainability and portability testing

  • Write test conditions for at least three non-functional characteristics and state the oracle you would use for each

  • Explain how quality characteristics interact and give two examples where optimising one degrades another

  • Identify which characteristics are most exposed by a given risk profile and justify the choice

Your checkpoint

A quality-characteristics matrix covering five characteristics, each with the test analyst's responsibilities, at least three test conditions, the oracle used, and the risk of neglecting that characteristic.

Week 6

Reviews

  • Compare the review types on formality, objectives, roles and typical work products in a single table you build from memory

  • Map the activities and role responsibilities of a formal review onto a worked example, stating what each role does at each step

  • Choose the most appropriate review type for six described situations and justify each choice

  • Assess six stated review success factors against a scenario and identify which are missing

  • Log findings with severity and classification from a short specification you write yourself and then review

Your checkpoint

A review package containing the review-type comparison table, a role-by-activity map, six situation-based justifications, and eight logged findings with severity and classification, plus a 30-question scored quiz on domain 4.

Week 7

Test Management and Defect Management

  • Trace a defect through every state of the defect management workflow and state the test analyst's action at each transition

  • Write two defect reports from described failures and check each against a completeness checklist

  • Classify 12 given defects by type, severity and priority and justify the severity-versus-priority distinction

  • Explain how the test analyst contributes to test planning, estimation, monitoring and control without owning them

  • Select the metrics that best communicate test progress and product quality in three described situations

Your checkpoint

Two rewritten defect reports that pass a completeness checklist, a 12-defect classification table, and a metrics-and-purpose table covering five metrics, scored against a self-written rubric.

Week 8

The Test Analyst's Tasks in Risk-Based Testing & Test Analysis and Design & Testing Software Quality Characteristics & Reviews & Test Management and Defect Management

  • Sit two full-length timed mock exams under exam conditions and record every answer's confidence level

  • Re-derive from memory the technique selection rules and the risk, review and defect-management key concepts in a one-page recall sheet

  • Re-attempt every previously missed question and confirm the reasoning, not just the answer

  • Rank your five weakest sub-topics by weighting domain share against your mock accuracy and drill only those

Your checkpoint

Two completed full-length timed mock exams at exam pace, each scored at 75% or above, with a written error log listing every miss, its sub-topic, the correct reasoning and the date of re-check.

Milestones

Week 2: Risk register, risk-to-test traceability table and a 30-question domain 1-2 practice set are complete, with every wrong answer analysed in writing.

Week 4: Score 75% or higher on a timed 40-question mock covering domains 1 and 2, and confirm the technique portfolio is complete.

Week 6: Score 75% or higher on a timed 40-question mock covering domains 3 and 4, and produce a ranked list of the three weakest sub-topics so far.

Week 8: Two full-length timed mocks both scored at 75% or above, error log fully re-worked, and a one-page recall sheet reproduced from memory without notes.