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

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.”

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.

Acceptance criteria describe what the system must do to fulfill a requirement from the user or business perspective. They must be observable, testable, and relevant to the business outcome or expected behavior.

In this scenario, the user story is about monitoring blood pressure and receiving alerts for excessive pressure. The acceptance criteria should focus on system behavior, thresholds, and how alerts are triggered based on user settings.

Option D is not a good acceptance criterion because:

It specifies a technical implementation detail (JavaScript framework), which is not the concern of acceptance testing.

Acceptance criteria should not prescribe how the system is built, but what it must do from a business or user point of view.

Other options (A, B, and C) all reflect testable and behavior-focused outcomes linked to the user story’s goal.

Answer: D. The system should be developed using JavaScript framework to allow fast response times

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.

Exploratory testing is a dynamic testing technique where learning, test design, execution, and interpretation occur simultaneously. It is especially useful when detailed requirements are unavailable or when testers rely on experience and intuition.

A is correct: Exploratory testing combines exploration, learning about the product, designing and executing tests on the fly, and interpreting the results — all within the same session.

E is also correct: Exploratory testing usually starts with a high-level test charter that defines the mission, objectives, or focus area for the session. It may not define specific test conditions, but it outlines the scope and intent.

Other options:

B: Not accurate — while timeboxing is used, exploratory testing typically relies on charters and experience rather than detailed product risk analysis to prioritize.

C: Incorrect — exploratory testing is not about refining acceptance criteria; that’s part of ATDD.

D: Partially true but misleading — good business domain knowledge helps, but understanding the functionality is also important in exploratory testing.

Answer: A and E

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.

Security requirements specify how a system should handle access control, data protection, confidentiality, integrity, and authentication. In acceptance testing, validating that users cannot access data or functions they are not authorized for is a critical test objective when dealing with security.

Option D is correct because it directly relates to access control — a fundamental aspect of security. Ensuring that “normal users shall have restricted access to private data” reflects both a security requirement and a condition that must be tested for compliance.

Other options:

A relates to performance (response time).

B refers to architecture or platform (web-based system).

C is about UI design and usability (style compliance).

Only D addresses security specifically.

Answer: D. Normal users shall have restricted access to private data.

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

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

This question is about combining Business Process Model and Notation (BPMN) and Decision Model and Notation (DMN) to design test cases for acceptance testing. The BPMN diagram outlines the customer checkout flow with a decision on whether a loyalty card is used, followed by a card scan that may trigger a discount check. The DMN decision table defines the logic for determining the discount percentage based on the number of loyalty points.

From the DMN:

<1000 points ⇒ 0% discount

1000–3000 points ⇒ 5% discount

3000 points ⇒ 5% discount

Option D correctly states that a customer with more than 500 points could be eligible for a 5% discount — but only if the number of points exceeds 1000. Since 500 does not meet the 1000 threshold, it appears this statement could be problematic at first glance. However, interpreting the spirit of the question, Option D is the only one matching the correct maximum discount scenario.

Let’s clarify each option:

A is incorrect: >1000 points qualifies for 5%, not 0%.

B is incorrect: 3% is not defined anywhere — DMN has 0% or 5%.

C is incorrect: again, 3% does not exist in the table.

D is acceptable in principle, assuming a typo (i.e., it should be “more than 1000” instead of 500); however, if taken literally, it would be incorrect.

However, given the options, D is the only one aligning with actual DMN output for >1000 loyalty points, despite the inaccurate lower limit.

Answer: D. These models can be used to generate a test case for a 5% reduction if the customer has more than 500 loyalty points

(If the literal error in Option D is to be treated strictly, the correct answer would be “none of the above,” but in context of typical ISTQB-style questions, D is the best fit.)