Exhibit B is the only state transition diagram that matches the text description of Acme’s elevator door rules. It shows that the doors can transition between four states: Opened, Closing, Closed, and Opening. The transitions are triggered by either commands (open or close) or sensors (opened or closed). The diagram also shows that the open command can reverse the closing state, and the close command can reverse the opening state, as specified in the text. The other exhibits do not show the correct transitions or conditions for the elevator door system.  References  =

ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst, page 2

State Transition Testing Technique with Diagrams, section “State Transition Diagram”

State Transition Testing - Tutorialspoint, section “State Transition Diagram”

A usability review is a technique that evaluates the usability of a system or product based on a set of criteria or heuristics, without involving the actual users. It can be performed by experts or peers, and it can identify potential usability problems and suggest improvements. A usability review is suitable for situations where the availability of users is limited or impractical, and it can provide quick and low-cost feedback.  References  =  ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst , page 81, section 5.3.2.2.

The smallest set of test conditions to provide minimum coverage of the boundary values is the one that tests the minimum and maximum values for each category of carpet installation prices, as well as the values that are just above or below the boundaries. Option A covers these values, as it tests the boundary values of 0, 20, and 40 square yards, as well as the values that are one square yard more or less than these boundaries. It also tests the maximum possible value for the carpet area and the value that exceeds it. The other options do not test all the boundary values or have redundant values.  References  =

ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst 1 , page 2

Boundary Value Analysis and Equivalence Partitioning Testing 2 , section “Boundary Value Analysis”

Equivalence Partitioning Method 3 , section “Example 1: Equivalence and Boundary Value”

The requirement states that the system shall allow cash advances of  at least  200 Euros, but it does not specify the maximum amount or the conditions for different cards. This could lead to confusion, inconsistency, and errors in the system’s functionality and testing. The requirement should be more precise and define the exact limits and rules for each card type and scenario.  References  =  ISTQB Advanced Level Test Analyst Syllabus 2019 , section 2.1.1;  Requirement Analysis Templates & Techniques , section “Requirement Analysis Best Practices”.

Use cases are a test basis that describe the interactions between the users and the system in terms of scenarios. Use cases capture the functional requirements and the expected outcomes of the system. By visiting locations, spending time with expert users, and walking through their scenarios, the test analyst is using use cases as the test basis. However, use cases do not provide enough information to validate that the transactions are realistic, such as the prices, discounts, taxes, and fees involved in the car buying process. This information is still missing and needs to be obtained from other sources, such as the business rules or the data model.  References  =

ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst 1 , page 2

Use Case Testing - Tutorialspoint 2 , section “Use Case Testing”

Use Case Testing: A Complete Guide 3 , section “What is Use Case Testing?”

The minimum acceptable level of coverage for this use case is to cover all the scenarios and their combinations. Therefore, we need at least one test case for each of the following:

Basic scenario single-sided to single-sided

Alternative single-sided to double-sided

Alternative copy of a set

Alternative copy using the automatic document feeder

Error no paper in paper tray

Error paper jam

Error out of staples  References  =  ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst , page 63, section 4.4.2.2.

State transition testing is a technique that models the behavior of a system as a finite number of states and the transitions between them. It is suitable for testing systems that have different outcomes depending on the previous history of inputs and events. In this case, the ATM system has different states depending on whether the user has entered a valid or invalid PIN code, and how many times they have tried. 1-switch coverage is a criterion that requires testing all possible pairs of transitions from one state to another. This can help to find failures that occur when the system changes from one state to another, or when the system does not change state when it should. For example, 1-switch coverage would test the following scenarios:

User enters a valid PIN code on the first try and requests a cash advance (valid transition from unauthenticated to authenticated state)

User enters an invalid PIN code on the first try and then a valid PIN code on the second try and requests a cash advance (valid transition from unauthenticated to authenticated state after one invalid attempt)

User enters an invalid PIN code on the first and second try and then a valid PIN code on the third try and requests a cash advance (valid transition from unauthenticated to authenticated state after two invalid attempts)

User enters an invalid PIN code on the first, second, and third try and the system rejects the card (valid transition from unauthenticated to rejected state after three invalid attempts)

User enters a valid PIN code on the first try and then requests a cash advance twice (invalid transition from authenticated to authenticated state without inserting the card again)

User enters a valid PIN code on the first try and then removes the card and inserts it again and requests a cash advance (invalid transition from authenticated to unauthenticated state without entering the PIN code again)

References  =  ISTQB Advanced Level Test Analyst Syllabus 2019 , section 3.2.3;  How to Design Test Cases Using State Transition Testing Technique? ;  0 and 1 - Switch Coverage in State Transition Testing?

Low-level test cases are more suitable for testing software that controls the braking mechanism for commuter trains, as they provide more detail and specificity for verifying the functionality and safety of the system 1 .  Low-level test cases also use predefined data, which is more reliable and consistent than tester-created data, and can be easily traced to the test conditions and requirements 2 .  High-level test cases are more abstract and vague, and may not cover all the possible scenarios and risks involved in testing such a critical system 3 .

References  =  1 :  Test Case Design: a Guide for QA Engineers With Examples   2 :  How to Write Test Cases in Software Testing with Examples   3 :  Test Case vs Test Scenario – Difference Between Them

The correct answer is D. Automate the testing for the credit card exploratory tests so they can be used for confirmation testing after the defect is fixed.

A. Enter your exploratory test cases with detailed test steps into the Test Management System

This is incorrect because entering the test cases into the Test Management System is not enough to document and track the exploratory testing process. The test cases should also include the expected results, actual results, and defects found during the testing. Moreover, the test cases should be organized into a clear and logical structure that reflects the test charter and scope.

B. Close the session and start a new session with a new charter

This is incorrect because closing and starting a new session with a new charter would mean losing all the information and data collected during the previous session. This would make it difficult to resume and continue the testing process from where it left off. Instead, it would be better to use a consistent and stable session with a single charter that covers all the requirements and features of the system.

C. Continue the session and conduct the testing for debit cards

This is incorrect because continuing the session and conducting only one type of card (debit) would not provide a comprehensive coverage of all possible scenarios and outcomes of accepting credit cards. It would also limit the scope of testing to only one aspect of payment processing, which may not reflect all the business rules, validations, exceptions, or integrations involved in this domain.

D. Automate the testing for the credit card exploratory tests so they can be used for confirmation testing after the defect is fixed

This is correct because automating some or all of the exploratory tests can help to save time, effort, and resources by reducing manual effort and increasing efficiency. It can also help to improve accuracy, consistency, and reliability by eliminating human errors and biases. Moreover, automating some or all of the exploratory tests can enable them to be reused for confirmation testing after fixing any defects found during exploratory testing. Confirmation testing is a type of functional testing that verifies that all requirements are met by performing regression tests on previously tested functionality 1 .

 System integration testing (SIT) is a type of testing that verifies the interactions and functionality of different components or systems within a larger system. The developers, who are responsible for developing and integrating the components or systems, need to understand the tests to review them for accuracy, completeness, and feasibility. The auditors, who are responsible for ensuring the compliance and quality of the system, need to understand the tests to approve them for execution and reporting.  References  =

ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst 1 , page 2

System Integration Testing: A Complete Guide 2 , section “Who Performs System Integration Testing?”

System Testing vs Integration Testing: Key Differences 3 , section “What is System Integration Testing?”