Free CTFL-AT Exam Dumps

Question 11

Which of the following statements is FALSE regarding early and frequent feedback?

A. Early feedback decreases the amount of time needed for system testing.
B. Early feedback promotes early discovery and resolution of quality problems.
C. Early feedback provides the Agile team with information on its productivity.
D. Early feedback helps to deliver a product that better reflects what the customer wants.

Correct Answer:A
Early and frequent feedback is one of the core values of Agile development. It helps the Agile team to deliver features with the highest business value first, to discover and resolve quality problems as soon as possible, to provide information on the team’s productivity and progress, and to ensure that the product meets the customer’s expectations and needs. However, early feedback does not necessarily decrease the amount of time needed for system testing, as system testing is still an important activity in Agile projects to verify the integration and functionality of the whole system. Early feedback may reduce the number of defects found in system testing, but it does not eliminate the need for system testing. References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 10; ISTQB Agile Tester Sample Exam2, question 11.

Question 12

Which of the following is a risk that continuous integration introduces?

A. Teams sometimes over-rely on unit tests and exclude some important system and acceptance tests.
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. Developer's workload is increased, which can result in a reduction of output.

Correct Answer:B
Continuous integration is a practice of integrating code changes frequently and automatically into a shared repository, and running automated tests to verify the integration. Continuous integration can introduce some risks to the testing process, such as:
✑ Testers sometimes have too many builds to test, which reduces the quality of testing. This can happen when the code changes are too frequent or too large, and the testers do not have enough time or resources to test each build thoroughly. This can lead to missed defects, incomplete test coverage, and reduced confidence in the product quality.
✑ Testers sometimes have to deal with unstable or broken builds, which affects the testability of the product. This can happen when the code changes introduce errors or conflicts that cause the build to fail or malfunction. This can waste the testers’ time and effort, and delay the feedback cycle.
✑ Testers sometimes have to cope with changing requirements and priorities, which affects the test planning and execution. This can happen when the stakeholders or customers provide new or modified requirements or feedback during the development cycle. This can require the testers to adapt their test strategy, test cases, and test data accordingly, and to balance the testing of new features and regression testing of existing features. References: ISTQB® Foundation Level Agile Tester Syllabus1, Section 2.2.3, page 14; ISTQB® Glossary of Testing Terms2, version 4.0, page 15.