iSQI CTFL-AcT ISTQB Certified Tester - Acceptance Testing (CT-AcT) Exam Practice Test

In Acceptance Test-Driven Development (ATDD), test cases are derived early and are based on business understanding. Application workflows modeled using BPMN or similar notations provide a clear, visual representation of how a user interacts with a system and which business rules are applied.

Option D is correct because these workflow models help define acceptance test cases by outlining the process paths, user interactions, and decision points. These visual models bridge the gap between business needs and testing.

Other options:

A is incorrect — business rule and process models are created based on need; one doesn't necessarily precede the other.

B is misleading — writing business rule models doesn't imply stakeholder commitment to ATDD.

C is incorrect — Gherkin is used for writing scenarios in BDD/ATDD, but business rules are typically modeled using DMN, not Gherkin.

Answer: D. Application workflow models facilitate the generation of ATDD acceptance test cases

Non-functional quality attributes (also called quality characteristics) such as usability, reliability, operability, performance, and maintainability are often validated during acceptance testing to ensure the system behaves as expected under real-world conditions.

Option C is correct because operability — a subcharacteristic of usability per ISO 25010 — refers to the degree to which users can operate and control the system effectively. Acceptance testing often involves running the system in realistic settings to validate these aspects.

Other options:

A (Modularity and reusability) are more relevant to system architecture and design, not acceptance testing.

B is incorrect — time behavior (performance) can and should be tested at multiple levels, including system and integration testing before acceptance.

D is misleading — testing basic functionality is necessary, but it does not address non-functional quality attributes.

Answer: C. During acceptance testing, the operability of the product is checked in a realistic environment

In cross-functional, globally distributed teams, establishing collaboration, communication, and trust is key. A workshop (even virtual) is a proven method for initiating alignment, especially when a new team member joins, and project coordination is weak.

Option A promotes transparency and collective understanding, crucial for building team cohesion.

Option B is too passive and one-directional. Long emails rarely solve coordination problems in Agile or collaborative contexts.

Option C is about tool setup, not team integration or communication — tools are supportive but not substitutes for human connection.

Option D is not efficient; traveling to meet each team member is impractical and doesn’t guarantee a shared team vision.

✔ Answer: A. You organize a workshop with all team members to establish common understanding and to lay the foundation for fruitful trusting collaboration.

Equivalence Partitioning (EP) is a black-box test design technique that divides input data into valid and invalid partitions, where each partition is expected to exhibit similar behavior. In the context of acceptance testing, EP is especially effective because it helps validate whether a system behaves correctly for representative input ranges defined in the acceptance criteria.

Acceptance testing aims to confirm that the system meets business requirements and handles inputs as expected. EP allows the tester to cover a large input space using fewer test cases while maintaining a high level of effectiveness. It supports efficiency, broad coverage, and relevance to user expectations.

Other options are less suitable:

A. Static code analysis is a white-box technique, more relevant to unit or integration testing.

B. Input validation is an objective or activity, not a test design technique.

D. Defect-based testing is more diagnostic, used after failures or during exploratory testing — less structured for planned acceptance testing.

Exact Reference – ISTQB CTFL Acceptance Testing Syllabus (Section 2.4):

“Black-box techniques such as equivalence partitioning and boundary value analysis are suitable for deriving acceptance tests from user stories or business rules.”

In BPMN models, additional annotations such as links to requirements, test data, or risks improve the value of the diagram for downstream stakeholders like testers. When BPMN tasks or flows are linked to known risks, testers can prioritize regression test cases accordingly — a key principle in risk-based testing.

Option D is correct because linking risks to business processes gives testers meaningful input for deciding which parts of the system require deeper or repeated testing.

Other options:

A: Priority links are useful, but less impactful than risk-based test selection.

B: Links to test equipment are not commonly embedded in process diagrams and are more relevant to hardware or system integration testing.

C: Linking to requirements helps traceability, but execution readiness is more closely tied to test cases and data than to BPMN.

Answer: D. Link to risks provide input to testers for selecting regression tests

Traceability is a key principle in requirements and test management. It ensures that all features, requirements, and tests are linked and accounted for. Including traceability to user stories in BPMN diagrams or DMN tables supports transparency, auditability, and maintenance.

Option B is correct because embedding or referencing traceability information within business models improves communication across stakeholders, ensures proper test coverage, and helps during change impact analysis.

Let’s evaluate other options:

Option A is incorrect. Trying to place all model elements in one diagram can lead to cluttered and unreadable models.

Option C is misleading. While separation of concerns is useful, traceability (links to requirements, risks) should be integrated or closely accessible from the models.

Option D is incorrect. Acceptance testers should be involved early to collaborate and review models. Waiting until models are finalized contradicts agile and ATDD principles.

Answer: B. BPMN diagrams and DMN tables should include information such as traceability to user stories.

Effective test reporting should be tailored to the audience’s role and needs. Project managers are typically concerned with high-level progress, schedules, risks, and milestones. Progress trend charts (e.g., test execution over time, defect trends) provide insights into how the project is advancing and help identify delays or bottlenecks.

Option B is correct as it fits the informational needs of a project manager.

Other options:

A: Defect reports are too detailed for steering groups, which prefer strategic summaries or risk reports.

C: Pie charts may provide high-level summaries, but development teams usually need detailed defect or test result data.

D: System users (e.g., customers) are not responsible for project risks and would not benefit from test risk rankings.

Answer: B. Progress trend charts for the project manager

Let’s analyze the DMN table shown in the image:

Rule 1: If weight ≤15, size ≤50, and distance ≤10 → use Normal bicycle

Rule 2: If weight is between 15 and 60 kg, size ≤150, and distance ≤25 → use Electric cargo bike

Rule 3: Otherwise → use Electric van

Now consider the options:

A: Incorrect — parcel size is not the only determining factor for using electric vans; it's about weight, size, and distance combined.

B: Incorrect — normal bicycles are used only when weight ≤15 kg, size ≤50 cm, and distance ≤10 km — so not just “short trips.”

C: Incorrect — electric cargo bikes are explicitly used for short trips (≤25 km), per Rule 2.

D: Correct — based on the rules, any weight above 15 kg (and up to 60 kg) results in the use of electric cargo bikes. So if weight >50 kg (but ≤60), cargo bike is still used under the conditions of Rule 2.

Therefore, the most consistent interpretation of the decision model is:

Answer: D. When the weight of the parcel exceeds 50kg then the electric cargo bike is necessarily used

User Experience (UX) requirement analysis is a critical component of acceptance testing and product development. According to ISTQB Acceptance Testing syllabus and industry-aligned UX design methodologies (e.g., ISO 9241-210 and BABOK guidelines), UX requirement analysis is typically structured around the following pillars:

User Analysis – Understanding who the users are (roles, goals, experience levels)

Task Analysis – Understanding what users do (tasks, workflows, pain points)

Context Analysis – Understanding where and how users interact with the product (environmental and contextual factors)

Competitor Analysis – Understanding how similar problems are solved in the market

Option B best describes Task Analysis, one of the most practical and impactful pillars. In task analysis, business analysts and UX researchers observe how users interact with current or comparable systems to understand workflow patterns, user frustrations, needs, and required system functionality. This method helps uncover implicit needs that users may not articulate in interviews.

This approach is aligned with ISTQB’s emphasis on understanding real-world usage and business processes as a foundation for deriving acceptance criteria and tests. It supports the creation of realistic scenarios that reflect actual user behavior, which is essential for verifying system fitness for use.

The other options are inaccurate:

A refers to psychological disposition, which is more aligned with user profiling or persona development, not a core focus of user analysis in requirement engineering.

C incorrectly ties context analysis with deriving security requirements, which is not its purpose.

D describes an unrealistic or incorrect method for competitor analysis.

Therefore, Option B is the best description of a key pillar of UX requirement analysis per industry and ISTQB standards.

The relationship between business goals, business needs, and requirements is hierarchical and reflects increasing levels of specificity:

Business Goals: High-level strategic objectives.

Business Needs: Problems or opportunities that must be addressed to achieve those goals.

Requirements: Specific capabilities or conditions the system must satisfy to meet the needs.

Option B is correct because it accurately describes how these elements relate at different abstraction levels in the requirements hierarchy. This relationship is fundamental to business analysis and accepted by standards like BABOK and ISTQB.

Other options:

A is reversed — business goals usually precede and drive the elicitation of requirements.

C and D misrepresent the sequence — product requirements are derived from business goals and needs, not the other way around.

Answer: B. Business goals, business needs and requirements describe, at different levels of abstraction, what shall be achieved

Collaboration between business analysts and testers is essential in defining and reviewing acceptance criteria. When both roles work together, they ensure the criteria are not only aligned with business goals but also testable and clearly specified.

Option A is correct because shared understanding of acceptance criteria allows testers to design test cases that truly validate business expectations, reducing misinterpretations and increasing confidence in the product.

Other options:

B is valid but not the best — non-functional requirements are important but often handled separately.

C is partially correct but assumes acceptance test cases already exist, whereas the review often happens earlier in the process.

D focuses on test reporting, which is downstream from criteria definition and test case design.

Answer: A. A shared vision between the business analyst and the tester on acceptance criteria facilitates the design of acceptance test cases.

In acceptance testing, close collaboration between testers and business analysts ensures that test results are properly interpreted and aligned with business expectations.

A. Testers verify the effectiveness of corrective actions and document their verdict in the defect report — Correct. When a defect is resolved, testers retest the system and record whether the issue is fixed. This is a common testing activity during acceptance test execution.

E. Business analysts compare the test execution result to the acceptance criteria of the requirement / user story — Correct. This ensures the functionality fulfills business needs and determines whether the criteria have been met for acceptance.

Incorrect options:

B: Testers do record actual results, but not necessarily "in a defect" unless a defect is found.

C: Priority is usually assigned by business analysts or stakeholders, not testers alone.

D: Business analysts do consider the impact of changes, but evaluating development risks is more a joint task with architects or developers.

Answer: A and E

Collaboration between business analysts and testers is critical in Agile and acceptance testing environments. One of the most effective areas of cooperation is the joint development and review of acceptance criteria for user stories. This ensures that criteria are testable, clearly defined, and aligned with stakeholder expectations.

Option B is correct because creating acceptance criteria is where both business analysts (who understand the business needs) and testers (who ensure testability and clarity) contribute effectively.

Other options:

A (Business needs assessment) is typically a responsibility of business analysts, not a joint activity with testers.

C (Review of risk to prioritize acceptance tests) is a valuable activity but comes after criteria are defined. While it can be collaborative, it's more specific to test planning.

D (Definition of Beta Testing sessions) is less relevant to ongoing collaborative work between testers and BAs — this involves users and release planning.

Answer: B. Development of acceptance criteria for user stories

Comprehensive Detailed Explanation (Approx. 200 words):

Acceptance criteria should focus on business-relevant outcomes that are specific, testable, and observable. In this user story, the goal is to validate that the registration functionality is available and behaves as expected.

Let's analyze each proposition:

i) “A registration form is displayed on the screen.”

→ Valid. It is observable, specific, and directly aligned with the user story.

ii) “The form is written in the Groovy language; the cursor is initially set on the ‘login’ field...”

→ Invalid as acceptance criteria. It contains implementation details (e.g., “Groovy language”) irrelevant to business stakeholders. Also, low-level UI behavior like cursor position is overly technical and not a business-driven criterion.

iii) “I cannot register myself if the login I choose is used by another player.”

→ Valid. It defines system behavior based on a business rule (unique login) and is testable.

iv) “After successful registration process I am informed about it by an e-mail.”

→ Valid. It describes a user-visible outcome after registration, which is observable and testable.

Correct answer: D. only i), iii), and iv) are well-written acceptance criteria.

Exact Reference – ISTQB CTFL Acceptance Testing Syllabus (Section 1.3.2):

“Acceptance criteria must describe the externally visible and verifiable system behavior, excluding implementation details.”

Acceptance criteria describe the conditions under which a requirement or user story is considered fulfilled. These criteria serve as the basis for deriving acceptance test cases. To transform them into concrete tests, testers apply test design techniques such as:

Business process-based testing (deriving tests from modeled workflows)

Use case testing (based on user interactions with the system)

Option B is correct because it clearly describes how structured techniques are applied to translate acceptance criteria into actionable test cases, ensuring traceability and relevance.

Other options:

A is incorrect — experience-based techniques may supplement, but structured methods are foundational in deriving test cases from defined criteria.

C is misleading — risk-based testing is a well-established and effective practice for prioritizing test efforts, including acceptance testing.

D is incorrect — both functional and non-functional criteria are important; there’s no fixed rule to prioritize one over the other.

Answer: B. Test techniques such as business process-based testing or use case testing can be used to create acceptance tests from the acceptance criteria

Comprehensive Detailed Explanation (Approx. 200 words):

Building a new team with members from diverse backgrounds requires activities that foster shared values, identity, and trust. Designing a team emblem with values, goals, and a motto is a well-known team-building technique often used in Agile kick-offs. It engages creativity, sparks discussion about shared purpose, and reinforces a collective team identity.

Option A is correct because it supports both vision and team spirit — crucial for newly formed teams.

Other options:

B focuses on individual backgrounds but may not build a collective vision.

C risks highlighting negative views about the organization and may not foster trust at the early stage.

D uses a “staircase” metaphor but incorrectly locates the team at the top of the stairs — potentially signaling an endpoint rather than a beginning, making it inappropriate for a new team.

Answer: A. You invite the team members and ask them to design their own emblem…

Beta testing is a type of external user acceptance testing performed by potential or existing customers in a real-world environment. It typically occurs after internal validation and acceptance tests have been passed. The purpose is to validate the product in realistic contexts, identify usability issues, uncover defects that may have been missed in lab settings, and gather feedback for improvements.

Option C is correct because it best describes the intent and value of beta testing — to observe how the product performs in real-life configurations, which may include varying hardware, usage patterns, or business workflows.

Option A is incorrect — while some people use the terms loosely, beta testing is not a strict synonym for acceptance testing. Acceptance testing usually refers to more formal, criteria-driven testing (e.g., alpha or internal acceptance testing), while beta testing emphasizes broad, usage-based validation.

Option B is misleading — beta testers may follow scenarios, but beta testing is not typically based on predefined acceptance criteria alone. It emphasizes exploration in realistic use cases.

Option D is false — beta testing is not primarily about measuring test coverage. It is qualitative and feedback-driven rather than systematically structured.

Exact Reference – ISTQB CTFL Acceptance Testing Syllabus (Section 3.2):

“Beta testing is performed by users in their own environment and supports validation of the system in realistic operational conditions.”

Acceptance Test-Driven Development (ATDD) involves early collaboration between stakeholders to define acceptance criteria and tests before development begins. Using business process models in ATDD helps visualize user behavior, align test cases with real workflows, and serve as living documentation.

Option C is the least meaningful argument because:

Business process models abstractly describe workflows and decisions at a business level. While they help clarify requirements and detect requirement-related defects, they do not directly support detecting defects in the application code, which is typically the focus of unit and integration testing, not acceptance testing.

Let’s validate the other options:

A is a strong argument — process models clarify use cases for testers.

B is valid — graphical models help visualize test coverage directly.

D is true — as business process models evolve, they remain valuable artifacts aligned with current system behavior and requirements.

Answer: C. Business process models will make it easier to detect defects in the application code.

Usability testing aims to evaluate the ease of use, efficiency, and satisfaction with which users can achieve tasks. When checking the ergonomics (e.g., layout, visual clarity, interaction comfort), checklist-based evaluations are particularly useful.

Option A is correct because a checklist of ergonomic/usability heuristics (e.g., Nielsen’s heuristics, ISO 9241 standards) allows evaluators to systematically assess whether the interface meets established usability criteria.

Other options:

B (Biometrics-based evaluation) tracks physiological responses (e.g., stress or eye movement), which are useful but indirect and less targeted to ergonomic checks.

C (Walkthroughs) help assess usability by observing task flows, but they are less focused on layout and ergonomic design.

D (Log file analysis) captures behavior but not directly ergonomic issues like spacing, font size, or element alignment.

Answer: A. Checklist-based evaluation

Comprehensive Detailed Explanation (Approx. 200–220 words):

This question focuses on the coverage criterion “execute all possible process tasks” from the BPMN model of a $100 withdrawal.

Let’s analyze the process:

The process starts when the user selects “Withdraw $100.”

A decision gateway checks if the balance is ≥ $100.

If NO: the card is removed and withdrawal is rejected.

If YES: the user is prompted to select whether they want a receipt.

Depending on the user’s choice:

If YES: the receipt is printed → then $100 is withdrawn → card is removed.

If NO: $100 is withdrawn → card is removed (no receipt printed).

To meet the criterion “execute all possible process tasks,” we must cover:

Rejected withdrawal path (balance < 100)

Withdrawal without receipt

Withdrawal with receipt

Receipt printing

Card removal in both success and failure

Test case coverage:

Test 1 (balance = $100, receipt = YES): covers successful withdrawal + receipt printed.

Test 3 (balance = $85): covers withdrawal rejected + card removed.

Together, these two tests execute all possible process tasks:

Withdraw with receipt

Reject due to insufficient balance

Receipt printed

Withdraw funds

Remove card

Other test combinations are redundant or do not add new path coverage.

Comprehensive Detailed Explanation (Approx. 200–220 words):

In the first BPMN diagram (Loan Request Process), the process starts with the receipt of a loan application. Then, parallel gateways (indicated by the “+” symbols) are used to trigger three separate evaluations: verifying employment, requesting and reviewing a credit record, and performing and reviewing a title search. These are executed concurrently, not sequentially.

After all checks are completed, the loan application is reviewed. A decision gateway (diamond with an “X”) checks whether the loan is approved. Depending on the decision:

If approved: a loan approval letter is sent, and a sub-process is triggered (represented by the rectangle with a "+" symbol inside), which is the creation of the loan contract. This is what identifies it as a BPMN “sub-process.”

If rejected: a rejection letter is sent.

In both cases, the process ends after customer notification.

Evaluation of answer options:

A: Incorrect — the verification steps occur before the loan status is determined.

B: Correct — the “Create the loan contract” activity has a “+” symbol, indicating a sub-process.

C: Incorrect — the parallel gateway means these tasks are executed concurrently, not sequentially.

D: Incorrect — all review activities are mandatory prior to application review.

Therefore, B is the correct answer.

UX context analysis evaluates the environment and conditions in which users interact with a product. This includes:

External conditions: lighting, noise, device constraints

Psychological conditions: cognitive load, stress, motivation

These factors influence usability, accessibility, and overall experience.

Option A is correct as it reflects the essence of UX context analysis — understanding the broader user environment to inform design and testing.

Other options:

B describes personas, which are user archetypes used for behavior modeling — more aligned with user profiling.

C focuses on competitor analysis — useful for inspiration, not context analysis.

D involves use cases and workflows — useful for behavior modeling, but not specifically context analysis.

Answer: A. External conditions and psychological conditions are analyzed to derive design decisions

==================

Acceptance Test-Driven Development (ATDD) is a collaborative approach in which acceptance criteria are defined early, often before implementation starts. Business process models (e.g., BPMN) and business rule models (e.g., DMN) are essential tools to formalize how the system should behave under various conditions.

In ATDD, these models provide a structured representation of system workflows and decision logic, which can then be used by testers and stakeholders to derive or generate acceptance tests. This ensures that testing is aligned with actual business processes and requirements.

Option C is correct because it aligns with the purpose of ATDD: to use business models as a foundation for deriving acceptance tests in collaboration with business analysts, testers, and developers.

Other options:

A is incorrect — models are created as part of the project, not necessarily before it starts.

B is incorrect — models support and clarify acceptance criteria; they do not replace them.

D is incorrect — models are maintained as living documentation, especially in agile and iterative approaches.

Answer: C. In an ATDD approach, testers use business process and business rule models to generate acceptance tests.

Beta testing is a type of acceptance testing performed by end users in a real-world or production-like environment. It is especially relevant for cloud-based and SaaS platforms where widespread feedback is required before release.

Option B is correct because SaaS platforms often release features to a subset of users (beta users) to test the software under actual operating conditions, get feedback, and fix any defects that were not found during internal testing. This allows vendors to validate functionality, performance, and usability in diverse environments.

Other options:

A: Beta testing is not limited to Commercial Off-the-Shelf (COTS) software.

C: Incorrect — beta testing is a form of acceptance testing, not a separate unrelated technique.

D: Incorrect — beta testing and acceptance testing overlap, but they are not synonyms; the terminology does not change based on the development approach (Agile or not).

Answer: B. Beta testing is often used for acceptance testing of Software as a Service (SaaS) platforms