Free CTFL-AT – ISTQB Certified Tester - Foundation Level Extension - Agile Tester Practice Test Question

Select an option, then click Submit answer.

• ○

  1, 3, 5

• ○

  1, 2, 3

• ○

  2, 3, 4

• ○

  1, 2, 4

Select an option, then click Submit answer.

• ○

  Testing carried out informally where no formal test preparation or execution takes place, no recognized test design technique is used and there are no expectations for results.

• ○

  A group of software development methodologies based on iterative incremental development with self-organizing cross-functional teams who cooperate to define requirements and to implement the solution.

• ○

  A framework to describe the software development lifecycle activities from requirements specification to maintenance where test planning of the various test levels is done as soon as the test basis is ready

• ○

  A way of developing software where the test cases are developed, and often automated, before the software under test is developed.

Select an option, then click Submit answer.

• ○

  Acceptance test criteria are 1, 2, 3 and 6

• ○

  Acceptance test criteria are 1, 3, 4 and 5

• ○

  Acceptance test criteria are 2, 4, 5 and 6

• ○

  Acceptance test criteria are 1, 2, 4 and 5

Select an option, then click Submit answer.

• ○

  Risk-based testing fits well in Agile development processes, as risks are analyzed twice - during release and iteration planning.

• ○

  Risk-based testing does not fit well in Agile development processes, as short iterations mandate short test times.

• ○

  Risk-based testing does not fit in Agile development processes, as each iteration focuses on limited parts of the product.

• ○

  Risk-based testing fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories.

Select an option, then click Submit answer.

• ○

  Having at least once a day an automated build and test process that detects integration errors early and quickly.

• ○

  Avoiding requirements misunderstandings which may not have been detected until later in the development cycle when they are more expensive to fix.

• ○

  Capitalizing on the combined skills of business representatives, testers and developers working together to contribute to project success.

• ○

  Reducing the involvement of business representatives because of the increased communication and collaboration between testers and developers.