You are testing the latest version of an air-traffic control system prior to production deployment using exploratory testing. After following an unusual sequence of input steps, the system crashes. After the crash, you document a defect report with the following information:
* Title: System crashes unexpectedly during input.
* Brief summary: System crashes when an unusual sequence of inputs is used.
* Version: V1.001
* Test: Exploratory testing prior to production deployment
* Priority: Urgent
* Risk: High
* Reference: Screenshot of crashed application
What critical Information Is missing from this report?
Answer : C
The critical information missing from the defect report is a detailed description of the defect to enable reproduction. A clear and concise description of the steps taken to reproduce the defect is essential for developers to understand the context and to be able to replicate the issue in their environment. Without this information, it can be challenging to diagnose and fix the defect. The ISTQB CTFL syllabus emphasizes the importance of providing all necessary details in a defect report to facilitate effective communication and resolution.
Which of the statements correctly describes when a whole team approach may NOT be suitable?
Answer : A
The whole team approach involves collaboration among all team members, including testers, developers, and business representatives, to achieve quality goals. However, this approach may not be suitable in situations where a high level of test independence is required. Test independence is essential in cases where unbiased testing is critical, such as in regulated environments or where high-risk systems are involved. This is because team members might unintentionally influence each other's work, leading to potential bias in testing outcomes.
Consider an estimation session in which a six-member Agile team (Memb1..... Memb6) uses the planning poker technique to estimate a user story (in story points). The team members will use a set of cards with the following values: 1,2, 3,5, 8,13,21. Below is the outcome of 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 teams using the planning poker technique for estimating user stories, it is common practice to have further discussions and rounds of estimation if there is a significant discrepancy in the initial estimates. This helps in reaching a consensus and ensures that all team members understand the complexity and requirements of the user story. According to the ISTQB CTFL syllabus, planning poker involves discussions to clarify differences in estimates, especially when there is a wide range of values selected. By having Memb6 and Memb4, who provided the most pessimistic and optimistic estimates, explain their reasoning, it fosters a deeper understanding and encourages the team to converge towards a more accurate and agreed-upon estimate.
From a testing perspective, configuration management
Answer : B
Configuration management in the context of testing involves the systematic control of changes to the configuration items, including testware such as test scripts, test data, and test environments. It ensures that all changes are tracked and recorded, enabling the version control and management of testware .
Option A is related to test execution rather than configuration management. Option C describes quality management in a broader sense, not specifically configuration management. Option D is specific to the configuration of tools, not the overall management of testware versions.
A test status report SHOULD:
Answer : A
A test status report is a document that provides a snapshot of the testing activities and their progress during a particular period. It should include information about any impediments encountered during the test execution and the actions taken to resolve them, which helps stakeholders understand the challenges and how they were addressed .
Option B describes an activity related to test completion rather than ongoing status reporting. Option C is incorrect because the structure and contents of the report may vary based on the audience's needs. Option D, while important, is not the primary purpose of a test status report, which focuses more on the current status and impediments.
Which of the following about typical information found within a test plan is FALSE?
Answer : C
A typical test plan includes various elements, such as resource requirements, test completion criteria, and suspension/resumption criteria. However, the list of product risks that have not been fully mitigated is generally not included in the test plan but rather in the risk management documentation.
The test plan focuses on planning and executing tests, including resource allocation and defining criteria for test suspension and resumption.
While risk management is crucial, unmitigated risks are typically documented in risk logs or separate risk management plans.
Which of the following statements about the test pyramid is TRUE?
Answer : B
The test pyramid concept suggests that there should be more low-level tests (unit tests) and fewer high-level tests (end-to-end tests).
As we move higher up the pyramid (e.g., from unit tests to integration tests to end-to-end tests), each test covers more production code.
Higher-level tests (like end-to-end) validate larger parts of the application, including multiple units and their interactions.
This aligns with the principle that higher-level tests provide broader coverage but are fewer in number and more expensive to run and maintain.