ISTQB Agile Tester Extension Exam Crash Course Part 6
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. 51 to 60) with Explanation in Favour of the Correct Answer
The Correct Answer option has been Hi-lighted in Yellow.
Q. 51: (Level K2) Which out of the following is the purpose of hardening or stabilization iterations in Agile projects?
A. It is used to resolve any lingering defects and other forms of technical debts.
B. It is used for customer testing so the team can get the feedback on product quality.
C. It is used to finish any pending automation tasks to achieve desired test coverage. D. It is used for the team to work on process improvement activities.
Explanation in favor of the correct answer:
Option (A) is True – as the bugs creeping out of previous iterations are a form of Technical Debt. Hardening or stabilization iterations occur periodically
to resolve technical debt in Agile development.Option (B) is False – as the purpose of hardening or stabilization iterations is not for customer testing.
Option (C) is False – as the purpose of hardening or stabilization iterations is not to catch up on automation tasks.
Option (D) is False – as the process improvement activities happen in parallel with iteration activities.
<<<<<< =================== >>>>>>
Q. 52: (Level K2) Out of the following which test activities is typically done during agile projects, but is not as common on traditional projects?
A. Testers prepare detailed test strategy to address all testing activities during each iteration.
B. Testers spend a lot of time creating, executing and maintaining automated tests and results.
C. Testers use defect based techniques to find defects.
D. Testers used risk-based testing as one of the test strategies.
Explanation in favor of the correct answer:
Option (A) is False – as lightweight documentation is favored in Agile projects.
Option (B) is True – as test automation occurs at all levels in most agile teams. In Agile projects testers focus on automating, executing and maintaining tests on integration, system, and acceptance level. In traditional projects, testers do not have the same focus on automation.
Option (C) is False – as defect based techniques such as software attacks and error guessing are used in traditional projects also.
Option (D) is False – as risk-based testing techniques are used in traditional projects also.
<<<<<< =================== >>>>>>
Q. 53: (Level K2) Which out of the following TWO statements are true on agile projects?
Select TWO options.
A. Testers should work closely with developers while retaining an objective outlook.
B. Test managers do not exist in organizations doing agile development.
C. There is no difference between what testers and developers do on agile projects.
D. Developers should rely on testers to create the automated regression tests.
E. A selection of users may perform beta testing on the product after the completion of a series of iterations.
Explanation in favor of the correct answer:
The basic hypothesis of agile projects is a joint collaboration between testers, developers, and business stakeholders being a homogeneous cross-functional team operating for a common goal.
<<<<<< =================== >>>>>>
Q. 54: (Level K2) Consider the following work products used by Agile team for development and testing activities:
i. Quality risk catalogs.
ii. Test Results log.
iii. User stories.
iv. Automated unit tests.
Which out of the above are Test work products?
A. i and ii
B. ii only
C. i and iii
D. All of the above.
Explanation in favor of the correct answer:
Statement (i) is True – as it is one of the Test work products.
Statement (ii) is True – as it is one of the Test work products.
Statement (iii) is False – as it is one of the business-oriented work products, not a Test work product.
Statement (iv) is False – as these are the developer work products, not a Test Work product.
<<<<<< =================== >>>>>>
Q. 55: (Level K2) Out of the following which combination of activities should occur in an Agile project?
i. Functional verification testing of user stories developed in the previous iteration.
ii. Tester, developer, and business representative working collaboratively to determine whether the feature is fit for use.
iii. Re-running the automated unit tests and feature verification tests from the current iteration and previous iteration.
iv. System test level entry and exit criteria.
A. ii and iv
B. i and ii
C. ii and iii
D. ii only
Explanation in favor of the correct answer:
Statement (i) is False – as features should be verified in the same iteration in which they are developed.
Statement (ii) is True – as this is required in an Agile project as part of feature validation testing.
Statement (iii) is True – as this is required in an Agile project as part of regression testing which is a parallel process throughout the iteration.
Statement (iv) is False – as this is not required in Agile project. Test level entry and exit criteria are more closely associated with sequential lifecycle models.
<<<<<< =================== >>>>>>
Q. 56: (Level K2) Which out of the following TWO statements are true on Agile projects?
A. Feature verification testing, which is often automated, may be done by developers or testers.
B. Regression testing can be done by the business users either at the close of each iteration, after the completion of each iteration, or after a series of iterations.
C. Feature validation testing is usually manual and can involve developers, testers, and business stakeholders working collaboratively
D. Acceptance testing can be done by developers, testers, and business stakeholders working collaboratively
Explanation in favor of the correct answer:
Option (A) is True – as feature verification testing involves testing against the user story’s acceptance criteria and is done by developers or testers.
Option (B) is False – as regression testing should be done by the tester, not the business user.
Option (C) is True – as feature validation testing involves developers, testers, and business stakeholders working collaboratively to determine whether the feature is fit for use.
Option (D) is False – as acceptance testing is done by the client.
<<<<<< =================== >>>>>>
Q.57: (Level K2) 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.
Out of the following which combination of these activities should occur in an Agile project?
A. ii only
B. i and ii
C. ii and iii
D. iii only
Explanation in favor of the correct answer:
The basic hypothesis of agile projects is a joint collaboration between testers, developers, and business stakeholders being a homogeneous cross-functional team defining and operating on common acceptance criteria.
<<<<<< =================== >>>>>>
Q.58: (Level K2) Out of the following which statements about independent testing on agile projects is FALSE?
A. There can be a risk of losing test independence for organizations introducing agile.
B. Independent testers will find more defects than developers regardless of the test level.
C. Independent testing can be introduced at the end of a sprint.
D. The independent test team can be part of another team.
Explanation in favor of the correct answer:
It is a misconception that Independent testers are more efficient than developers.
<<<<<< =================== >>>>>>
Q. 59: (Level K2) Out of the following which testing tasks should NOT be taken by the independent testing team on Agile projects?
A. System Integration testing.
B. Test data creation.
C. Non Functional testing
D. User story acceptance testing.
Explanation in favor of the correct answer:
Option (A) is False – as Independent testing team can work on the test levels like system integration testing that might not fit well within a sprint.
Option (B) is False – as Independent testing team can work on test data creation which is an iteration-independent activity.
Option (C) is False – as Independent testing team can work on non-functional testing which is an iteration-independent activity.
Option (D) is True – as user story acceptance testing involves working closely with developers and other team members so there is a chance to lose test independence.
<<<<<< =================== >>>>>>
Q. 60: (Level K2) Which out of the following TWO statements are true for independent test teams on agile projects?
1. Independent test Teams can be used for creating and supporting test environments and data.
2. Independent testers can work on all the iteration testing activities.
3. Independent test teams can work as ‘on demand’ testers In the final days of each sprint.
4. Independent testers can work on all the iteration automation activities.
A. 1 and 4
B. 1 and 2
C. 2 and 4
D. 1 and 3
Explanation in favor of the correct answer:
Statement (1) is True – as independent test teams can work on the iteration-independent activities like creating and supporting test environments and data
Statement (2) is False – reason being, if the team will work on the iteration testing activities with the Agile team, then there is a chance to lose test independence.
Statement (3) is True – as independent test teams can provide an objective, unbiased evaluation of the software at the end of a sprint.
Statement (4) is False – reason being, if the team will work on the automation testing activities with the developers, then there is a chance to lose test independence.
Continue to Crash Course Part 7
