Font size
WorksheetsISTQB CTFL-AT (2)
Total questions: 12
Worksheet time: 13mins
FA-2.1.1 K2 - Select ONE option.
Which of the following test activities is typically done during agile projects, but is not as common on traditional projects?
Testers write detailed test plans so all team members can understand what will be tested during each iteration.
Testers are heavily involved in the creation of automated test cases which are then used to verify the implementation of the requirements.
Testers decide entry and exit criteria for each test level.
Testers are involved in the development to better understand what needs to be tested.
FA-2.1.2 K2 - Select ONE option.
Consider the following activities:
I. Strict enforcement of system test level entry and exit criteria.
II. Collaboration between tester, developer, and business stakeholders to define acceptance criteria.
III. Functional verification testing of user stories developed in the previous iteration.
Which of the following combination of these activities should occur in an agile project?
ii only
i and ii
ii and iii
iii only
FA-2.1.3 K2 - Select TWO option.
Which of the following statements are true on agile projects?
Testers should work closely with developers while retaining an objective outlook
Test managers do not exist in organizations doing agile development
There is no difference between what testers and developers do on agile projects.
Developers should rely on testers to create the automated regression tests.
A selection of users may perform beta testing on the product after the completion of a series of iterations.
FA-2.1.3 K2 - Select ONE option.
Which of the following statements about independent testing on agile projects is FALSE?
There can be a risk of losing test independence for organizations introducing agile.
Independent testers will find more defects than developers regardless of test level.
Independent testing can be introduced at the end of a sprint
The independent test team can be part of another team.
FA-2.2.1 K2 - Select ONE option.
In an agile project, which of the following would best denote product quality at the end of iteration 6 of a new system release consisting of 8 iterations?
No severity 1 or 2 defects were detected during system testing of iteration 6, which allowed the teams to move into iteration 7
The results of a customer beta test on the iteration 6 software release indicate that the system works correctly and that it has improved productivity.
The agile team has been successfully tracking to estimates, with limited variance showing on the burndown charts for all iterations to date
All story cards in scope for each iteration, up to the current iteration, have been marked as “Done”, but with some technical debt being incurred.
FA-2.2.1 K2 - Select ONE option.
Which of the following is best at showing the team’s progress against estimates?
Burndown charts
Automation logs
The agile task board showing user story and task progress
Defect tracking tools
FA-2.2.1 K2 - Select ONE option.
The business advises during iteration 5 planning that they require changes to the system delivered in iteration 3. Of the following activities, which would need to be done first to minimize the introduction of regression risk when this feature is changed?
Review and update all manual and automated tests impacted by this change to meet the new acceptance criteria.
Write new manual and automated tests for the feature and add them to the regression test suite.
Automate all test cases from the previous iteration and add them to the automated regression test suite.
Increase the amount of test automation around the system to include more detailed test conditions.
FA-2.2.2 K2 - Select ONE option.
Which of the following are reasons why automation is essential within agile projects?
i. So that teams maintain or increase their velocity
ii. To prevent the test team from becoming bored with manual, repetitive tasks
iii. To retest all test cases from previous iterations
iv. To eliminate regression in the product due to high code churn
v. To ensure that code changes do not break the software build
i and iv
i and v
iii and iv
ii and v
FA-2.3.1 K2 - Select ONE option.
In agile projects there is more need for testers to understand and develop test automation scripts than in traditional projects. Of the following:
i. Requirements change daily and have to be regression tested. This rapid change requires automated tests because manual testing is too slow.
ii. The tests should generate feedback on product quality as early as possible. So all acceptance tests should be executed in each iteration, ideally as modifications are made. In practice that can only be realized by automated tests.
iii. Test-First and Continuous Integration Practice require that the regression test suite is executed whenever changed code is checked-in. In practice that can only be realized by automated tests.
iv. Iterations or sprints are of fixed length. The team has to guarantee that all tests can be completely executed at the last day of each iteration/sprint. In practice, that can only be realized by automated tests.
v. Agile projects rely on unit testing rather than on systems testing. Since unit tests cannot be executed manually, all tests have to be automated tests.
i & iii
ii & v
iv & v
ii and iii
FA-2.3.2 K2 - Select TWO option.
Which tasks are typically expected of a tester on an agile project?
i. decide on user acceptance
ii. design, create and execute appropriate tests
iii. schedule defect reports for analysis
iv. automate and maintain tests
v. improve program logic by pair programming
i & iii
ii & iii
ii & iv
ii and v
FA-2.3.2 K2 - Select ONE option.
Which of the following is NOT a typical task performed by the tester within an agile team
To automate tests and maintain them
To mentor and coach other team members
To produce and update burndown charts
To participate in code analyzing activities
Keyword K1 - Select ONE option.
The term “burndown” refers to which of the following?
A chart showing which team members are working the most, and are likely to be under stress
A chart showing the progress of each user story, and when they are likely to be completed
A chart showing the amount of work left to be done, versus the time allocated for the iteration
A chart showing defects that have been fixed, and when the remaining defects are likely to be fixed
