ISTQB CTFL-AT (3)

FA-3.1.1 K1 - Select ONE option.

Which of the following statements about Test Driven Development (TDD) is FALSE?

• TDD is a ”test first” approach to develop reusable automated tests

• The TDD cycle is continuously used until the software product is released

• TDD helps to document the code for future maintenance efforts

• The result of TDD are test classes used by the developer to develop test cases

FA-3.1.2 K1 - Select ONE option.

What does the term ‘Test Pyramid’ refer to and illustrate situations for?

• The team’s testing workload increases from sprint to sprint

• The backlog size, and thus the number of tests, decreases

• The number of automated unit tests is higher than the number of automated tests for higher test levels

• The number of automated tests in place increases from sprint to sprint

FA-3.1.3 K2 - Select ONE option.

Which of the following demonstrates effective use of the testing quadrants?

• When communicating test ideas, the tester can refer to the matching test quadrant, so that the rest of the team will better understand the purpose of the test.

• The tester can use the types of tests described in the testing quadrants as a coverage metric, the more tests covered from each quadrant, the higher the test coverage.

• The team should pick a number of tests expected from each quadrant, and the tester should design and execute those tests to ensure all levels and types of tests have been executed.

• The tester can use the testing quadrants during risk analysis; with the lower level quadrants representing lower risk to customer.

FA-3.1.3 K2 - Select ONE option.

Given the following user stories: “As a bank teller, I can easily navigate through the system menu and links, and find the information I am looking for” “For all users, the system must display all queries in less than 2 seconds, 90% of the time”

And the associated test cases:

TC1: Login as bank teller. Enter customer ID. Verify that the customer transaction history is easy to find, and that navigating through the menus is intuitive.

TC2: Login as bank teller: Enter customer Name. Verify that the customer accounts are easy to find and that navigating through the menus is intuitive.

TC3: Simulate expected traffic on system and validate the time for customer transaction history to display is less than 2 seconds.

Which test quadrants would the above test cases be part of?

• Q1 unit level, technology facing & Q2 system level, business facing

• Q2 system level, business facing & Q3 system or user acceptance level, business facing

• Q3 system or user acceptance level, business facing & Q4 system or operation acceptance level, technology facing

• Q2 system level, business facing & Q4 system or operation acceptance level, technology facing

FA-3.1.4 K3 - Select ONE option.

At the beginning of the 5 th iteration of a project, a new requirement was introduced to support a new type of browser. The tester realizes that the existing test automation framework and scripts will not support the new type of browser.

What is the best course of action for the tester on this team to take?

• The tester should notify the team that they are planning on working extra hours throughout the next 2 sprints in order to update the existing test automation framework and scripts to support the new type of browser so as not to disturb the existing sprint plan.

• The tester will notify the team of the issue. A risk analysis is done, and the team decides that regression testing must be performed on the new type of browser in addition to the other supported browsers. The tester will update the sprint plan by adding tasks to modify the framework and scripts to support the new type of browser.

• The tester does some research and concludes that the risk is low that any new defects would be introduced in the new type of browser that have not already been found in other supported browsers. The tester continues with the existing sprint plan and makes no changes to test automation framework or scripts.

• The tester will stop what they are doing, design specific tests for compatibility testing of the new type of browser and communicate with the team that any other testing work for the sprint will have to be pushed to the next iteration.

FA-3.2.1 K3 - Select TWO option.

Given the following results from a product risk analysis that occurred at the beginning of an iteration:

 User story 1 (Performance): likelihood: high, impact: high

 User story 2 (Security): likelihood: high, impact: high

 User story 3 (Functional): likelihood: medium, impact: high

 User story 4 (Functional): likelihood: high, impact: medium

 User story 5 (Compatibility): likelihood: low, impact: low

 User story 6 (Recoverability): likelihood: low, impact: low

Which of the following describes best what the team should do with this information?

• Move onto planning poker session to estimate effort for user stories and determine what can be done in the current iteration, and what needs to be added to backlog.

• Remove user stories 5 and 6 from the current iteration and move to a later iteration

• Because of the number of high likelihood, high impact risks slotted for this iteration, the team has no choice but to extend the timeframe of the iteration by 2 weeks.

• The team should collaborate on effective ways to mitigate the high likelihood, high impact risks.

• The team should plan to complete all items in the current sprint, but save the lower risk items for the end of the sprint, and only test these items if there is time.

FA-3.2.2 K3 - Select ONE option.

Given the following user story: “As the president, any data I upload should not be viewable by any other user of the system” During the first poker planning session, the following story points were given based on risk, effort, complexity, and proper extent of testing:

Customers: 5

Developers:5

Testers: 20

What is the best outcome following this planning session?

• Because the customer’s and developer’s size estimates match, the team can be confident that this estimate is good and should move onto the next user story.

• The team should hold a conversation to understand why the testers felt this user story was significantly more work. Another round of the planning poker session should occur following that discussion.

• Because the customer owns the system in the end, the customers’ estimates should be taken as correct when there is a conflict.

• The poker planning sessions should continue until all estimated story points are an exact match between customers, developers, and testers.

FA-3.3.1 K3 - Select ONE option.

An agile team is assigned to a project to update an existing medical device to newer technologies. Since the last release of the existing medical device, a new version of the medical device standard has been released. User access to the device is changing and will be documented in user stories. Based on this information, and in addition to the user stories, which of the following would best provide relevant information to support your testing activities?

i Updated version of standards document for medical system.

ii Existing defects or typical defect areas in existing system.

iii Obsolete user access test cases and results for existing application.

iv Performance metrics for existing application.

v Defects logged during other similar conversion projects for medical devices.

• i, ii, iii, iv

• ii, iv, v

• i, ii, v

• All of the above

FA-3.3.2 K2 - Select ONE option.

Which alternative is the BEST description of when to stop testing (release criteria) in an agile project?

• All test cases have been executed

• The probability of remaining faults has been reduced to a level that can be accepted by the customer

• The achieved test coverage is considered enough. The coverage limit is justified by the complexity of the included functionality, its implementation, and the risks involved

• The iteration/sprint is finished

FA-3.3.2 K2 - Select TWO option.

Which of the following are examples of testable acceptance criteria for test related activities?

• Structure based testing: White box testing in addition to black box testing is used

• System testing: At least 80% of functional regression tests are automated.

• Security testing: A threat risk analysis scan is completed with no faults identified.

• Performance testing: The application is responding in a reasonable amount of time with 5000 users.

• Compatibility testing: The application is working on all major browsers.