CTEL-TM-SM — Strategic Test Management glossary

116 terms the exam expects you to know, defined in plain language.

A

Acceptance Criteria(acceptance criteria): Predefined standards that deliverables must meet for formal acceptance in a testing contract.
Alignment of Test Environments, Tools, and Data Management(alignment of test environments and tools): The coordination and integration of testing infrastructure and data practices between an organization and a third-party testing team.
Alignment with Test Policy and Strategy(alignment with test policy): Ensuring external testing expectations are consistent with organizational test standards.
Analytical test strategy(analytical strategy, analytical strategy families, analytical): A family of test strategies that derive test conditions from systematic analysis of the test basis, risks, or models.
Audience-Specific Test Reporting(tailor the level of detail to the audience): Tailoring the level of detail in reports to match the needs of executives or technical teams.

B

Business Objectives(business objectives): The overarching goals of the organization that the test mission must align with to ensure effective testing.

C

Change Control(change control): A formal process to document and resolve deviations found during verification audits, including impact analysis and resolution.
Change management(change management): A systematic approach to managing changes in an integration project to minimize disruptions.
Change management in integration(change management): A structured approach to managing transitions of integration systems, including communication and training.
Common Challenges in Third-Party Test Strategy Merging(challenges in merging test strategies): Differences in terminology, process maturity, and tool proficiency that arise when merging test strategies with external organizations.
Common Mis-Recalls in ISTQB(common mis-recalls): Frequent errors in ISTQB exams include reversing process order, confusing similar role names, and ignoring context.
Communication Channels and Escalation Paths(communication channels, escalation paths): Established methods and procedures for reporting, issue escalation, and regular interactions with external sources.
Conflict Escalation Process for External Testing(escalation process): A predefined procedure with neutral mediation to resolve disputes between internal teams and external testing services.
Context-Dependent Answers in ISTQB(context-dependent answers): ISTQB exam answers often depend on the specific context described, avoiding universal 'X is better than Y' statements.
Context-Driven Test Strategy Selection(strategy selection): The process of choosing test strategies based on project-specific factors such as risks, resources, and lifecycle model.
Contingency Planning(contingency planning, contingency plans): Predefined plans to address potential failures or deviations by external sources.
Continuous Regression(continuous regression, continuous regression testing): The practice of performing regression tests repeatedly throughout iterative development.
Contractual Agreements for Testing(contractual agreements, contracts): Legal contracts that define the scope of testing, acceptance criteria, and quality metrics between an organization and a third-party test provider.
Core Competency of Managing External Relationships(managing external relationships): A defined competency for test managers involving the merging of test strategies with third-party organizations as per ISTQB syllabus.
Cultural Differences in External Testing Collaboration(cultural differences): Organizational cultural variations that affect communication and collaboration when working with third-party test providers.
Cultural Sensitivity in Global Testing Communication(cultural differences): Awareness of cultural differences that affect communication style and interpretation when working with global external parties.
Cultural and Language Differences(cultural differences, language differences): Potential communication barriers requiring translation or liaison roles to ensure effective collaboration.
Cumulative Regression Risk(regression risk): The increasing defect risk from changes across multiple increments that requires systematic regression testing.

D

Defect Detection Percentage (DDP)(defect detection percentage): A metric that measures the percentage of defects found during testing relative to total defects.
Detailed Iteration Plan(detailed iteration plans): A specific plan for each iteration or release, containing test cases, assignments, and timelines.
Dispute Resolution Mechanism(dispute resolution): Processes like escalation paths or arbitration specified in a contract to resolve disagreements.

E

Expectation Management in External Testing(managing expectations): Setting realistic deliverables, quality levels, and timelines to align internal and external stakeholders.
External Source (ISTQB)(external source): An organization or individual that provides testing services or products outside the organization's direct control.
External Testing Alignment: Ensuring external testing activities conform to the organization's test policy and strategy via contracts.
External Testing Communication Plan(communication plan, escalation plan): Defined escalation and resolution procedure for quality issues from external parties.
External Testing Communication Protocols(communication channels and protocols): Agreed-upon channels, frequency, and formats for communication with external testing parties, documented in the test plan.
External Testing Contract Requirements(contract requirements, sla quality criteria, external testing contract requirements): Documented quality criteria and acceptance thresholds in an agreement with an external test party.

F

Fallback planning in integration(fallback planning): The process of designing alternative procedures to revert to a stable state if integration fails.
Flexible Test Strategy(adaptive testing strategy): A test strategy that accommodates evolving requirements and frequent changes in iterative development.
Formal Change Control(change control): A defined process for managing deviations from agreed plans, established before contract signing.
Formal Change Control for Deviations(change control process): Documented process to handle and resolve deviations found during external verification.

G

Go/No-Go Decision(go/no-go decisions): A binary decision point that determines whether to proceed with or abandon a project, phase, or activity based on predefined criteria.
Governance in integration(governance): The set of policies and processes ensuring integration projects align with objectives and compliance.

H

Heuristic Strategy(heuristic): A test strategy family that relies on heuristics, exploratory testing, and tester experience to guide test design.
Hybrid Model(hybrid models, hybrid lifecycle model, hybrid model): A software development lifecycle that combines sequential and iterative phases.
Hybrid model interface risk(interface risk): Risk of defects being introduced at the integration points between sequential and iterative phases.

I

ISTQB strategy families(seven strategy families, istqb test strategy families, strategy families): Seven categories of test strategies: analytical, model-based, methodical, process-compliant, dynamic, heuristic, and consultative.
Indemnification Clause(indemnification): A contractual provision that protects one party from losses caused by the other party's actions.
Independent Verification of External Results(independent verification, independent check): Separate validation of critical external deliverables like security or performance test results.
Independent Verification of Test Results(independent verification): The practice of having a separate party verify critical test results to ensure accuracy and impartiality, especially for safety-critical systems.
Integration Framework(integration framework): A defined structure specifying scope of work, quality criteria, and acceptance procedures for engaging external sources.
Integration Point(integration points): The interface between different lifecycle phases where defects are often introduced.
Integration Testing Coordination(integration testing coordination): Coordination of test environments, data, and schedules between systems developed by different parties.
Integration of External Defect Reports(merging defect reports): Process of merging defect data from external testing into the overall test management framework.
Integration of Test Artifacts(test artifacts integration, exchange of test artifacts): The exchange and integration of test cases, defect reports, and other testing outputs into the organization's systems when working with a third party.
Intellectual Property Rights for Test Artifacts(ip rights for test artifacts): Explicit assignment of ownership for test cases and automation scripts in a contract to prevent disputes.
Intellectual Property and Data Security(intellectual property concerns, data security): Protection of IP and data through contracts, NDAs, and security measures when engaging external sources.
Iteration Backlog Coordination(test manager coordination): Coordination between test manager, development, and product owners to ensure test results influence the next iteration's backlog.
Iterative Risk Reassessment(risk reassessment, continuous risk management, iterative risk reassessment): The practice of reevaluating risks at the start of each development cycle and adjusting test priorities.
Iterative Test Reporting(test dashboards, iteration feedback): Providing timely feedback to stakeholders after each iteration using dashboards with progress, defect trends, and risk status.

L

Limitation of Liability(liability limit): A contract clause capping the amount one party must pay the other for damages.

M

Master Test Plan(master test plan): A high-level plan that defines the overall scope, resources, schedule, and risks for the entire project.
Maturity-Based Oversight Adjustment: Adapting the level of supervision on external testing based on the assessed maturity of the provider.
Merging Test Strategies with Third-Party Organizations(merging test strategies with third-party organizations): The process of aligning and integrating an external organization's test strategy with the overall organizational test strategy through negotiation and contractual agreements.
Methodical Strategy(methodical): A test strategy family that uses predefined test conditions such as checklists, classification trees, or quality characteristics.
Metrics of success(metrics of success): Quantitative measures used to evaluate whether testing goals have been met, such as coverage percentage and defect detection rate.
Milestone-Based Test Planning(milestone-based test planning): A test planning approach for sequential phases using major milestones as checkpoints.
Model-based testing(model-based testing): An analytical test strategy that uses formal or semi-formal models of the system to generate test cases automatically or semi-automatically.
Multi-Level Test Planning(master test plan, iteration test plans, multi-level test planning): A test planning approach with a high-level master plan covering the entire project and detailed plans for each iteration.

P

Payment Model(payment models): Contractual basis for compensation, e.g., fixed-price or time-and-materials, affecting risk and flexibility.
Phase-End Review(phase-end reviews): A review conducted at the conclusion of a sequential phase to assess completion.
Phase-Gate Report(phase-gate reports, phase-gate reporting): A report summarizing progress and quality at the end of a sequential phase.
Priority(priority): An attribute of a defect that indicates the urgency of its resolution.
Project Risk Profile(project risks): The set of risks and their severity that influences the choice and mix of test strategies.

Q

Quality Acceptance Thresholds(acceptance thresholds, quality criteria, quality acceptance threshold, quality acceptance thresholds): Specific metrics such as defect density and test coverage that external deliverables must meet.
Quality Policy(quality policy): An organization's overall intentions and direction regarding quality, from which the test mission is derived.
Quality and Performance Metrics(quality metrics, performance metrics): Measurable indicators such as defect detection percentage, test coverage, and schedule adherence for vendor evaluation.

R

Reactive strategy(reactive strategy, reactive strategies): A test strategy where test design, execution, and prioritization are driven by discoveries during testing or external triggers such as production failures.
Real-time KPI reporting(real-time kpi reporting): The ability to display key performance indicators immediately as data is processed for timely decisions.
Regression Test Automation(automated regression suites, regression test automation): The use of automated test suites to execute regression tests efficiently across iterations.
Requirements-based testing(requirements-based testing): An analytical test strategy that derives test cases directly from functional and non-functional requirements.
Risk Allocation(risk allocation): Contractual distribution of liability for defects after release, IP rights, and confidentiality between parties.
Risk Management for External Sources(risk management): Assessment of external party capability, financial stability, and compliance to mitigate integration risks.
Risk Reassessment in Testing(risk reassessment): Periodic review of risks each cycle to keep test priorities aligned with current threats.
Risk-based testing(risk-based testing): An analytical test strategy where test efforts are prioritized according to the likelihood and impact of failure.

S

Safety-critical system(safety-critical systems): A system where risk analysis is mandatory, making risk-based testing particularly well-suited.
Security and Confidentiality in Third-Party Testing(security and confidentiality): The need to protect sensitive data and environments when sharing them with external testing organizations.
Service Level Agreement(sla, slas): A formal agreement between a service provider and customer defining the expected level of service.
Severity(severity): An attribute of a defect that indicates its impact on the system.
Severity and Priority(severity vs. priority): Two distinct attributes of a defect: severity measures impact on the system, priority measures urgency for fixing.
Sprint-Based Dashboard(sprint-based dashboards): A visual display of test metrics and progress for each Agile iteration.
Standardized Test Reporting Templates(standardized reporting templates): Predefined formats for test progress reports and defect summaries tailored to different stakeholder audiences.
Strategy Compatibility(compatibility of strategies): The degree to which different test strategies can be effectively combined without conflict, such as scripted versus exploratory approaches.

T

Test Automation Maintenance(script maintenance, fragile scripts, test automation maintenance): The ongoing effort to keep test scripts robust and prevent fragility that can become a bottleneck.
Test Environment Provisioning(test environment): The contractual specification of responsibilities for setting up and maintaining test environments.
Test Goals(test goals, goals, test goal, testing goal): Specific, measurable objectives that support the test strategy, such as achieving a target code coverage percentage.
Test Independence(test independence): The degree of separation between test and development roles, as mandated by the test policy.
Test Level(test levels): A group of testing activities organized in a hierarchy, e.g., unit, integration, system.
Test Level and Test Type(test level vs. test type): Test level refers to the stage of testing (e.g., unit, integration), test type refers to the objective (e.g., functional, performance).
Test Maturity Level Adjustment(maturity level adjustment, test maturity level adjustment): Adaptation of verification rigor based on the external party's testing maturity.
Test Mission(test mission, mission): A high-level statement describing the purpose and scope of testing within an organization, derived from the quality policy and business goals.
Test Mission and Goals(test mission, test goals): The overarching purpose and specific objectives that the test strategy must align with and support.
Test Plan(test plan): A document that specifies the scope, approach, resources, and schedule for testing activities.
Test Policy(test policy, organizational policy, policy): A high-level document that defines the principles and approach to testing across the organization.
Test Policy and Strategy Alignment(alignment with test policy and strategy): The requirement that external testing adhere to the organization's established test policy and strategy, ensuring consistency.
Test Strategy(test strategy, strategy): A concrete plan for a specific project that translates the test policy into details such as test levels, techniques, and resources.
Test Strategy Alignment(test strategy alignment): The compatibility of an external party's test strategy with the organization's test policy and goals.
Test Strategy Document(test strategy document): A key output of the test planning process that documents the selected test strategies and their combination.
Test Type(test types): A category of testing focused on specific quality characteristics, e.g., functional, performance, security.
Test artifact traceability(traceability): Ability to link test artifacts across lifecycle components to ensure consistency.
Test strategy family(strategy families, test strategy families): A category of test approaches such as analytical, process-compliant, or dynamic, used to address different project contexts.
Testing Deliverable(testing deliverables): A tangible output of testing, such as test plans, test cases, defect reports, and summary reports.
Testing Deliverables(deliverables): Tangible outputs like test plans, test cases, defect reports, and summary reports defined in a contract.
Testing Scope Definition(testing scope): The specification of test levels, test types, and quality characteristics covered in a contract to avoid ambiguity.
Tool Chain Compatibility(tool chain compatibility): Ensuring compatible tools or defined data exchange formats between the organization and external sources.
Transition Period for Third-Party Onboarding(transition period, onboarding period): A planned period during which a third-party testing team is onboarded and their processes are adapted to the organization's quality management system.

V

Validation(validation): A process that checks if the product meets user needs, ensuring the correct product is built.
Validation and Verification(validation vs. verification, verification): Verification checks if the product meets specifications, validation checks if it meets user needs.
Verification Audits(verification audits): Scheduled assessments to evaluate compliance with the test plan and quality of results from external testing.
Verification Audits and Milestone Reviews(audits, milestone reviews): Scheduled assessments to evaluate external party compliance with test plans and results.

W

Written Confirmation of Agreements(document all agreements): Documenting critical decisions and agreements in writing to prevent misunderstandings with external parties.