CTAL-TTA — Advanced Technical Test Analyst (v4.0)

CTAL-TTA — Advanced Technical Test Analyst (v4.0) glossary

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

#

100% Statement Coverage Does Not Imply 100% Branch Coverage(100% statement coverage does not imply 100% branch coverage): A key fact that a test suite can achieve full statement coverage without covering all branches, making it a weak criterion.

A

Atomic Condition(atomic condition): A condition in a decision that cannot be further broken down into simpler conditions.
Availability(availability): The sub-characteristic of reliability indicating the degree to which the system is operational and accessible when required.

B

Boundary Value Analysis(boundary value analysis): Test technique that tests input values at the boundaries of valid ranges.
Branch Coverage(branch coverage): A stronger coverage criterion than statement coverage that requires every branch (true and false) to be taken.

C

CI/CD Pipeline Integration(ci/cd pipeline integration, integration into ci/cd): The process of incorporating a testing tool into the continuous integration and delivery pipeline to automate testing.
Code Metrics(code metrics, code metric, cyclomatic complexity, coupling): Measurable attributes of code such as complexity and coupling, assessed by static analysis tools.
Coding Standard Enforcement(coding standard enforcement): Type of static analysis that checks source code adherence to defined coding standards.
Coding Standards(coding standards, misra, cert, coding standard): Predefined rules and guidelines (e.g., MISRA, CERT) that static analysis enforces to ensure code quality and safety.
Compound Conditions(compound conditions): Conditions composed of multiple sub-conditions combined with logical operators like AND or OR.
Condition: A boolean expression that cannot be broken down into simpler boolean sub-expressions.
Condition Coverage(condition coverage): A structural coverage metric measuring whether each atomic condition in a decision has been evaluated to both true and false.
Configuration Drift(configuration drift): A gradual, unplanned change in environment configuration over time, causing tests to fail due to inconsistencies.
Containerization(containerization, docker): A technique using containers (e.g., Docker) to provision isolated, reproducible test environments on demand.
Context-Dependent Decision Making(context-dependent): The principle that in ISTQB, statements like 'X is better than Y' are usually not universal but depend on context.
Context-Dependent Technique Selection(context-dependent decision making): The principle that the choice of testing technique depends on project context and domain.
Control Flow Analysis(control flow analysis): Type of static analysis that examines the flow of control in source code.
Control Flow Defect(control flow defects): A defect in program paths, such as unreachable code or infinite loops.
Control Flow Defects(control flow defects): Defects in program flow such as unreachable code, infinite loops, and incorrect loop termination.
Control Flow Graph(control flow graph, cfg): A graphical representation of a program's control flow where nodes represent basic blocks and edges represent control flow.
Coverage Criteria(coverage criteria, mc/dc, test coverage criterion, coverage criterion): A measure used in white-box testing to indicate the extent of code exercised, such as MC/DC.
Coverage criteria subsumption(stronger coverage criteria subsume weaker ones): The property that stronger coverage criteria encompass weaker ones.
Cyclomatic complexity(cyclomatic complexity): A metric indicating code complexity, used to assign risk levels for testing.

D

Data Flow Analysis(data flow analysis): Type of static analysis that examines data usage and flow in source code.
Data Flow Anomaly(data flow anomaly, data flow anomalies): An abnormal sequence of variable states (defined, used, killed) indicating potential bugs or dead code.
Data Flow Defects(data flow defects): Defects in data usage including uninitialized variables, unused variables, and incorrect pointer usage.
Data Generation Tools(data generators): Software tools that create, generate, or populate test data at runtime to reduce dependencies on static datasets.
Data Masking(data masking): The process of obfuscating sensitive data in test datasets to comply with privacy regulations like GDPR.
Data-Driven Testing(data-driven approach): An approach where test logic is separated from test data, allowing the same script to run with multiple data sets.
Dead Code(dead code, unreachable code): Unreachable code that should be excluded from the total count of statements when calculating coverage.
Decision Condition Testing(condition coverage): A structural coverage criterion requiring each atomic condition in a decision to be evaluated to both true and false.
Decision Coverage(decision coverage, branch coverage): A structural coverage metric requiring every decision outcome (e.g., true/false) to be taken at least once; also called branch coverage.
Decision Testing(branch coverage): A structural coverage criterion requiring the overall outcome of a decision to be both true and false.
Distinction Between Technical and Project Risks(technical vs project risks): The separation of product risks related to technology quality from management, scheduling, or resource risks.
Dynamic analysis(dynamic analysis): A technique that analyzes software behavior during execution to identify defects.
d-d Anomaly(d-d, d-d anomaly): A data flow anomaly where a variable is defined twice without an intervening use.
d-u Anomaly(d-u, d-u anomaly): A data flow anomaly where a variable is defined but never used.

E

Early Defect Detection(early defect detection): Benefit of static analysis that finds defects early in the development lifecycle.
Environment Contention(environment contention): A challenge where multiple teams share the same test environment, leading to conflicts and unreliable test results.
Exponential Test Case Growth(exponential number of test cases, exponential growth): The property that multiple condition coverage requires 2^n test cases for n conditions, making it impractical for large n.

F

Failure Mode and Effects Analysis(fmea, failure mode and effects analysis): A systematic technique used to identify potential failure modes and their effects on system quality.
Failure rate(failure rate): A reliability metric indicating the frequency with which a system fails over a given period.
False Positive(false positives): An irrelevant or incorrect warning generated by a static analysis tool.
False Positives (Static Analysis)(false positives): Reported defects in static analysis that are not actual defects, requiring human triage to avoid wasted effort.
False positive (static analysis)(false positives): A static analysis alert that incorrectly flags a code section as containing a defect.
Fault tolerance(fault tolerance): The sub-characteristic of reliability that enables the system to maintain operation in the event of faults.

G

Garbage Collection Logging(garbage collection logging): A dynamic analysis technique that analyzes GC logs to identify objects persisting across collections.

H

Hazard Analysis(hazard analysis): A risk identification technique that focuses on hazards that could lead to system failures, especially in safety-critical systems.
Heap Profiling(heap profiling): A dynamic analysis technique that records allocations and deallocations to find unreleased memory blocks.

I

ISO 25010 quality model(iso 25010, iso 25010 model, iso 25010 quality model): A standard quality model that defines software quality characteristics and subcharacteristics.
ISTQB Glossary(istqb glossary): Authoritative source of precise definitions for testing terms used in ISTQB exams.
Infinite Loop(infinite loops): A loop that never terminates due to a missing or incorrect exit condition.
Infrastructure as Code(infrastructure-as-code, iac): A strategy to define and provision test environments declaratively using version-controlled configuration files.
Integration of Static Analysis(integration of static analysis): The practice of embedding static analysis into development processes like continuous integration for early and frequent defect detection.
Inter-procedural Analysis(inter-procedural analysis): Data flow analysis performed across function calls, more comprehensive but computationally expensive.

L

Line Coverage(line coverage): A metric often confused with statement coverage, measuring lines of code executed rather than statements.
Load Testing(load testing): Test technique that evaluates system behavior under normal and peak load conditions.

M

MC/DC(modified condition/decision coverage, mc/dc): A coverage criterion that ensures each condition independently affects the decision outcome.
Manual Fallback Process(fallback manual process): A contingency process using manual testing to reduce impact of tool failures.
Maturity(maturity): The sub-characteristic of reliability that denotes the system's ability to avoid failure under normal operation.
Mean time between failures (MTBF)(mean time between failures, mtbf): A reliability metric measuring the average time between system failures.
Mean time to repair (MTTR)(mean time to repair, mttr): A reliability metric measuring the average time required to restore a system after a failure.
Memory Leak(memory leak): A type of resource leak that occurs when a program incorrectly manages memory, failing to release memory no longer needed.
Modified Condition/Decision Coverage(modified condition/decision coverage, mc/dc): A rigorous coverage criterion requiring every condition in a decision to independently affect the decision outcome.
Modified Condition/Decision Coverage (MC/DC)(modified condition/decision coverage, mc/dc): White-box test technique that achieves high code coverage by testing all conditions and decisions.
Multiple Condition Testing(multiple condition testing, multiple condition coverage): A test coverage criterion requiring every combination of true/false values for each atomic condition in a decision to be executed at least once.
Multiple-Condition Coverage(multiple-condition coverage): A structural coverage metric requiring all possible combinations of atomic condition outcomes to be tested.

N

Negative Testing(negative testing): Test technique that checks system behavior with invalid or unexpected inputs.
Nested Decisions(nested decisions): Decisions that appear inside the true or false branches of another decision.

O

Operational profiling(operational profiling): A reliability testing technique that simulates real-world usage to uncover failure patterns.
Over-Reliance on Tools(over-reliance): A risk where dependence on a single tool creates blind spots or single points of failure.

P

Path coverage(path coverage): A stronger coverage criterion than MC/DC that ensures all paths are tested.
Project Risk(project risk): A risk that concerns the management of the project, such as resource or scheduling issues.
Proof-of-Concept Evaluation(proof-of-concept, poc): A practical assessment of a tool against specific organizational requirements to validate its effectiveness before full-scale adoption.
Proof-of-Concept Trial(proof-of-concept trials): A preliminary evaluation of a tool in a realistic context before acquisition.

Q

Quality Characteristics for Technical Testing(quality characteristics for technical testing): Attributes such as reliability, performance, and security evaluated during technical testing.

R

Recoverability(recoverability): The sub-characteristic of reliability that describes the ability to restore the system after a failure.
Recovery testing(recovery testing): A reliability testing method that verifies the system can restore itself after a crash.
Reference Counting(reference counting): A dynamic analysis technique that tracks references to detect objects that are no longer reachable.
Reliability(reliability): The ability of a component or system to perform required functions under stated conditions for a specified period of time.
Residual Risks(residual risks): Risks that remain after mitigation efforts; they must be communicated to stakeholders.
Reviews(reviews): Static testing techniques where work products are examined by people to find defects.
Risk Likelihood and Impact Assessment(likelihood and impact assessment): The process of evaluating each identified risk based on its probability of occurrence and potential consequences to prioritize testing efforts.
Risk Priority Number(rpn, risk priority number): A numeric score derived from severity, occurrence, and detection ratings to prioritize failure modes in FMEA.
Risk-Based Testing(risk-based testing, risk-based testing approach): Testing approach that prioritizes tests based on risk analysis to reduce risks to an acceptable level.
Risk-based prioritization(risk-based prioritization): Prioritizing testing of high-risk code sections based on risk assessment.

S

Safety-Critical Systems(safety-critical systems): Systems where failure could result in loss of life, significant property damage, or environmental harm, often requiring stronger coverage criteria.
Security Vulnerabilities (Static Analysis)(security vulnerabilities): Security weaknesses detectable by static analysis such as buffer overflows, SQL injection, and XSS.
Security Vulnerability Detection(security vulnerabilities): Static analysis technique that identifies security flaws like buffer overflows or SQL injection.
Severity vs. Priority(severity vs. priority, severity, priority): A pair of closely-related concepts often confused; severity measures impact, priority measures urgency.
Short-Circuit Evaluation(short-circuit evaluation): An evaluation technique where a boolean expression stops evaluating as soon as the final result is determined.
Short-Circuit Operator(short-circuit operator): A logical operator that may skip evaluating a condition if the result is determined by the first operand, potentially leaving conditions uncovered.
Statement Coverage(statement coverage): A structural coverage metric requiring every executable statement in source code to be executed at least once.
Statement Testing(statement testing): A white-box testing technique that aims to execute every executable statement at least once.
Static Analysis Tool(static analysis tools): A tool that performs data flow analysis by parsing source code and building a data flow graph.
Static Analysis Tools(static analysis tools, static analysis): Tools that scan source code for potential defects without executing the program.
Static Analysis vs Dynamic Analysis(static analysis vs dynamic analysis): Complementary testing approaches: static analysis examines code without execution, while dynamic analysis tests runtime behavior.
Static analysis(static analysis, static analysis techniques): A technique that analyzes source code without executing it to find defects.
Static and Dynamic Analysis(static and dynamic analysis): Analysis techniques that examine software without executing it (static) or during execution (dynamic).
Stress Testing(stress testing): Test technique that evaluates system stability under extreme or overload conditions.
Structural Coverage Criterion: A testing metric based on code structure, defining what parts of the code must be exercised by tests.
Structural Defects(structural defects): Defects related to code structure like excessive complexity, deep nesting, and high coupling.
Subsumption of Coverage Criteria(subsumption, coverage subsumption): The property that achieving a stronger coverage criterion implies satisfaction of a weaker one, e.g., decision coverage subsumes statement coverage.
Synthetic Data Generation(synthetic data generation): The creation of artificial test data that mimics real data but contains no sensitive information.

T

Technical Review(technical review, technical reviews): A formal or informal meeting where technical artifacts like code and architecture are examined.
Technical Risks(technical risks, technical risk): Risks related to technology used in the system, such as performance, security, or reliability issues.
Technical Test Analyst(tta, technical test analyst role, technical test analyst): A role focused on identifying technical risks by analyzing system architecture, design, and technology stack.
Technical Test Analyst (TTA)(technical test analyst, tta): Role responsible for identifying technical risks and proposing mitigation actions through technical testing.
Technical Testing Tool(testing tool, technical testing tool): A software tool that supports testing activities such as static analysis, dynamic analysis, performance testing, or security testing.
Technical risk assessment(technical risk assessment): Evaluation of technical risks based on likelihood and impact to prioritize testing.
Technology Stack Compatibility(technology stack compatibility, tool fit): The degree to which a testing tool aligns with an organization's existing technology stack and environments.
Test Case Derivation from CFG(deriving test cases from control flow graphs): The process of selecting input values that cause each node in a control flow graph to be executed, covering all paths for 100% statement coverage.
Test Case Derivation from Control Flow Graph(test case derivation, deriving test cases from control flow graphs): The process of creating test cases corresponding to paths through a control flow graph to achieve coverage.
Test Data Management for Automation(test data management for automation): The practice of creating, managing, and maintaining test data to ensure repeatability and independence of automated tests.
Test Environment Management for Automation(test environment management for automation): The practice of setting up and maintaining stable, consistent, and reproducible test environments for automated tests.
Test Level(test level): The scope of testing, such as unit, integration, or system level.
Test Level vs. Test Type(test level vs. test type): A pair of closely-related concepts; test level refers to scope like unit or system, test type refers to objective like functional or performance.
Test Manager vs. Test Management Role(test manager vs. test management role): A pair of role names that are easily confused; test manager is a specific job title, test management role is a broader responsibility.
Test Tool Risks(risks associated with test tools, tool risks): Risks introduced by using test tools, including incorrect results, over-reliance, and vendor lock-in.
Test Tools and Automation(test tools and automation): Software tools and automated scripts used to support test activities and execution.
Test Type(test type): The objective of testing, such as functional or non-functional testing.
Tool Misconfiguration(misconfiguration): A risk causing incorrect test results due to improper tool setup.
Tool Obsolescence(tool obsolescence): A risk that a test tool becomes outdated or unsupported over time.
Tool Selection Process(tool selection process, selection process): A structured procedure for choosing a testing tool, involving requirements identification, research, proof-of-concept, and final recommendation.
Total Cost of Ownership(total cost of ownership, tco): The complete cost of a tool over its lifecycle, including licensing, training, and maintenance.

U

Unreachable Code(unreachable code): Code that can never be executed due to control flow constraints.
u-d Anomaly(u-d, u-d anomaly): A data flow anomaly where a variable is used before it is defined.

V

Validation(validation): Process of checking that the right product is built, often via dynamic analysis.
Validation vs. Verification(validation vs. verification): A pair of closely-related concepts; verification checks conformance to specifications, validation checks fitness for use.
Vendor Lock-In(vendor lock-in): A risk of becoming dependent on a vendor's proprietary technology or services.
Verification(verification): Process of checking that a product is built correctly, often via static analysis.
Verification vs Validation(verification, validation): Distinct processes where verification checks correctness against specifications and validation checks user needs.

W

White-Box Testing Tool(white-box testing tool): A testing tool that supports structural testing techniques and coverage criteria like MC/DC for specific programming languages.
White-box testing(white-box testing, white-box test techniques): A test technique that uses internal knowledge of the code structure to design test cases.