CT-MBT — Model-Based Testing glossary

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

A

Abstract Test Case Transformation(adaptation of abstract test cases, transforming abstract test cases): The process of converting abstract test cases into executable test scripts by adding concrete input values and system-specific commands.
Abstract test cases(abstract test case, abstract test cases): Sequences of actions or states from the model that describe what to test but not how to execute it.
Abstraction Level in MBT(level of abstraction, abstraction level): The degree of detail in an MBT model, balancing effort and coverage according to testing needs.
Adaptation layer(adapter, adaptation layer): A bridge that maps abstract actions to concrete API calls, UI interactions, or system commands.
Alignment of MBT metrics with organizational goals(alignment with organizational goals): A principle from the ISTQB syllabus that deployment metrics should align with organizational objectives and be tracked over time.
Automated Test Case Generation(automated test generation, automatic test case generation): The process of automatically deriving test cases from a model without manual intervention.
Automated regression testing for MBT(regression testing of test cases, automated regression testing): A practice of re-executing generated test cases automatically to detect inconsistencies after model updates.
Automatic test regeneration(automatic test regeneration): The automatic regeneration of tests when the source model is updated, reducing maintenance effort.

B

Boundary Value Analysis(boundary value analysis, boundary value analysis technique, boundary values): A data-based technique that selects test cases at the boundaries of equivalence classes to detect boundary-related defects.
Boundary value coverage(boundary value coverage, boundary value coverage criterion): A data coverage criterion requiring test cases that exercise the boundaries of input domains.

C

Classic Test Design Techniques(classic techniques, classic test design techniques): Manual test design methods such as equivalence partitioning, boundary value analysis, and state transition testing.
Common Mis-Recall Patterns(common mistakes, common pitfalls): Recurring errors such as reversed process steps, confused role names, or rephrased glossary terms.
Concretizing test cases(test implementation, concretization): The process of transforming abstract test cases into concrete, executable test scripts.
Consistency and Repeatability(consistency and repeatability): Properties of MBT where generated test cases are uniform and can be reproduced reliably across runs.
Continuous testing pipeline(continuous testing pipeline): An integrated CI/CD environment where MBT is applied for ongoing test generation and execution.
Cost-Benefit Analysis(cost-benefit analysis): A systematic process of identifying and estimating costs and benefit streams for MBT deployment.
Coverage criteria(all-states coverage, all-transitions coverage, coverage criteria): Specific selection criteria like all-states or all-transitions used to generate test cases from the model.

D

Data Boundary Testing(data boundaries): A testing method that examines values at the edges of input ranges to uncover defects.
Data Flow Subject(data-flow model, data flow): A subject of an MBT model that captures how data moves through the system, enabling tests for data integrity.
Data coverage criteria(data coverage criteria, data coverage criterion): Coverage criteria that consider data values used in the model, such as boundary values or pairwise combinations.
Data-Based Selection Criteria(data-based criteria): A test selection family that derives test cases from data aspects of the model, using techniques like equivalence partitioning and boundary value analysis.
Dedicated MBT model(dedicated mbt models, building dedicated mbt models): A model built specifically for test generation, tailored to test objectives and desired abstraction level.
Defect Reports(defect reports): Reports of defects linked to relevant test cases and model elements.

E

Early defect detection through model reviews(early defect detection, model reviews): The practice of validating requirements by reviewing models to catch defects before implementation.
Equivalence Partitioning(equivalence partitioning, equivalence partitions): A data-based technique that partitions model variables into equivalence classes to derive test cases representative of each class.
Executable Test Script(executable test scripts, executable scripts, concrete test script, concrete test scripts): A concrete test script that can be run against the system under test, derived from an abstract test case.

F

Functional Behavior Subject(functional behavior): A subject of an MBT model that captures what the system does, focusing on functionality.

G

Generated Test Cases(generated test cases): Test cases automatically produced from a test model using selection criteria.

H

Hybrid Testing Approach(hybrid approach): A strategy combining Model-Based Testing with manual testing to achieve better ROI.

I

ISTQB Glossary(glossary): The authoritative source for canonical definitions of all ISTQB terms.
ISTQB Sample Exam(sample exam): An official practice exam that mirrors the real exam in length and format.
ISTQB testing terminology glossary(istqb glossary, testing terminology glossary): An authoritative glossary of testing terms used across ISTQB certification syllabi, providing canonical definitions for exam answers.
Impact Analysis(impact analysis): Analysis of how changes affect test coverage, supported by traceability links.
Iterative MBT Model Development(iterative model development): An incremental approach to building models that starts with a small, abstract model and expands based on feedback.

L

Level of Abstraction Selection(level of abstraction, abstraction level): The critical choice of model detail that balances missing test scenarios against costly maintenance.

M

MBT Benefits(benefits of mbt): Efficiency gains such as reduced test creation time, increased coverage, and early defect detection.
MBT Deployment Costs(costs of mbt deployment, deployment costs): Initial and ongoing expenses including tool acquisition, training, modeling, and maintenance.
MBT Pilot Evaluation(evaluating pilot results): The phase after execution where results are compared against predefined metrics to decide on broader rollout.
MBT Pilot Execution(executing the pilot): The standard MBT process of creating a model, generating test cases, executing them, and analyzing results.
MBT Pilot Lessons Learned(lessons learned): Documented insights from the pilot about what worked well and what did not, used to guide scaling decisions.
MBT Pilot Metrics(metrics, evaluation metrics): Quantitative measures such as model coverage, number of generated tests, defect detection rate, and time savings.
MBT Pilot Planning(planning the pilot): The process of defining objectives, selecting tools, training the team, and establishing metrics for the pilot.
MBT Pilot Project Purpose(purpose of a pilot project): To reduce risk by uncovering challenges early, such as tool integration issues or team skill gaps, before full rollout.
MBT Pilot Project Scope(pilot scope): The selection of a representative but not mission-critical project with manageable model size and clear success criteria.
MBT Pilot ROI Measurement(roi, return on investment): Evaluation of return on investment using metrics like time savings and defect detection compared to baseline.
MBT Pilot Risk Reduction(de-risking, risk reduction): The primary benefit of a pilot, uncovering challenges early to avoid costly failures in full adoption.
MBT Pilot Success Criteria(success criteria): Specific, measurable objectives aligned with organizational goals, e.g., reduce test creation time by 30%.
MBT Pilot Team Training(training, team training): Essential preparation to ensure team has sufficient modeling skills, a common cause of pilot failure if skipped.
MBT ROI(roi, return on investment): The return on investment from Model-Based Testing, calculated as (Benefits – Costs) / Costs × 100%.
MBT defect detection rate(defect detection rate): A metric measuring the number of defects found by MBT-generated tests relative to manual testing.
MBT model maintenance(model maintenance, maintaining mbt models, maintaining the model): A continuous process of updating MBT models to keep them consistent with system changes and test objectives.
MBT model maintenance effort(effort to update models, model maintenance effort): A metric measuring the effort required to update models when the system under test changes.
MBT return on investment (ROI)(roi, return on investment): A metric comparing costs of MBT adoption (licenses, training, modeling) against savings from automation and improved quality.
MBT test case generation percentage(percentage of test cases generated from models): A metric quantifying the proportion of test cases generated from models rather than manually.
Manual test design(manual test design): The traditional approach of creating test cases by hand, which is time-consuming and error-prone.
Model Abstraction Level(abstraction level, model abstraction): The level of detail in a model that determines the types of tests that can be generated.
Model Creation and Validation(model creation and validation): The activity of building and verifying a model for use in MBT, shifting effort from manual test design.
Model Maintainability(maintenance effort, model maintenance): The ease of maintaining a model, which can be reduced by excessive detail or complexity.
Model Maintenance(model maintenance, model maintenance effort): Keeping the test model updated alongside the system under test to avoid invalid test cases.
Model Maintenance in Iteration Cycle(model maintenance): The ongoing update of the model as the system evolves, included as part of the iteration cycle.
Model Updates(model updates): Modifications to a model that enable efficient test maintenance when the system changes.
Model Validation Step(model validation): A required review activity in each iteration to ensure the model correctly represents the system or requirements.
Model adaptation for test generation(adaptation, adapting): The process of modifying an existing model to align with the abstraction level and content needed for MBT.
Model coverage(model coverage): A metric quantifying the extent to which model elements (states, transitions, decisions) are exercised by tests.
Model drift(model drift, drift from system behavior): A situation where an MBT model becomes out of sync with the actual system behavior over time.
Model quality and maintenance(model quality, maintenance): The accuracy, completeness, and currency of a model, affecting the reliability of generated tests.
Model reuse validation(reusing an existing model, model reuse): Verification that a reused design model still captures necessary testing details like error handling.
Model validation(model validation): The process of ensuring that models correctly represent intended behavior to produce valid tests.
Model-Based Testing(model-based testing, mbt): A test approach that uses a formal model of system behavior to automatically generate test cases.
Model-Based Testing (MBT)(mbt, model-based testing): A testing approach that automates test case generation from models of system behavior.
Model-Based Testing (MBT) deployment(deployment of mbt in an organization, mbt deployment): The process of introducing and integrating Model-Based Testing practices across an organization's software testing lifecycle.
Model-Based Testing Pilot Project(mbt pilot project, pilot project): A small-scale, controlled implementation of MBT to assess feasibility, benefits, and costs in a specific context.
Model-Test Traceability(traceability between model elements and test cases, traceability): The linkage between model elements and generated test cases, essential for impact analysis when the model or system changes.
Modeling Language(modeling language): A language, such as UML state machines or activity diagrams, used to build the test model.
Modeling Notation Selection(modeling notation, notation selection): The choice of modeling notation (e.g., state machines, activity diagrams) based on the type of test objective.
Multiple Model Subjects(multiple subjects, multiple models): The practice of using different models with distinct subjects to cover various testing concerns without overcomplicating a single model.

O

Over-modeling in Early Iterations(over-modeling): A common pitfall where too many details are added before core behavior is validated, increasing rework and delaying feedback.

P

Pairwise coverage(pairwise coverage): A data coverage criterion ensuring that every combination of values for two variables is tested.
Pairwise testing(tests interactions between requirement pairs): A software testing technique that tests interactions between pairs of requirements to reduce test cases.
Parameterization: The creation of multiple test instances from a single abstract test case by varying parameter values.
Periodic model review(model review, periodic review of models): A scheduled activity to check MBT models for consistency, completeness, and adherence to modeling guidelines.
Priority(priority): A category assigned to a test case or defect indicating its importance relative to others in testing.
Project-Driven Selection Criteria(project-driven criteria): A test selection family based on non-functional factors such as risk, schedule, and resource availability to prioritize test cases.

R

ROI Calculation Formula(roi formula): The formula (Benefits – Costs) / Costs × 100% used to quantify MBT ROI.
Random Selection Criteria(random selection, random selection criteria): A test case generation method that selects test cases uniformly at random from the set of all possible test sequences, with each having equal probability.
Regression Testing with MBT(regression testing, regression testing with mbt): Using an MBT model to quickly regenerate test cases after system changes to ensure continued correctness.
Requirements Coverage(requirements coverage): A technique within requirements-based selection criteria where each requirement triggers at least one test case.
Requirements Pair Coverage(requirements pair coverage): A technique within requirements-based selection criteria where each pair of requirements is tested together.
Requirements-Based Selection Criteria(requirements-based selection criteria, requirements-based criteria): A family of test selection criteria in CT-MBT that derives test cases from the model by targeting specific functional or non-functional requirements, focusing on coverage of requirements rather than structural model elements.
Requirements-based coverage criteria(requirements-based coverage criteria): Coverage criteria that link test cases to specific requirements, ensuring each requirement is covered by at least one test case.
Reusing Existing Models for MBT(reusing an existing model, existing model reuse, model reuse for mbt, reusing existing models): Using a model created for another purpose and adapting it for model-based test generation.
Risk Assessment: The process of evaluating risk levels of model elements to guide test selection, requiring reliable assessments.
Risk-Based Criteria(risk-based criteria): A project-driven criterion that prioritizes test cases covering high-risk model elements based on assessed risk levels.
Risk-Based Selection Criteria(risk-based criteria): Test selection criteria that prioritize test cases covering high-risk model elements based on assessed risk levels.
Risk-based testing(risk-based criteria): A testing approach that prioritizes test cases based on risk criteria, focusing on high-risk model elements.

S

Sample Exam Rationale(rationale document): Documentation explaining the correct answer and why each distractor is wrong.
Selection Criteria(selection criteria, coverage-based selection criteria): Rules or conditions used to automatically derive test cases from a test model.
Severity vs Priority(severity, priority): Two closely-related but distinct concepts in defect management; severity indicates impact, priority indicates urgency.
Single source of truth(mbt model, model): The MBT model that serves as the primary basis for generating and maintaining test cases.
State Machine Model(state machine model): A model focused on states and transitions, suitable for testing control-flow aspects of a system.
State Transition Testing(state transition testing): A classic technique that tests system behavior by modeling states and transitions.
State coverage(state coverage): A structural coverage criterion requiring that every state in the model is visited by at least one test case.
Stochastic Selection Criteria(stochastic selection, stochastic selection criteria): A test case generation method that assigns probabilities to model elements and generates test cases according to those probabilities to focus on important or frequently used parts.
Structural Coverage in MBT(structural coverage, coverage objective): A test objective requiring explicit model elements to achieve coverage of transitions, decisions, or other structures.
Structural coverage criteria(structural coverage criteria, structural coverage): Coverage criteria focusing on covering elements of a model's structure such as states, transitions, or decisions.
Subject of MBT Model(subject of an mbt model, subject of mbt model): A specific aspect or view of the system under test that a model represents, defining the scope of test generation.
Systematic coverage(test coverage, systematic coverage): The property of tests ensuring all modeled behaviors, including edge cases, are tested.

T

Test Execution Feedback Loop(feedback loop, iterative workflow): An iterative cycle where test execution results inform updates to the model, enabling model refinement.
Test Execution Logs(test execution logs, test execution log): Records of actual results and deviations during test execution.
Test Generation(test generation): Process of creating test cases from a model based on selection criteria.
Test Generation Efficiency(generation efficiency, efficiency of test generation, test generation efficiency): The speed and cost of generating tests from a model, which can be reduced by overly complex models.
Test Generation vs Test Selection(test generation, test selection): Two process steps in test design; test generation creates test cases, test selection chooses which to execute.
Test Implementation(test implementation): The step of transforming abstract test cases into concrete, executable test scripts via mapping and adapters.
Test Lead(test lead): Role overseeing daily testing activities such as model creation and test execution.
Test Manager vs Test Lead(test manager, test lead): Two distinct roles; a test manager has overall responsibility, while a test lead oversees daily testing activities.
Test Model(test model, model): A representation of system behavior used to derive test cases in MBT.
Test Objective Alignment(aligning model selection with test objectives, objective alignment, test objectives, selecting the appropriate subject, test objective alignment): The principle that model abstraction and notation should be chosen to match the specific test objectives.
Test Scripts(test scripts): Exportable formats of generated test cases for test execution tools.
Test Selection(test selection): Process of choosing which generated test cases to execute based on risk, time, or other factors.
Test case concretization(concretization): Process of converting abstract test cases into executable concrete test cases.
Test case traceability(traceability): Ability to link test cases back to their source requirements or model elements.
Test data binding(test data binding): The inclusion of parameter values or test data during the generation of abstract test cases.
Test level(test level): A group of test activities organized together, such as unit, integration, system, or acceptance testing.
Test maintenance via model updates(test maintenance, model update, model updates): The capability to update only the model and automatically regenerate tests when the system changes.
Test management role(test management role): The set of responsibilities overseeing and coordinating the testing effort within a project.
Test manager(test manager): The person responsible for planning, organizing, and controlling the test process.
Test type(test type): A group of test activities aimed at testing specific characteristics, like functional, performance, or security testing.
Time-Based Criteria(time-based criteria): A project-driven criterion that limits the number of test cases to fit a given execution window or schedule constraint.
Traceability Reports(traceability reports, traceability report): Documents linking each test case to model elements and requirements.
Traceability of model changes(change traceability, model change traceability): A requirement that model updates are linked to the source of change, such as a requirement change request.
Trade-offs in MBT strategy(trade-offs): The balance between cost, effort, abstraction level, and suitability when choosing between reusing or building models.
Transition coverage(transition coverage): A structural coverage criterion requiring that every transition is executed at least once, and the most commonly used MBT criterion.

V

Validation(validation): The process of evaluating a system to determine if it satisfies the specified requirements during or at the end of development.
Validation vs Verification(validation, verification): Two distinct testing activities: verification checks if the product is built correctly, validation checks if the correct product is built.
Verification(verification): The process of evaluating a system to determine if it meets conditions imposed at the start of a development phase.