Consider an estimation session where a six-member Agile team (Memb1, ... , Memb6) is performing a planning poker session to estimate a user story (in story points). Team
members are using a set of cards with the following values: 1, 2, 3, 5, 8, 13, 21. Below is the outcome produced by the first round of estimation for this session:
Which of the following answers best describes how the estimation session should proceed?
Answer : D
In Agile estimation sessions, particularly during Planning Poker, the goal is to reach a consensus on the effort required for a user story. The process encourages discussion and collaboration among team members to understand the story's requirements and complexities fully. Here's a breakdown of the options and why D is the correct choice:
Option A: Calculating the arithmetic mean of all estimates.
This method is straightforward but does not facilitate team discussion or consensus-building. It merely averages out the estimates without addressing the reasons behind the varying estimates. Thus, important insights and understanding of the task complexity might be missed.
Option B: Selecting the most frequent estimate value.
While this approach acknowledges the majority's opinion, it ignores the minority views, which might highlight significant aspects of the story that need consideration. It doesn't ensure that all perspectives are considered and discussed.
Option C: Calculating the mean of the most optimistic and pessimistic estimates.
This approach considers the extremes but again lacks the team discussion and consensus aspect. It also assumes that the extreme values alone can balance out the estimate, which might not always capture the true complexity or simplicity of the task.
Option D: Discussing the most pessimistic and optimistic estimates.
This approach fosters team collaboration and understanding. Memb4 and Memb6 explain their reasoning for the highest and lowest estimates, respectively, which can reveal different perspectives on the task's complexity. This discussion helps the team align their understanding and often leads to a more accurate and agreed-upon estimate in subsequent rounds.
In conclusion, the main goal of Agile estimation techniques like Planning Poker is to encourage team communication and collaboration to ensure that all aspects of the user story are considered. Option D best aligns with this goal by promoting discussion and consensus.
Which of the following statements is CORRECT?
Answer : D
White-box testing involves testing the internal structures or workings of an application, as opposed to the functionality exposed to the end user. Experience-based testing, such as exploratory testing, involves testers using their knowledge, experience, and intuition to test the system without predefined test cases, often focusing on the input-output behavior of the system.
Which ONE of the following statements is correct?
Answer : C
Performing static testing on a commercially available executable library can raise legal issues, primarily related to the ownership and licensing of the software. These libraries are often proprietary, and analyzing them without permission may violate software licenses or intellectual property laws. Static testing typically involves analyzing source code, which may not be accessible for such libraries without appropriate permissions.
ISTQB CTFL Syllabus V4.0, Section 3.2.2 on legal and ethical considerations in static testing.
Which of the following statements about impact of DevOps on testing is CORRECT?
Answer : A
DevOps practices emphasize the importance of testing non-functional characteristics such as performance, security, and reliability. This focus ensures that the system not only meets functional requirements but also performs well under various conditions and is secure. DevOps promotes a continuous testing approach, which includes both functional and non-functional testing integrated into the development and deployment pipelines.
ISTQB CTFL Syllabus V4.0, Section 2.1.4 on DevOps and testing, which highlights the role of DevOps in emphasizing non-functional characteristics.
In a review, which of the following is the responsibility of the manager?
Answer : C
In a review process, the manager's responsibility is to ensure that sufficient time is allocated for the review activities. This includes planning and scheduling the review sessions, making sure that the team has enough time to conduct a thorough and effective review.
ISTQB CTFL Syllabus V4.0, Section 3.2.3 on the roles and responsibilities in a review process, specifically mentioning the manager's role in ensuring adequate time for reviews.
A test manager has started a cycle of testing for an e-commerce application. The reason for testing is the change in the protocol for connecting to the payment gateway because of new regulations. Which of the following correctly names this type of testing?
Answer : D
Maintenance testing is performed to ensure that the application continues to function correctly after changes have been made. These changes can include modifications due to new regulations, bug fixes, enhancements, or any other updates. In this case, the change in the protocol for connecting to the payment gateway due to new regulations falls under maintenance testing, as it involves testing the application to ensure it works correctly after the implementation of the required changes.
Top of Form
Bottom of Form
You are working on creating test cases for a user story -
As a customer, I want to be able to book an ISTQB exam for a particular date, so that I can find choose my time slot and pay the correct amount, including discounts, if any.
The acceptance criteria for this :
1. The dates shown should be from the current date to 2 years in future
2. Initially there should be 10 timeslots available for each day, 1 hour each, starting at 8 AM GMT
3. Maximum 5 persons should be able to select a time slot after which that time slot should become unavailable
4. First timeslot should have a 10% discount.
Which of the following is the BEST example of a test case for this user story?
Answer : A
The best example of a test case for this user story should cover the acceptance criteria comprehensively. Option A addresses the critical aspects of the acceptance criteria:
Verifying the discount for the first timeslot (8 AM GMT) - ensuring it provides a 10% discount.
Verifying that changing the time slot removes the discount - ensuring the discount logic is correctly applied.
This test case effectively validates the functionality related to both the discount and the ability to change time slots, which are key parts of the user story's requirements.