ISTQB CTAL-TM cheat sheet

Organizational test strategy = generic, long-lived, reusable across projects; test approach = project-specific adaptation of that strategy, documented in the test plan.

ISTQB distinguishes strategy content by: test levels, test types, entry/exit criteria, test techniques, independence level, and test environment/automation policies.

Test approach selection drivers: risk level, business domain criticality, contractual/regulatory constraints, SDLC model, team skill, tool availability, time-to-market pressure.

Sequential (V-model, waterfall) favors early detailed test planning and formal gate reviews; iterative/incremental shifts planning to per-iteration level with regression emphasis.

Agile test approach characteristics: whole-team quality ownership, test-first (ATDD/TDD), lightweight documentation, continuous regression via automation.

Risk-based approach: prioritize test effort by risk exposure (likelihood x impact); highest-risk items get most rigorous techniques and earliest execution.

Methodical approach: follows a predefined set of test conditions (e.g., checklists, standards compliance) without formal risk analysis.

Reactive approach: testing driven by defects found and exploratory/ad-hoc investigation rather than pre-planned conditions; suited to poorly documented or unstable specs.

Consultative approach: test coverage guided by input from stakeholders/users rather than internal risk or formal models.

Test roles per ISTQB: test manager (planning, monitoring, control, reporting), test leader (level/phase coordination), tester (analysis, design, execution, reporting).

Skill categories: testing-specific (techniques, tools), domain knowledge (business/technology), and soft skills (communication, analytical, diplomatic reporting).

TMMi and CTP (Certified Tester Professional) describe maturity/competency growth paths; TPI Next uses maturity levels per key area for process improvement.

Independence levels (low to high): author tests own code, tests by teammates in same team, tests by independent testers in same org, tests by external/outsourced testers.

Higher independence reduces author bias but can reduce information sharing and slow feedback; choice depends on risk and domain criticality.

Motivation factors (Herzberg-style application): recognition, challenging work, career path, adequate tools; hygiene issues such as poor environment erode motivation.

Team composition decisions: ratio of testers to developers, skill mix (automation vs. manual/exploratory), location (co-located vs. distributed), and outsourcing scope.

Competency gap analysis: compare required skills per role against current skills; close gaps via training, mentoring, pairing, or recruitment.

Onboarding a new tester requires: domain overview, test process/strategy documents, tool access, and a supervised first assignment.

Test process groups (ISTQB): planning, monitoring & control, analysis, design, implementation, execution, completion - activities overlap and are iterative.

Entry criteria gate the start of a test level (e.g., build available, smoke test passed, test data ready); exit criteria gate completion (e.g., coverage threshold, defect closure rate).

In sequential models, test levels map to development phases; in iterative models, all levels may occur within each iteration (shift-left).

Shift-left: static analysis, reviews, and early test design reduce defect cost; shift-right: production monitoring, A/B testing, and operational feedback.

Continuous integration/continuous delivery requires automated regression suites, version-controlled testware, and fast feedback loops.

Regression testing scope grows with each increment; select tests by change impact and risk rather than rerunning everything blindly.

Maintenance testing triggers: perfective (improvements), corrective (defects), adaptive (environment changes), preventive (refactoring/technical debt).

Test completion activities: archive testware for reuse, hand over known defects and residual risk, capture lessons learned, release resources.

DevOps/Agile: test manager role shifts toward enabling quality culture, cross-functional team coaching, and cross-team coordination of test environments and data.

Test plan contents (IEEE 829 / ISO 29119-aligned): scope, objectives, approach, entry/exit criteria, schedule, resources, risks, deliverables, environment, and metrics.

Estimation techniques: expert judgment, analogy (similar past projects), work breakdown structure, three-point estimation (optimistic + 4x likely + pessimistic) / 6, and function/use-case point analysis.

Test effort factors: product risk, complexity, size, required coverage, process maturity, team skill, and tool support.

Monitoring compares actual vs. planned: test case execution progress, defect discovery rate, coverage achieved, effort spent, and schedule variance.

Control actions when off-plan: re-prioritize test cases, adjust scope, add/reallocate resources, escalate risks, or revise exit criteria with stakeholders.

Common metrics: test case execution percentage, pass/fail rate, defect density (defects per size/function), defect detection percentage (DDP = defects found in test / total defects found), and defect removal efficiency.

Defect detection percentage (DDP) = defects found by a given test level / total defects found by that level and later phases x 100%.

Test progress report: periodic, factual status; test summary report: end-of-level/project, includes assessment against exit criteria and residual risk.

Earned value application: planned value vs. earned value vs. actual cost; schedule performance index (SPI) = EV/PV, cost performance index (CPI) = EV/AC.

Stakeholder categories: business/product owners, developers, operations, end users, regulators, and external suppliers; each has different information needs and influence.

RACI matrix assigns Responsibility, Accountability, Consultation, and Information rights for test activities and deliverables.

Product risk = possibility that a product characteristic fails to meet stakeholder needs; project risk = possibility that the project fails to meet its objectives (schedule, budget, resources).

Risk analysis = risk identification + risk assessment (likelihood x impact); risk control = risk mitigation, contingency, transfer, and acceptance.

Risk-based testing process: identify risks, assess and prioritize, select test conditions/techniques, execute highest-risk first, monitor risk as it changes.

PRAM (Pragmatic Risk Analysis and Management) and risk matrices are common frameworks for assigning risk levels and owners.

Defect management lifecycle: new -> assigned -> open -> fixed -> retest -> closed, with reopen and reject/defer branches; each transition is logged with an audit trail.

Defect report essential fields: ID, summary, environment/build, steps to reproduce, expected vs. actual result, severity, priority, status, reporter, assignee.

Severity (impact on the system) and priority (urgency of fix) are independent; a low-severity cosmetic defect can be high priority for a demo or release.

Defect triage meeting participants: test manager/leader, development lead, product owner; decisions include fix now, defer, reject (not a defect), or duplicate.

Organizational test strategy = generic, long-lived, reusable across projects; test approach = project-specific adaptation of that strategy, documented in the test plan.

ISTQB distinguishes strategy content by: test levels, test types, entry/exit criteria, test techniques, independence level, and test environment/automation policies.

Test approach selection drivers: risk level, business domain criticality, contractual/regulatory constraints, SDLC model, team skill, tool availability, time-to-market pressure.

Sequential (V-model, waterfall) favors early detailed test planning and formal gate reviews; iterative/incremental shifts planning to per-iteration level with regression emphasis.

Agile test approach characteristics: whole-team quality ownership, test-first (ATDD/TDD), lightweight documentation, continuous regression via automation.

Risk-based approach: prioritize test effort by risk exposure (likelihood x impact); highest-risk items get most rigorous techniques and earliest execution.

Methodical approach: follows a predefined set of test conditions (e.g., checklists, standards compliance) without formal risk analysis.

Reactive approach: testing driven by defects found and exploratory/ad-hoc investigation rather than pre-planned conditions; suited to poorly documented or unstable specs.

Consultative approach: test coverage guided by input from stakeholders/users rather than internal risk or formal models.

Test roles per ISTQB: test manager (planning, monitoring, control, reporting), test leader (level/phase coordination), tester (analysis, design, execution, reporting).

Skill categories: testing-specific (techniques, tools), domain knowledge (business/technology), and soft skills (communication, analytical, diplomatic reporting).

TMMi and CTP (Certified Tester Professional) describe maturity/competency growth paths; TPI Next uses maturity levels per key area for process improvement.

Independence levels (low to high): author tests own code, tests by teammates in same team, tests by independent testers in same org, tests by external/outsourced testers.

Higher independence reduces author bias but can reduce information sharing and slow feedback; choice depends on risk and domain criticality.

Motivation factors (Herzberg-style application): recognition, challenging work, career path, adequate tools; hygiene issues such as poor environment erode motivation.

Team composition decisions: ratio of testers to developers, skill mix (automation vs. manual/exploratory), location (co-located vs. distributed), and outsourcing scope.

Competency gap analysis: compare required skills per role against current skills; close gaps via training, mentoring, pairing, or recruitment.

Onboarding a new tester requires: domain overview, test process/strategy documents, tool access, and a supervised first assignment.

Test process groups (ISTQB): planning, monitoring & control, analysis, design, implementation, execution, completion - activities overlap and are iterative.

Entry criteria gate the start of a test level (e.g., build available, smoke test passed, test data ready); exit criteria gate completion (e.g., coverage threshold, defect closure rate).

In sequential models, test levels map to development phases; in iterative models, all levels may occur within each iteration (shift-left).

Shift-left: static analysis, reviews, and early test design reduce defect cost; shift-right: production monitoring, A/B testing, and operational feedback.

Continuous integration/continuous delivery requires automated regression suites, version-controlled testware, and fast feedback loops.

Regression testing scope grows with each increment; select tests by change impact and risk rather than rerunning everything blindly.

Maintenance testing triggers: perfective (improvements), corrective (defects), adaptive (environment changes), preventive (refactoring/technical debt).

Test completion activities: archive testware for reuse, hand over known defects and residual risk, capture lessons learned, release resources.

DevOps/Agile: test manager role shifts toward enabling quality culture, cross-functional team coaching, and cross-team coordination of test environments and data.

Test plan contents (IEEE 829 / ISO 29119-aligned): scope, objectives, approach, entry/exit criteria, schedule, resources, risks, deliverables, environment, and metrics.

Estimation techniques: expert judgment, analogy (similar past projects), work breakdown structure, three-point estimation (optimistic + 4x likely + pessimistic) / 6, and function/use-case point analysis.

Test effort factors: product risk, complexity, size, required coverage, process maturity, team skill, and tool support.

Monitoring compares actual vs. planned: test case execution progress, defect discovery rate, coverage achieved, effort spent, and schedule variance.

Control actions when off-plan: re-prioritize test cases, adjust scope, add/reallocate resources, escalate risks, or revise exit criteria with stakeholders.

Common metrics: test case execution percentage, pass/fail rate, defect density (defects per size/function), defect detection percentage (DDP = defects found in test / total defects found), and defect removal efficiency.

Defect detection percentage (DDP) = defects found by a given test level / total defects found by that level and later phases x 100%.

Test progress report: periodic, factual status; test summary report: end-of-level/project, includes assessment against exit criteria and residual risk.

Earned value application: planned value vs. earned value vs. actual cost; schedule performance index (SPI) = EV/PV, cost performance index (CPI) = EV/AC.

Stakeholder categories: business/product owners, developers, operations, end users, regulators, and external suppliers; each has different information needs and influence.

RACI matrix assigns Responsibility, Accountability, Consultation, and Information rights for test activities and deliverables.

Product risk = possibility that a product characteristic fails to meet stakeholder needs; project risk = possibility that the project fails to meet its objectives (schedule, budget, resources).

Risk analysis = risk identification + risk assessment (likelihood x impact); risk control = risk mitigation, contingency, transfer, and acceptance.

Risk-based testing process: identify risks, assess and prioritize, select test conditions/techniques, execute highest-risk first, monitor risk as it changes.

PRAM (Pragmatic Risk Analysis and Management) and risk matrices are common frameworks for assigning risk levels and owners.

Defect management lifecycle: new -> assigned -> open -> fixed -> retest -> closed, with reopen and reject/defer branches; each transition is logged with an audit trail.

Defect report essential fields: ID, summary, environment/build, steps to reproduce, expected vs. actual result, severity, priority, status, reporter, assignee.

Severity (impact on the system) and priority (urgency of fix) are independent; a low-severity cosmetic defect can be high priority for a demo or release.

Defect triage meeting participants: test manager/leader, development lead, product owner; decisions include fix now, defer, reject (not a defect), or duplicate.

Organizational test strategy = generic, long-lived, reusable across projects; test approach = project-specific adaptation of that strategy, documented in the test plan.

ISTQB distinguishes strategy content by: test levels, test types, entry/exit criteria, test techniques, independence level, and test environment/automation policies.

Test approach selection drivers: risk level, business domain criticality, contractual/regulatory constraints, SDLC model, team skill, tool availability, time-to-market pressure.

Sequential (V-model, waterfall) favors early detailed test planning and formal gate reviews; iterative/incremental shifts planning to per-iteration level with regression emphasis.

Agile test approach characteristics: whole-team quality ownership, test-first (ATDD/TDD), lightweight documentation, continuous regression via automation.

Risk-based approach: prioritize test effort by risk exposure (likelihood x impact); highest-risk items get most rigorous techniques and earliest execution.

Methodical approach: follows a predefined set of test conditions (e.g., checklists, standards compliance) without formal risk analysis.

Reactive approach: testing driven by defects found and exploratory/ad-hoc investigation rather than pre-planned conditions; suited to poorly documented or unstable specs.

Consultative approach: test coverage guided by input from stakeholders/users rather than internal risk or formal models.

Test roles per ISTQB: test manager (planning, monitoring, control, reporting), test leader (level/phase coordination), tester (analysis, design, execution, reporting).

Skill categories: testing-specific (techniques, tools), domain knowledge (business/technology), and soft skills (communication, analytical, diplomatic reporting).

TMMi and CTP (Certified Tester Professional) describe maturity/competency growth paths; TPI Next uses maturity levels per key area for process improvement.

Independence levels (low to high): author tests own code, tests by teammates in same team, tests by independent testers in same org, tests by external/outsourced testers.

Higher independence reduces author bias but can reduce information sharing and slow feedback; choice depends on risk and domain criticality.

Motivation factors (Herzberg-style application): recognition, challenging work, career path, adequate tools; hygiene issues such as poor environment erode motivation.

Team composition decisions: ratio of testers to developers, skill mix (automation vs. manual/exploratory), location (co-located vs. distributed), and outsourcing scope.

Competency gap analysis: compare required skills per role against current skills; close gaps via training, mentoring, pairing, or recruitment.

Onboarding a new tester requires: domain overview, test process/strategy documents, tool access, and a supervised first assignment.

Test process groups (ISTQB): planning, monitoring & control, analysis, design, implementation, execution, completion - activities overlap and are iterative.

Entry criteria gate the start of a test level (e.g., build available, smoke test passed, test data ready); exit criteria gate completion (e.g., coverage threshold, defect closure rate).

In sequential models, test levels map to development phases; in iterative models, all levels may occur within each iteration (shift-left).

Shift-left: static analysis, reviews, and early test design reduce defect cost; shift-right: production monitoring, A/B testing, and operational feedback.

Continuous integration/continuous delivery requires automated regression suites, version-controlled testware, and fast feedback loops.

Regression testing scope grows with each increment; select tests by change impact and risk rather than rerunning everything blindly.

Maintenance testing triggers: perfective (improvements), corrective (defects), adaptive (environment changes), preventive (refactoring/technical debt).

Test completion activities: archive testware for reuse, hand over known defects and residual risk, capture lessons learned, release resources.

DevOps/Agile: test manager role shifts toward enabling quality culture, cross-functional team coaching, and cross-team coordination of test environments and data.

Test plan contents (IEEE 829 / ISO 29119-aligned): scope, objectives, approach, entry/exit criteria, schedule, resources, risks, deliverables, environment, and metrics.

Estimation techniques: expert judgment, analogy (similar past projects), work breakdown structure, three-point estimation (optimistic + 4x likely + pessimistic) / 6, and function/use-case point analysis.

Test effort factors: product risk, complexity, size, required coverage, process maturity, team skill, and tool support.

Monitoring compares actual vs. planned: test case execution progress, defect discovery rate, coverage achieved, effort spent, and schedule variance.

Control actions when off-plan: re-prioritize test cases, adjust scope, add/reallocate resources, escalate risks, or revise exit criteria with stakeholders.

Common metrics: test case execution percentage, pass/fail rate, defect density (defects per size/function), defect detection percentage (DDP = defects found in test / total defects found), and defect removal efficiency.

Defect detection percentage (DDP) = defects found by a given test level / total defects found by that level and later phases x 100%.

Test progress report: periodic, factual status; test summary report: end-of-level/project, includes assessment against exit criteria and residual risk.

Earned value application: planned value vs. earned value vs. actual cost; schedule performance index (SPI) = EV/PV, cost performance index (CPI) = EV/AC.

Stakeholder categories: business/product owners, developers, operations, end users, regulators, and external suppliers; each has different information needs and influence.

RACI matrix assigns Responsibility, Accountability, Consultation, and Information rights for test activities and deliverables.

Product risk = possibility that a product characteristic fails to meet stakeholder needs; project risk = possibility that the project fails to meet its objectives (schedule, budget, resources).

Risk analysis = risk identification + risk assessment (likelihood x impact); risk control = risk mitigation, contingency, transfer, and acceptance.

Risk-based testing process: identify risks, assess and prioritize, select test conditions/techniques, execute highest-risk first, monitor risk as it changes.

PRAM (Pragmatic Risk Analysis and Management) and risk matrices are common frameworks for assigning risk levels and owners.

Defect management lifecycle: new -> assigned -> open -> fixed -> retest -> closed, with reopen and reject/defer branches; each transition is logged with an audit trail.

Defect report essential fields: ID, summary, environment/build, steps to reproduce, expected vs. actual result, severity, priority, status, reporter, assignee.

Severity (impact on the system) and priority (urgency of fix) are independent; a low-severity cosmetic defect can be high priority for a demo or release.

Defect triage meeting participants: test manager/leader, development lead, product owner; decisions include fix now, defer, reject (not a defect), or duplicate.