The correct answer is C. All the expected environments and combinations.

All the expected environments and combinations

Interoperability testing should target all the expected environments and combinations that the system will interact with in the real world.This will ensure that the system can function correctly and reliably with different hardware, software, network, and external factors that may affect its communication and compatibility with other systems1.

References=

• ISTQB Certified Tester Advanced Level Syllabus Test Analyst2, Section 3.2.2 Interoperability
• ISTQB Test Analyst Syllabus and Study Guide3, Section 3.2.2 Interoperability
• A Simple Guide to Interoperability Testing (with Examples)4, Section 2. How to do Interoperability testing

Experience-based test techniques rely on the tester’s knowledge, intuition, and creativity to design and execute tests. They are useful when there are no or poor specifications, limited time, or high-risk areas. Examples of experience-based test techniques are error guessing, exploratory testing, and checklist-based testing. References = ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst, page 67, section 4.5.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?

In a keyword-driven test automation approach, the Test Analyst is responsible for defining the keywords that represent the actions and expected outcomes of the test cases. The keywords are then implemented by a developer or a tool as reusable functions or scripts that can be executed by the test automation framework. For example, the Test Analyst can define keywords such as “transfer”, “check balance”, “verify balance”, etc. for the account transfer user story. These keywords can then be used to design test cases in a data-driven or table-driven format, such as:

Table

Keyword

Parameter 1

Parameter 2

Parameter 3

transfer

Lars

Ann

150

check balance

Ann

-

150

verify balance

Ann

-

150

transfer

Tim

Ann

300

check balance

Ann

-

450

verify balance

Ann

-

450

References = Keyword Driven Testing Framework with Example (Section 1 and 2), What is Keyword Driven Testing: A Detailed Tutorial With Examples (Section 1 and 2), ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst (Section 4.2.1 and 4.2.2)

Testing pairs of combinations is a technique that reduces the number of test cases by testing only two factors at a time, instead of testing all possible combinations. Testing pairs of combinations is based on the assumption that most defects are caused by interactions of at most two factors. Testing pairs of combinations can be applied to this problem using the installation environments, which are the browsers, the operating systems, and the languages. By using testing pairs of combinations, the number of test cases will be lower than exhaustive testing, which would require testing every combination of factors. The formula for calculating the number of test cases for testing pairs of combinations is:

N = P * (P - 1) / 2

where N is the number of test cases, and P is the number of values for each factor. In this problem, P is 4, as there are four browsers, four operating systems, and four languages. Therefore, the number of test cases for testing pairs of combinations is:

N = 4 * (4 - 1) / 2 N = 4 * 3 / 2 N = 12 References =

• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2
• Pairwise Software Testing - GeeksforGeeks2, section “Introduction”
• Pairwise Testing: A Best Practice That Isn’t3, section “Pairwise Testing”

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-costfeedback. References = ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst, page 81, section 5.3.2.2.

The correct answer isB.The information exchange between each system and its environment.

The information exchange between each system and its environment

The information exchange between each system and its environment refers to the compatibility and functionality of the systems with respect to the hardware, software, network, and other external factors that may affect their interaction.This type of testing is important to ensure that the systems can operate smoothly and reliably in different scenarios and conditions1.

References=

• ISTQB Certified Tester Advanced Level Syllabus Test Analyst2, Section 3.2.2 Interoperability
• ISTQB Test Analyst Syllabus and Study Guide3, Section 3.2.2 Interoperability
• A Simple Guide to Interoperability Testing (with Examples)4, Section 2. How to do Interoperability testing

Classification trees are a combinatorial testing technique that allows the tester to represent the data items and their values in a graphical form, and to exclude certain combinations by using constraints or rules. Classification trees can help the tester to visualize and organize the test data, and to generate test cases that cover all relevant combinations of values. The other techniques do not provide a convenient way to exclude certain combinations, or require more complex mathematical calculations. References =

• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2
• Classification Tree Method for Test Design2, section “Classification Tree Method”
• Classification Tree Method - Tutorialspoint3, section “Classification Tree Method”

Risk mitigation is the process of implementing actions to reduce the probability and/or impact of risks1. When you execute the tests in priority order based on the risk ratings, you are performing risk mitigation, as you are trying to prevent or minimize the potential failures and defects in the system2. Risk planning, identification, and assessment are the previous steps in the risk management process, which help to prepare for risk mitigation3.

References = 1: Risk Mitigation – Planning, Implementing, and Monitoring 2: Risk Based Testing Approach for Agile Teams 3: The Ultimate Guide to Risk Based Testing: Risk Management in Software Testing

Pairwise testing is a test design technique that reduces the number of test cases needed to cover all possible combinations of input parameters, by testing only pairs of parameters at a time. It is based on the assumption that most defects are caused by interactions of at most two factors. Pairwise testing is suitable for testing systems that have multiple parameters with discrete values, such as browsers, plug-ins, servers, and operating systems. It can help to find defects that are related to the compatibility and interoperability of the system in different environments. References = ISTQB Advanced Level Test Analyst Syllabus 2019, section 3.2.3; Pairwise Testing or All-Pairs Testing Tutorial with Tools and Examples; Test Design Techniques, section 5.4.

The use case only describes the normal or happy path scenario, where the user performs a successful cash withdrawal. However, it does not consider any alternative or exceptional scenarios, such as invalid card, incorrect PIN, insufficient balance, network failure, etc. These scenarios are important to test the robustness and reliability of the ATM system, and should be included in the use case specification. References = ISTQB Certified Tester Advanced Level Syllabus Test Analyst, Section 2.2.1, Use Case Testing1; ISTQB Advanced Level Test Analyst (CTAL) Exam Study Guide, Section 2.2.1, Use Case Testing2

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”

The test conditions are the inputs and outputs that are used to define the scope and objectives of testing. They should be understandable by business stakeholders because they affect their expectations and satisfaction with the software product. Business stakeholders can provide valuable feedback to the test analyst on the test conditions, such as clarifying any ambiguities, suggesting any changes, or identifying any gaps or risks. References =

• ISTQB Certified Tester Advanced Level Overview of Syllabi1, page 10
• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst2, page 2
• Who are the stakeholders in software testing? How to identify them?3, section “Stakeholders in testing will require attention”

Defect taxonomies are categorized lists of defects that can be used to identify and prevent common types of errors in software development and testing. They can also be used to design test cases that target specific defect types, such as security vulnerabilities. Therefore, using a list of known defect types to penetrate the security of computer systems is an example of the use of defect taxonomies. References = Defect Taxonomies - The Practical Guide to Defect Prevention (Chapter 10), Using Defect Taxonomies for Testing Requirements, Defect Based Approach using Defect Taxonomy, Requirements-based testing with defect taxonomies

Pairwise testing is a technique that tests all possible discrete combinations of each pair of input parameters. In this case, there are two main categories: Colour and Shape. Under Colour, there are three subcategories: Red, Blue, and Green. Under Shape, there are two subcategories: Triangle and Circle. There is an additional category under Triangle labeled Size of triangle, with two subcategories: Small and Large. To test all pairs of these parameters, we need to use a tool or an algorithm that can generate the optimal test cases. One such tool is Pairwise.org, which can produce the following test cases:

Table

Colour

Shape

Size of triangle

Red

Triangle

Small

Blue

Circle

-

Green

Triangle

Large

Red

Circle

-

Blue

Triangle

Small

Green

Circle

-

Red

Triangle

Large

Blue

Triangle

Large

These eight test cases cover all pairs of parameters, such as Red-Triangle, Red-Small, Blue-Circle, etc. Therefore, the answer is B. 8. References = Pairwise Testing or All-Pairs Testing Tutorial with Tools and Examples, Pairwise Testing - What It Is, When & How to Perform?, All-pairs testing - Wikiwand, ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst (Section 3.2.3)

Experience-based testing is a technique that relies on the tester’s intuition, skills, and past experiences to create test scenarios. However, this approach makes it challenging to measure and assess the test coverage, as there is no clear criteria or method to determine which areas of the software have been tested and which have not. This can lead to gaps in the testing process and potential risks of missing defects1

References =

• ISTQB Advanced Level Test Analyst Syllabus 2019, Section 3.2.3.1, page 462
• Experience Based Testing: What It Is and Why It Matters?3
• Experience based testing technique - ToolsQA4

The correct answer isD.The story contains more than one item of functionality.

The story contains more than one item of functionality

A user story should be small, simple, and focused on one item of functionality that delivers value to the user. This story combines two items of functionality: querying the balance and withdrawing money. These items could be separated into two different stories, each with its own acceptance criteria and priority.This would make the stories easier to understand, estimate, test, and deliver1.

References=

• User Stories | Examples and Template | Atlassian2, Section User story best practices
• ISTQB Certified Tester Advanced Level Syllabus Test Analyst3, Section 2.1.1 Test Analyst Tasks in the Test Process
• ISTQB Test Analyst Syllabus and Study Guide4, Section 2.1.1 Test Analyst Tasks in the Test Process

The correct answer isD.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 functionality1.

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 system1. 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 requirements2. 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 system3.

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 level of detail and documentation required for test cases in the project depends on the type of application under test, the standards followed by the organization, and the maturity of the development process. For a web application that is undergoing frequent changes, it is advisable to use high-level test cases that describe the main features and functionalities from a user’s perspective, and low-level test cases that provide more details and specifications for each feature. High-level test cases can be supported by low-level test cases to ensure traceability between the requirements and the test scenarios, as well as to facilitate future changes or enhancements. Low-level test casescan also be reviewed and updated by the end-users who have extensive domain knowledge and are involved in the project. References =

• ISTQB Certified Tester Advanced Level Overview of Syllabi1, page 10
• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst2, page 2
• Test Documentation in Software Testing (Example)3, section “Best practice to Achieve Test Documentation”

Equivalence partitioning is a technique that divides the input domain into classes of data that are expected to behave similarly. The test sets should cover one value from each equivalence class, as well as the boundary values between them. The equivalence classes for the metro fare system are:

• Before 9:30 am (full fare)
• Between 9:30 am and 5:00 pm (saver ticket)
• Between 5:00 pm and 7:00 pm (full fare)
• After 7:00 pm (saver ticket)

The boundary values are 9:30 am, 5:00 pm, and 7:00 pm. Therefore, the test set that provides the best equivalence partitioning coverage is the one that includes one value from each equivalence class and the boundary values, which is option D. References =

• ISTQB Certified Tester Advanced Level Syllabus Technical Test Analyst1, page 2
• Boundary Value Analysis and Equivalence Partitioning Testing2, section “Equivalence Partitioning”
• Equivalence Partitioning Method3, section “Example 1: Equivalence and Boundary Value”