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

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

A

Acceptance Criteria for Quality Characteristics(acceptance criteria for quality characteristics, non-functional acceptance criteria): Objective, repeatable conditions defining pass/fail for non-functional attributes, including measurement method and thresholds.
Acceptance criteria(acceptance criteria): Conditions that a user story must satisfy to be accepted by the product owner.
Acceptance criteria-based testing(acceptance criteria-based testing): Deriving test cases directly from each acceptance criterion to ensure every condition is verified.
Action Entry(action entries): The part of a decision table indicating which actions occur for each condition combination.
Ad Hoc Review(ad hoc review): An informal review technique without a structured process or predefined checklist.
All Classes Coverage(all classes): A coverage criterion that ensures each class appears in at least one test case.
All Combinations Coverage(all combinations): A coverage criterion requiring every column of the decision table to be tested.
All-pairs Algorithm(all-pairs algorithm): An algorithm used to generate the minimal set of test cases for pairwise testing.
Anomaly(anomaly): Any condition that deviates from expectation based on requirements, specifications, user documentation, or standards.

B

Black-Box Test Design Technique(black-box test design technique): A test design technique that bases test cases on specifications without accessing internal code structure.
Black-Box Test Techniques(black-box techniques, black-box test techniques, black-box test design technique): Test design techniques that derive test cases from an analysis of the specification without reference to internal structure.
Boundary Value(boundary value): A value at the edge of a domain, including on, just inside, and just outside the boundary.
Boundary Value Analysis(boundary value analysis): A black-box test technique that focuses on the boundaries between partitions.
Business Rules(business rules): Logical conditions where the outcome depends on multiple conditions, tested effectively with decision tables.

C

Checklist-Based Review(checklist-based review): A review technique that uses a predefined list of questions or criteria to guide examination.
Class(class, partition): A partition of a classification representing a specific value or group.
Class (Classification Tree)(class, classes): A disjoint and complete subset of a classification's domain, representing a specific value or range.
Classification(classification, input parameter): An input parameter or category partitioned into disjoint and complete classes.
Classification (in Test Design)(classification): An input parameter or category partitioned into disjoint and complete classes.
Classification Tree(classification tree, classification trees): A tree structure representing the input domain where branches are classifications and leaves are classes.
Classification Tree Method(classification tree method, ctm, classification tree): A black-box technique that uses a classification tree to partition test inputs and design test cases.
Classification Trees(classification trees, classification tree method): A combinatorial technique that uses a tree structure to represent partitions of the input domain and combines leaves from different trees to create test cases.
Co-existence(co-existence): A sub-characteristic of compatibility where a product performs functions efficiently while sharing resources without harmful impact.
Cognitive Walkthroughs(cognitive walkthroughs): A technique that evaluates a system's ease of learning by simulating a user's problem-solving process.
Combinatorial Testing(combinatorial techniques, combinatorial testing techniques): A testing approach that covers interactions between input parameters using techniques like pairwise, orthogonal arrays, and classification trees.
Compatibility(compatibility): A quality characteristic measuring the ability to exchange information or coexist with other products, systems, or components.
Compatibility Testing(compatibility testing): A type of non-functional testing that evaluates the degree to which a software product interacts with other products in a shared environment.
Condition Entry(condition entries): The part of a decision table containing true/false or specific values for each condition.
Constraint(constraints, constraint, dependency): Rule to exclude invalid or impossible combinations of classes.
Constraints(constraints): Rules that exclude invalid or impossible combinations of parameter values in test case generation.
Constraints in combinatorial testing: Rules that exclude invalid or impossible combinations of classes to keep test cases realistic.
Context-Dependent Best Practice in ISTQB(treating x is better than y as universal): A principle that ISTQB exam answers depend on context, so absolute statements like 'X is better than Y' are typically incorrect.
Coverage Criteria(coverage criteria, all classes, pairwise): Rules like 'all classes' or 'pairwise' to guide test case selection.

D

Decision Table(decision table): A matrix listing conditions and actions, with columns representing unique condition combinations.
Decision Table Testing(decision table testing): A black-box technique that uses a decision table to design test cases for combinations of conditions.
Defect Detection in Reviews(defect identification in reviews): The process of identifying issues in test basis documents, test cases, and other work products during reviews.
Defect Report(defect report): A documented record of a confirmed anomaly with details to enable effective resolution.
Defect Reporting(defect reporting, defect logging): The process of logging discrepancies with clear steps to reproduce and supporting evidence.
Defect Severity and Priority(severity, priority): Attributes assigned to a defect indicating its impact and urgency for resolution.
Defect Tracking System(defect tracking system): A tool used to manage and monitor defect reports throughout the testing lifecycle.
Defect management(defect management): Logging, tracking, and retesting defects found during an increment.
Disjoint and Complete Classes(disjoint and complete classes, disjoint and complete): A property ensuring every input belongs to exactly one class per classification with no overlap and full coverage.
Domain(domain): A set of values that a variable can take, either continuous or discrete.
Domain Analysis(domain analysis): A black-box test design technique that tests the boundaries and partitions of input and output domains.
Domain Boundary(boundary): The edge of a domain where the behavior of the system changes.
Don't Care Entries(don't care entries): Entries used to reduce the number of test cases in a decision table while covering important combinations.

E

Each Condition Coverage(each condition): A coverage criterion ensuring each condition takes both true and false values at least once.
Environmental Conditions(environmental conditions): Contextual factors such as load or network speed that must be specified for testing quality characteristics.
Equivalence Partitioning(equivalence partitioning): A black-box test technique that divides input data into partitions from which test cases can be derived.
Error Guessing(error guessing): An experience-based technique that uses the tester's knowledge to guess potential defects and design test cases.
Exception scenarios(exception scenarios): Alternative or error conditions that a user story may encounter, requiring additional test cases.
Experience-Based Test Techniques(experience-based techniques, experience-based test techniques, experience-based technique): Test design techniques that rely on the tester's knowledge, intuition, and experience to derive test cases.
Exploratory Testing(exploratory testing): An experience-based technique involving simultaneous learning, test design, and test execution.

F

Formal Review Process(formal review process steps, review steps): A structured review with defined phases: planning, kick-off, preparation, review meeting, rework, follow-up.
Functional Suitability(functional suitability): A quality characteristic measuring the degree to which functions meet stated and implied needs under specified conditions.

G

Given-When-Then format(given-when-then format, gherkin, given-when-then): A structure for writing acceptance criteria, also known as Gherkin, specifying context, action, and expected outcome.

H

Happy path(happy path): The main success scenario of a user story that should be covered by test cases.
Heuristic Evaluation(heuristic evaluation): A usability evaluation method where experts inspect an interface against established usability principles.
Higher-order Combinatorial Testing(higher-order combinatorial testing, triplewise): Testing that covers interactions among three or more parameters, used when defects require higher-order combinations.

I

ISO 25010(iso 25010): A standard that defines compatibility as the degree to which a product can exchange information and perform functions while sharing an environment.
ISO 25010 Quality Model(iso 25010 model): A standard that defines a set of quality characteristics for software products, such as functional suitability and reliability.
ISO/IEC 25010 Quality Model(iso/iec 25010, iso/iec 25010 model): An international standard defining eight quality characteristics for software product quality.
ISTQB Glossary Definitions(istqb glossary): Authoritative definitions of testing terms used as references for the CTAL-TA exam.
Interoperability(interoperability): A sub-characteristic of compatibility where a product can exchange and use information with other products.
Iterative test process(iterative test process, cyclical activities): TA activities repeated each increment to adapt to new features and changes.

M

Measurable Thresholds(quantitative thresholds, measurable thresholds): Quantitative limits (e.g., response time, availability percentage) that make acceptance criteria unambiguous.

N

Nielsen's Heuristics(nielsen's heuristics): A set of ten usability principles used for heuristic evaluation to identify usability issues.

O

Objective Defect Reporting(objective defect reporting, objective defect report, factual defect reporting): The practice of writing defect reports without assumptions about the cause, focusing on facts.
Orthogonal Arrays(orthogonal arrays): A combinatorial technique that ensures each pair of values appears exactly the same number of times, providing balanced coverage.

P

Pairwise Combination(pairwise): A coverage criterion that requires testing pairs of classes from different classifications.
Pairwise Coverage(pairwise): A coverage criterion that reduces test cases by covering pairs of conditions.
Pairwise Testing(pairwise testing, all-pairs testing): A black-box technique that tests all pairs of input parameters to reduce the number of test cases.
Portability(portability): A quality characteristic measuring the ease of transferring a system from one operational or usage environment to another.

Q

Quality Characteristics(quality characteristics): Abstract attributes like usability or performance that are broken down into sub-characteristics for testing.
Quality Risk(quality risk): A factor that guides the selection of test techniques based on the type of defects to target.

R

Regression testing(regression testing, regression test suite): Testing to verify that unchanged functionality still works after changes.
Reproducibility(reproducibility): The ability to consistently recreate an anomaly under the same conditions.
Review Types(static review types): Categories of static testing such as informal review, technical review, walkthrough, and inspection.

S

Scenario-Based Review(scenario-based review): A review technique that walks through the work product using realistic user scenarios or use cases.
Severity vs. Priority Distinction(severity vs. priority): A key distinction in defect management: severity measures impact on the system, priority measures urgency of fixing.
Specification-Based Technique(specification-based technique): A test technique that uses detailed requirements or specifications to derive test cases.
State Transition Testing(state transition testing): A black-box technique that models system states and transitions to derive test cases.
Statement Testing and Coverage(statement testing, statement coverage): A white-box technique that tests each statement in the code at least once.
Static Testing Technique(static testing): A testing method that finds defects in work products without executing code.
Sub-characteristics of Quality(sub-characteristics): Specific attributes under each quality characteristic, such as functional completeness, learnability, or interoperability.
Systematic test design methods(systematic test design methods): Structured approaches for creating test cases to ensure comprehensive coverage.

T

Task Analysis(task analysis): A technique for understanding user tasks and goals to design relevant usability test scenarios.
Technical Test Analyst Role in Reviews: The role focusing on technical aspects of reviews, such as architecture and performance.
Test Analyst Role(test analyst, test analyst role): The role focused on testing functional suitability, usability, compatibility, and portability from a user-oriented perspective.
Test Analyst Role in Reviews(test analyst contribution): The role responsible for evaluating work products from an end-user perspective during reviews.
Test Analyst Role in Usability Testing(test analyst's specific contributions to usability testing): The test analyst plans, designs, executes usability tests, analyzes results, and documents usability issues.
Test Basis(test basis): The collection of artifacts (e.g., requirements, user stories, design documents) used as a foundation for testing.
Test Basis Documents(test basis): Documents from which test cases are derived; reviewed for defects by the Test Analyst.
Test Case(test case, test cases): A set of input values, execution preconditions, expected results, and execution postconditions developed for a particular objective.
Test Case Combination(test case, combination of classes): The selection of one class from each classification to form a test case.
Test Case Generation(generating test cases): Process of creating test cases by selecting one class from each classification.
Test Condition(test condition, test conditions): An item or event of a component or system that could be verified by one or more test cases.
Test Environment Representativeness(test environments): The principle that test environments must accurately reflect the target production environment to detect compatibility defects.
Test Environment Verification(test environment verification, environment verification, pre-anomaly verification): The step of confirming that the test environment and data are correct before logging an anomaly.
Test Level vs. Test Type Distinction(test level vs. test type): A distinction where test level refers to a specific test phase (e.g., unit, integration), test type refers to a test objective (e.g., functional, performance).
Test Manager Role Confusion(test manager vs. test management role): A common confusion between role titles such as 'test manager' and 'test management role', which can have different scopes in ISTQB contexts.
Test Manager Role in Reviews: The role focusing on managerial aspects of reviews, distinct from the Test Analyst's user-oriented focus.
Test Oracle(test oracle, oracle): A mechanism used to determine whether a system meets a given acceptance criterion during testing.
Test Process(test process): A set of activities applied repeatedly across the software development lifecycle, including test analysis, design, implementation, and execution.
Test Process Activity Sequence(reversing the order of activities): The prescribed order of activities within a test process, such as planning, analysis, design, implementation, execution, and closure.
Test Technique(test technique): A procedure used to derive and/or select test cases, according to the ISTQB glossary.
Test Technique Selection(technique selection): The systematic process of choosing test techniques based on quality risks and project context.
Test analysis(test analysis): Reviewing new or changed requirements to identify testable conditions.
Test artifact review(test artifact review, artifact review, test case review): Reviewing and updating existing test cases each increment to maintain validity.
Test design(test design): Creating or updating test cases using techniques like equivalence partitioning.
Test implementation(test implementation): Preparing test data, setting up test environments, and organizing test cases.
Testable Acceptance Criteria(testable acceptance criteria): Acceptance criteria that are unambiguous, independent of implementation details, and can be verified by a test.
Think-Aloud Protocols(think-aloud protocols): A method where users verbalize their thoughts while performing tasks to reveal usability problems.
Traceability(traceability): The ability to link test conditions and test cases back to the test basis to demonstrate coverage and support impact analysis.
Two-way Interaction(two-way interactions): An interaction between two parameters that is the primary cause of most defects according to empirical observation.

U

Usability(usability): A quality characteristic measuring the effectiveness, efficiency, and satisfaction of specified users achieving goals in a context.
Usability Defect(usability defects, usability issues): A problem affecting user experience, categorized by severity, frequency, and impact, reported with evidence.
Usability Requirements(usability requirements): Requirements specifying quality characteristics like learnability, operability, and accessibility for usability testing.
Usability Test Environment(test environment that mimics real user conditions): A test environment that mimics real user conditions such as different devices and network speeds.
Usability Test Scenarios(usability test scenarios): Test scenarios defined by the test analyst based on user personas and tasks to simulate real-world usage.
Usability Testing(usability testing): A dynamic testing activity assessing how effectively, efficiently, and satisfactorily specified users achieve goals in a specified context.
Use Case Testing(use case testing): A black-box test technique that derives test cases from use cases to validate system behavior.
User Observation(user observation): A usability testing technique where the test analyst observes users interacting with the product to identify issues.
User story(user story): A concise description of a feature from the end user perspective, following the format: As a [role], I want [goal] so that [benefit].
User story testing(user story testing): Test creation that validates the story's intent and acceptance criteria, focusing on business value.
User-Oriented Defects(user-facing defects): Defects related to usability, functional correctness, and consistency with requirements found during reviews.

V

Validation vs. Verification Distinction(validation vs. verification): A fundamental testing distinction: verification checks if the product is built correctly, validation checks if the correct product is built.

W

White-Box Test Techniques(white-box techniques, white-box test techniques): Test design techniques that derive test cases from an analysis of the internal structure of the component or system.
Work product review(work product review): TA participation in reviewing requirements and user stories each increment.