ISTQB Agile Tester Extension Exam Crash Course Part 8
The following user-friendly questions prepared according to different K-Levels are of great help in reviewing your skills before appearing in ISTQB Agile Tester Extension Certification exam as per the latest syllabus.
Set of 10 Questions (Q. 71 to 80) with Explanation in Favour of the Correct Answer
The Correct Answer option has been Hi-lighted in Yellow.
Q. 71: (Level K2) Out of the following which Two are the most popular tools and techniques to communicate the test progress to the team in an Agile project?
A. Agile task board.
B. Test Status report.
C. Daily stand up meeting.
D. Retrospectives.
Explanation in favor of the correct answer:
Option (A) is True – as to provide the detailed visual representation of the whole team’s current status, including the status of testing, teams use Agile task boards.
Option (B) is False – as test status reports are not used for communicating
test progress within the Agile team. They may be used for other metrics.
Option (C) is True – as the daily stand up meetings provide the opportunity for testers to communicate test progress, including issues that may block test progress.
Option (D) is False – as retrospectives are not for status reporting. They are used to discuss topics such as the process, people, organizations, relationships, and tools.
<<<<<< =================== >>>>>>
Q. 72: (Level K2) Match the following tools used in Agile projects with their corresponding use on the bottom:
1. Wiki dashboards.
2. Daily Stand-up meeting.
3. Customer satisfaction survey.
4. Agile Task boards.
i. To know the product quality.
ii. To get team current status.
iii. To generate the status report.
iv. To know the team issues.
A. 1-iv, 2-ii, 3-i, 4-ii
B. 1-iv, 2-i, 3-ii, 4-iii
C. 1-ii, 2-iv, 3-ii, 4-i
D. 1-iii, 2-iv, 3-i, 4-ii
Explanation in favor of the correct answer:
Option (1) matches with (iii) – Wiki dashboards can be used to automatically generate status reports based on test results and task progress.
Option (2) matches with (iv) – In Daily Stand-up meeting issues are communicated so the whole team is aware of the issues and can resolve them accordingly.
Option (3) matches with (i) – Customer satisfaction surveys are used to receive feedback on whether the product meets the customer’s expectation (overall product quality).
Option (4) matches with (ii) – Agile Task boards are used for instant visual representations of the whole team’s current status.
<<<<<< =================== >>>>>>
Q. 73: (Level K2) The Agile team wants to find out the overall product quality at the end of an iteration.
What is the best way of achieving this?
A. The best way is to check with the testers as they should be able to assess quality based on their testing.
B. The best way is to check the burndown chart. If the team has successfully achieved the estimates, then the product quality is good.
C. The best way is to ask the customer to test the product to know whether the system works correctly and meets expectations.
D. The best way is to check the technical debt incurred so fat This will best indicate the product quality.
Explanation in favor of the correct answer:
Option (A) is False – as test results may not necessarily indicate the product quality. It is important to know if the product meets the customer’s expectations.
Option (B) is False – as Burndown charts only show the planned progress and release date together with the actual progress of the user stories which is not an indicator of quality.
Option (C) is True – as customer feedback and working software are key indicators of product quality.
Option (D) is False – as technical debt may not necessarily indicate product quality. It is important to know if the product meets the customer’s expectations.
<<<<<< =================== >>>>>>
Q. 74: (Level K2) What is the best way to measure the Agile team’s progress against the estimates?
A. Test Status reports
B. Burndown charts
C. Number of completed stories in the sprint
D. Test Summary report
Explanation in favor of the correct answer:
Option (A) is False – as the test status report shows the progress of testing and can be used to measure the progress of testing.
Option (B) is True – as Burndown charts show the planned progress and release date together with the actual progress of the user stories.
Option (C) is False – as the number of completed stories will tell the team velocity for that sprint.
Option (D) is False – as the Test Summary report contains the summary of test activities and final test results.
<<<<<< =================== >>>>>>
Q. 75: (Level K2) “Test automation is important to manage regression risk in Agile projects”
Which out of the following TWO reasons support the above statement?
i. To eliminate regression risk due to high code churn.
ii. To ensures that all previous iterations’ stories are tested.
iii. To receive immediate feedback on overall product quality.
iv. So the team can make changes to previously delivered features to meet the customer’s needs.
v. It gives the team more time to spend on the current iteration activities.
A. i and ii
B. iv and v
C. iii and iv
D. ii and v
Explanation in favor of the correct answer:
Statement (i) is False – as automation can reduce the regression risk but cannot guarantee to eliminate all regression risk.
Statement (ii) is False – as it is not feasible to automate all of the tests and it is also not possible to retest/rerun all of the test cases from all of the previous iteration.
Statement (iii) is False – as automated acceptance test results can provide feedback on product quality with respect to the regression since the last build, but they do not provide the status of overall product quality.
Statement (iv) is True – as automation reduces the regression test effort so the team can accept and make changes to previously delivered features to meet the customer’s needs.
Statement (v) is True – as automation reduces the regression test effort so the team can work on tasks from the current iteration
<<<<<< =================== >>>>>>
Q. 76: (Level K2) Out of the following which can be used to reduce regression risk due to high code churn in Agile projects?
A. Automation done for test data generation.
B. Automation done for unit tests.
C. Automation done to compare data outputs.
D. Automation done to restore test environment to baseline.
Explanation in favor of the correct answer:
Automated unit tests will provide rapid feedback on product quality and can reduce the risk of regression. Automation for test data generation, comparing data output and restoring test environment will allow the team to spend more time in developing and testing new features but will not reduce the risk of code chum.
<<<<<< =================== >>>>>>
Q. 77: (Level K2) Which out of the following TWO statements justify the high investment on Automation in Agile projects?
i. Test Automation helps maintain velocity without incurring a large amount of technical debt.
ii. Test Automation helps to detect the defects early in the project cycle.
iii. Automated acceptance test results can provide immediate feedback on overall product quality.
iv. Test Automation gives the testers more time to test new features and functions in the current iteration.
v. Test Automation ensures that all test cases from the previous iterations are tested.
A. i and v
B. i and iv
C. iii and iv
D. ii and v
Explanation in favor of the correct answer:
Statement (i) is True – as changes in each iteration will require more and more regression testing. If automation was not used, then the team’s velocity would be reduced or the Technical debt will increase.
Statement (ii) is False – as this is not a reason to introduce automation on a project.
Statement (iii) is False – as automated acceptance test results can provide feedback on product quality with respect to the regression since the last build but they do not provide the status of overall product quality.
Statement (iv) is True – as automation reduces the regression test effort so the testers can work on other tasks from the current iteration.
Statement (v) is False – as it is not feasible to automate all the tests and it is not possible to retest/rerun all the test cases from all the previous iterations.
<<<<<< =================== >>>>>>
Q. 78: (Level K2) The Agile team has created an automation acceptance test suit to manage regression risk due to frequent changes in the project. This is now part of the continuous integration full system build, what should be the frequency of run?
A. Daily
B. Weekly
C. Each code check
D. At least once in the sprint
Explanation in favor of the correct answer:
Automation acceptance test suit should be run at least daily. To explain further, the automation acceptance test suit should not be run with each code check-in as they take longer to run than automated unit tests and could slow down the code check-in.
<<<<<< =================== >>>>>>
Q. 79: (Level K2) The Agile team is developing the automated build verification tests to provide instant feedback on the software after deployment.
Out of the following which TWO tests should be part of the Automated build verification tests?
1. All tests to cover critical system functionality.
2. All tests which have previously failed
3. All tests from the previous iteration
4. All tests to cover integration points.
A. 2 and 3
B. 1 and 4
C. 2 and 4
D. 1 and 2
Explanation in favor of the correct answer:
Statement (1) is correct – as all tests to cover critical system functionality should be part of the Automated build verification tests to make sure that the build is stable for testing.
Statement (2) is incorrect – as all tests which have previously failed are not necessarily part of the Automated build verification tests.
Statement (3) is incorrect – as all tests from the previous iteration are not necessarily part of the Automated build verification tests.
Statement (4) is correct – as all tests to cover integration should be part of the Automated build verification tests to make sure that the build is stable for testing.
<<<<<< =================== >>>>>>
Q. 80: (Level K2) Out of the following which would need to be done first to minimize the introduction of regression risk when a feature which has already been delivered is changed in the current iteration?
A. The team should increase the amount of test automation to reduce regression risk.
B. Automate all the tests for that feature and add them to the automated regression test suite.
C. The changes should be manually tested now and later added to the automation test suit.
D. Do the impact analysis to find out all of the manual and automated tests impacted by this change to meet the new acceptance criteria.
Explanation in favor of the correct answer:
Option (A) is False – as a review of the changes are required first before making any decision. It is unknown if additional automation is required.
Option (B) is False – as a review of the changes are required first before making any decision.
Option (C) is False – as a review of the changes are required first before making any decision since the tester would not know what new tests would be required for these changes.
Option (D) is True – as this is the initial task to be performed before a decision about any other changes can be made.
Continue to Crash Course Part 9
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.