ISTQB Agile Tester Extension Exam Theory Study Material Part 20
Have a deep study of this entire question bank and Lessons learnt out of the Agile projects. This study resource is as per the latest syllabus.
Just 1 hr. of time spent in brushing up your knowledge just before the ISTQB Agile Tester Extension Exam shall be of great help in clearing it.
Set of 10 Lessons Learnt (L. 41 to 50) out of Agile Projects
L. 41: The test pyramid emphasizes having more tests at the lower levels and a decreasing number of tests at the higher levels. It refers to situation where the number of automated unit tests is higher than the number of automated tests for higher test levels.
<<<<<< =================== >>>>>>
L. 42: The testing quadrants can be used as an aid to describe the types of tests to all stakeholders. It should not be used as metric for risk level or test coverage. In some situations, there may not be any tests for a quadrant.
<<<<<< =================== >>>>>>
L.43:
Planning poker sessions are held first to determine what can be accomplished in the given iteration. If it is determined that there is not enough time to complete all items, it is probable that the lower risk items will be added to the backlog for future sprints.
<<<<<< =================== >>>>>>
L. 44: The entire team must agree on the estimate for the user story. The customer alone does not understand the complexity of developing or testing the functionality.
<<<<<< =================== >>>>>>
L. 45: Exploratory testing is known as an experienced based approach to testing, which will be as effective as the tester running the tests. The benefit of this approach is that the tests that will be designed and executed will influence the next set of tests that are designed and executed.
<<<<<< =================== >>>>>>
L. 46: Exploratory testing is not a technique but an approach to testing that can use other techniques such as pairwise, classification trees, boundary value analysis etc.
<<<<<< =================== >>>>>>
L. 47: One of the benefits of using exploratory testing is when there are requirements that are less than perfect, and within agile projects there is limited analysis, depth and detail of requirements.
<<<<<< =================== >>>>>>
L. 48: Exploratory testing encompasses concurrent learning, test design, and execution.
<<<<<< =================== >>>>>>
L. 49: Best results are achieved when exploratory testing is combined with other test strategies.
<<<<<< =================== >>>>>>
L. 50: Exploratory tester needs good understanding of how the system is used and how to determine when it fails.
ISTQB Agile Tester Extension Exam Theory Study Material Part 21
