In the recent past, you have learned that test automation just using capture & playback tooling, possibly enhanced with some test programming, has limitations. For the next banking project, that will be run using Agile methods, you want to implement a keyword-driven test automation approach. You have already started to define some high-level test cases for the account transfer user story:
TC 1 transfer € 150 from Lars to Ann, verify Ann's balance to be € 150
TC 2 transfer € 300 from Tim to Ann, verify Ann's balance to be € 450
In the context of implementing the keyword-driven test automation approach, which of the following activities should now be conducted by the Test Analyst?

• A. Work together with a developer to define a test automaton architecture
• B. Select a tool to support keyword-driven testing
• C. Define keywords to be implemented, eg, check balance.
  B Design test navigation scripts.

You have been given a test charter to conduct exploratory testing for accepting credit and debit cards for an e-commerce system. You started with the credit cards and you have found that, valid or invalid, they are never accepted. You have logged this as a defect. What should you do now?

• A. Continue the session and conduct the testing for debit cards
• B. Automate the testing for the credit card exploratory tests so they can be used for confirmation testing after the defect is fixed.
• C. Enter your exploratory test cases with detailed test steps into the Test Management System
• D. Close the session and start a new session with a new charter

You are building tests using the classification tree below. You have been told that pairwise testing would be a good approach to this problem. When you apply the pairwise testing technique what would be the expected effect on the number of test cases?

• A. Pairwise testing would not be possible because equivalence partitions have not been defined
• B. Pairwise testing would not be applicable for this problem
• C. Pairwise testing will require fewer test cases than exhaustive testing
• D. Pairwise testing will have no effect on the number of test cases

You have been working as a Test Analyst for a customer-facing application that is critical to the reputation of your company. You have worked with business users to create use cases and captured a variety of scenarios, including both main and alternate paths. You have managed to create a suite of use cases that portrays a realistic usage model of the system.
Because of this, you will also be able to use these use cases for what other type of testing?

• A. Performance testing
• B. FMEA
• C. Defect-based testing
• D. Experience-based testing

Consider the following use case for a "pick your dog" application called "Shelter Search".
1. The user enters his zip code
2. The user enters his breed choice
3. The system displays the list of shelters within a 30 mile radius of the user's zip code which have the selected breed
4. The user selects a shelter
5. The system displays the available appointment times for the next seven days
6. The user selects an appointment time
7. The system records the user's appointment
8. The system displays the address and phone number for the selected shelter
9. The system confirms the user's appointment
Alternate Paths:
1a. The user cancels out
2a. The user doesn't find their choice
2b. The user enters their breed choice in the "other" text field
3a. No shelters are found with the selected breed
3b The user is prompted to enter a larger search radius
4a. The user cancels out
5a. There are no appointments available in the next seven days
5b. The user is asked if they want to search the next 30 days
6a. The user cancels out
7a. The system cannot record the appointment
7b. The system displays an error
8a. The system cannot display the address
8b. The system displays an error
How many test cases will be needed to achieve minimum coverage of this use case?

• A. 9
• B. 7
• C. 14
• D. 1