CT-AcT — Acceptance Testing glossary

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

A

Acceptance Criteria Definition(acceptance criteria definition): The process of transforming high-level requirements into clear, testable conditions through tester-business analyst collaboration.
Acceptance Test-Driven Development(atdd): A collaborative practice where acceptance criteria are defined before coding begins.
Acceptance Testing Tool Categories(tool categories): Groups of acceptance testing tools classified by primary function as per ISTQB syllabus.
Acceptance Testing for Non-Functional Requirements and Quality Attributes(non-functional acceptance testing, operational acceptance testing, oat, acceptance testing for non-functional requirements and quality attributes, acceptance testing for non-functional requirements, non-functional requirements acceptance testing): Acceptance testing focused on evaluating non-functional aspects such as performance, security, and usability.
Acceptance criteria(acceptance criteria): Conditions that a system must satisfy to be accepted by stakeholders, often written in Given/When/Then format.
Acceptance tests(acceptance tests): Tests derived from acceptance criteria to verify that the system meets requirements.
Alpha Testing(alpha testing): Acceptance testing performed by internal teams in a controlled environment before external release.
Atomic Acceptance Criteria(atomic acceptance criteria, independent criteria): Acceptance criteria that are independent and each address one specific condition to trace requirements clearly.
Atomic Acceptance Criterion(atomic acceptance criterion): A single, testable condition that can be verified independently and addresses one specific requirement.
Authentication and Authorization Testing(authentication and authorization testing): A test type that verifies identity verification and access control mechanisms.

B

BDD Frameworks(bdd frameworks): Frameworks like Cucumber used for collaborative acceptance test automation.
BPMN Diagram(bpmn diagram, bpmn diagrams): A standardized graphical notation for modeling business processes to derive acceptance test scenarios.
Behavior-Driven Development(bdd): A collaborative practice using the Given/When/Then format to define acceptance criteria.
Beta Testing(beta testing, field testing): Acceptance testing performed by selected external users in their own environments to gather early feedback.
Business Process Model and Notation (BPMN)(bpmn): A standard notation for modeling business processes using symbols for events, activities, gateways, and flows.
Business Process-Based Acceptance Testing(business process-based acceptance testing, business process modeling for acceptance testing, acceptance test scenario generation from process models): An acceptance testing approach that uses process models to derive test scenarios covering end-to-end flows.
Business Rule(business rule, business rules): A condition that governs business processes and is tested using decision tables in acceptance testing.

C

Capacity(capacity): A performance attribute referring to the maximum number of users or transactions a system can handle while meeting targets.
Checklist-Based Testing(checklist-based testing): A technique using a list of items or conditions derived from experience, risks, or defects to structure testing with flexibility.
Collaboration Tools(collaboration tools): Tools that facilitate communication among stakeholders in acceptance testing.
Collaborative Acceptance Criteria Definition(collaborative definition, defined collaboratively): The practice of defining acceptance criteria jointly by stakeholders, testers, and developers to ensure shared understanding.
Collaborative Acceptance Testing(collaborative testing, collaborative acceptance testing): An acceptance testing approach involving joint efforts of stakeholders, developers, and testers.
Collapsed decision table(collapsed decision tables): A technique to reduce redundancy in decision tables while ensuring each unique rule is still tested.
Compound Acceptance Criterion(compound acceptance criterion): An acceptance criterion that combines multiple conditions using conjunctions like 'and' or 'or'.
Criteria-based testing(criteria-based testing): Testing that is based on formal acceptance criteria and structured verification steps.

D

Data Integrity Checks(data integrity checks): Tests that ensure data has not been altered or corrupted during processing or storage.
Decision Table(decision table, decision tables): A table capturing combinations of conditions and corresponding actions for systematic business rule testing.
Defect Analysis and Feedback(defect analysis and feedback): The collaborative assessment of defects to determine business impact and prioritize rework.
Defect Resolution Path(resolution path, defect resolution path): An agreed course of action for a defect, such as fixing it, updating criteria, or deferring the issue.
Defect Triage Criteria(triage criteria): A set of rules used to filter low-impact issues before they are discussed in a joint defect analysis session.
Defect triage(defect triage, defect triage criteria): A process that uses agreed criteria to filter low-impact defects before joint analysis sessions.
Dynamic Application Security Testing (DAST)(dast, dynamic application security testing): An automated tool that tests running applications for security vulnerabilities.

E

Error guessing(error guessing): An experience-based testing technique where testers rely on intuition to predict and uncover defects.
Experience-Based Practices(experience-based practices, experience-based techniques): Testing approaches that leverage tester knowledge and intuition to find defects, including error guessing, exploratory testing, and checklist-based testing.
Experience-based testing(experience-based testing, experience-based practices): Testing techniques that rely on the tester's skill, intuition, and domain knowledge to find defects.
Exploratory testing(exploratory testing): An experience-based testing technique involving simultaneous test design, execution, and learning.

G

Given/When/Then format(given/when/then format, scenario-based format, given/when/then): A structured format for acceptance criteria that separates preconditions, actions, and expected outcomes.

I

ISTQB Glossary(istqb glossary): The official terminology reference for ISTQB exams that overrides intuitive understanding.
ISTQB testing terminology glossary(istqb glossary, istqb terminology glossary): The authoritative source of testing terms used across all ISTQB syllabi, providing canonical definitions for exam answers.
Independence of Acceptance Criteria: The property that each atomic criterion does not depend on another for its meaning or verification.

J

Joint Defect Analysis(joint defect analysis): A structured meeting where acceptance testing team, business analysts, and product owners collaboratively review defects to determine their validity and priority.
Joint Test Design and Review(joint test design and review): A collaborative activity where testers and business analysts create and review acceptance tests for completeness and business alignment.

N

Non-functional Testing Tools(non-functional testing tools): Tools that measure performance, security, and usability against acceptance criteria.

O

OWASP Top 10(owasp top 10): A standard awareness document listing the most critical web application security risks.
Operational Acceptance Testing(oat, operational acceptance testing): Testing that ensures the system is ready for operational use, covering aspects like backup, recovery, and security.
Operational Acceptance Testing (OAT)(oat, operational acceptance testing): A testing phase that ensures a system is ready for operational use, including security acceptance testing.

P

Penetration Testing(penetration testing): A manual or automated test that simulates attacks to evaluate system security.
Performance acceptance criteria(performance acceptance criteria): Measurable and unambiguous thresholds derived from SLAs or business requirements for system performance.
Performance efficiency(performance efficiency): A quality attribute defined in ISO 25010 that encompasses time behavior, resource utilization, and capacity.
Pilot Project for Tool Evaluation(pilot project): A small-scale trial to evaluate a tool's fit before full adoption.
Priority(priority): A testing concept that denotes the order of importance or urgency for addressing defects or test cases.
Probe effect(probe effect): The phenomenon where monitoring tools themselves affect system performance during testing.
Process and Business Rules-Based Acceptance Testing(business rules-based acceptance testing, process and business rules-based acceptance testing): A type of acceptance testing that validates software against defined business processes and rule sets.

R

Representative test environment(representative test environment): A test setup that mimics production to obtain valid performance test results.
Resource utilization(resource utilization): A performance attribute examining how a system uses CPU, memory, disk, and network resources.
Risk-Based Prioritization(risk analysis, risk-based prioritization): A method to prioritize security tests based on threat likelihood and impact.
Rule-based Format(rule-based format, checklist format): A checklist format for acceptance criteria that lists simple conditions, suitable for business rules or non-functional requirements.

S

SMART criteria(smart criteria): An acronym for Specific, Measurable, Achievable, Relevant, Time-bound, used to define acceptance criteria.
Security Acceptance Criteria(security acceptance criteria): Measurable and testable conditions that define when security requirements are met.
Security Acceptance Testing(security acceptance testing): A type of operational acceptance testing that verifies security controls are correctly implemented and effective.
Service-level agreement (SLA)(service-level agreements, slas): A contract that defines expected performance levels and serves as a source for acceptance criteria.
Splitting Compound Criteria: The process of breaking a compound criterion into multiple atomic criteria by removing conjunctions.
Static Application Security Testing (SAST)(sast, static application security testing): An automated tool that analyzes source code for security vulnerabilities.

T

Test Design and Automation Tools(test design and automation tools): Tools that support creation and execution of acceptance tests, often using keyword-driven or BDD frameworks.
Test Level(test level): A group of test activities organized by the stage of development, such as unit, integration, system, or acceptance testing.
Test Type(test type): A category of testing focused on specific quality characteristics, such as functional, performance, or security testing.
Testable Acceptance Criteria(testable acceptance criteria): Acceptance criteria that can be objectively verified whether the condition is met, avoiding vague terms.
Time behavior(time behavior): A performance attribute measuring response times, processing speeds, and throughput rates.
Tool Selection Criteria: Factors for choosing a tool based on methodology, acceptance testing type, and team skills.
Tools and Automation for Acceptance Testing(acceptance testing automation, tools and automation for acceptance testing): Software tools and scripts used to automate the execution of acceptance tests.
Traceability: The ability to link each acceptance criterion directly to a single requirement and a single test.

U

User Acceptance Testing(user acceptance testing, uat): Acceptance testing performed by end-users to validate business needs and usability.

V

Validation(validation): A testing activity that evaluates whether the product meets the user's real-world needs and expectations.
Verification(verification): A testing activity that checks if the product complies with specified requirements or design specifications.
Verification and Validation(verification, validation): Verification checks compliance with specified requirements; validation ensures the product meets user needs.
Vulnerability Scanning(vulnerability scanning): An automated test type that identifies known vulnerabilities in a system.