ISQI ISTQB Certified Tester - Foundation Level Extension - Agile Tester - CTFL-AT무료 덤프문제 풀어보기

A. Each of the four testing quadrants (Q1, Q2, Q3, and Q4) contains different test types and test levels, and these quadrants are numbered to describe the order in which the associated test types and test levels shall be performed in an Agile project (Q1 first, Q4 last)

B. Each of the four testing quadrants (Q1, Q2, Q3, and Q4) contains different test types and test levels, and these quadrants can be used by Agile teams and other stakeholders to ensure that all important test types and test levels are included in an Agile project

C. Each of the four testing quadrants (Q1, Q2, Q3, and Q4) contains different test types and test levels, and these quadrants are numbered to describe the risk level associated with the test types (Q1 = least risky, Q4 = most risky)

D. Each of the four testing quadrants (Q1, Q2, Q3, and Q4) represents a different test level (Q1 = Unit, Q2
= Integration, Q3 = System, and Q4 = Acceptance) and describes the different test types that shall be performed by Agile teams in that test level for an Agile project

A. 1, 3, 4

B. 2, 4, 5

C. 1, 2, 5

D. 2, 3, 4

A. Developer's workload is increased, which can result in a reduction of output.

B. Testers sometimes have too many builds to test, which reduces the quality of testing.

C. Teams no longer have the ability to run manual tests, as all tests must be automated.

D. Teams sometimes over-rely on unit tests and exclude some important system and acceptance tests.

A. Tools that generate data to populate an application's database

B. Continuous integration and build distribution tools

C. Tools that capture and log activities performed on an application during its use

D. Application lifecycle management (ALM) and task management tools

A. A user manual.

B. Usability testing test results.

C. Acceptance testing entry criteria.

D. The released product.

A. Assign testers to be members of the Agile team, but ensure the testers report to a different manager than the developers.

B. Share the Test Strategy with the Agile development team, but not the details of the Test Cases.

C. Co-locate only some of the testers with the Agile development team, while the rest of the testers are in a different location.

D. Locate the team that develops the test automation framework in a different location to the Agile development team.

A. Metrics such as burndown charts, velocity, and number of stories completed could be effectively used during Agile retrospectives for process improvement

B. An Agile retrospective should be held at the end of an iteration only when the number of story points completed by the team in that iteration is lower than the team velocity

C. Agile retrospectives should focus exclusively on improving negative aspects, without wasting time in discussions on what worked well during the iteration

D. All of the improvements identified in an Agile retrospective must be implemented as soon as possible during the next iteration

A. Regression risk is reduced when there is a high degree of code changes being applied from one iteration to the next

B. Technical debt is due to manual testing and it cannot be present when the team implements test automation

C. Test automation can help to manage regression risk since it allows the running of regression test suites within each iteration

D. Automated unit tests are generally not run with each code check-in as they take longer to run than automated acceptance tests and could slow down the code check-in process

A. A small child may try to steam milk. Probability: High. Impact: Low

B. Operators will not read the instructions and will try various switches and buttons until something works.
Probability: Low. Impact: Low

C. An untrained customer will attempt to use the coffee machine. Probability: High. Impact: High

D. The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High