Which of the following statements about retrospectives is true?
Correct Answer: D
Retrospectives are critical for continuous improvement in Agile projects. They involve not only identifying process improvements but also planning their implementation and ensuring they areretained, considering the specific context of the project, such as the software development lifecycle. This holistic approach ensures that improvements are practical and sustainable. References: * ISTQB CTFL Syllabus 4.0, Chapter 2.1.6, page 26: Retrospectives and Process Improvement
Question 117
What type of testing measures its effectiveness by tracking which lines of code were executed by the tests?
Correct Answer: B
Structural testing is a type of testing that measures its effectiveness by tracking which lines of code were executed by the tests. Structural testing, also known as white-box testing or glass-box testing, is based on the internal structure, design, or implementation of the software. Structural testing aims to verify that the software meets the specified quality attributes, such as performance, security, reliability, or maintainability, by exercising the code paths, branches, statements, conditions, or data flows. Structural testing uses various coverage metrics, such as function coverage, line coverage, branch coverage, or statement coverage, to determine how much of the code has been tested and to identify any untested or unreachable parts of the code. Structural testing can be applied at any level of testing, such as unit testing, integration testing, system testing, or acceptance testing, but it is more commonly used at lower levels, where the testers have access to the source code. The other options are not correct because they are not types of testing that measure their effectiveness by tracking which lines of code were executed by the tests. Acceptance testing is a type of testing that verifies that the software meets the acceptance criteria and the user requirements. Acceptance testing is usually performed by the end-users or customers, who may not have access to the source code or the technical details of the software. Acceptance testing is more concerned with the functionality, usability, or suitability of the software, rather than its internal structure or implementation. Integration testing is a type of testing that verifies that the software components or subsystems work together as expected. Integration testing is usually performed by the developers or testers, who may use both structural and functional testing techniques to check the interfaces, interactions, or dependencies between the components or subsystems. Integration testing is more concerned with the integration logic, data flow, or communication of the software, rather than its individual lines of code. Exploratory testing is a type of testing that involves simultaneous learning, test design, and test execution. Exploratory testing is usually performed by the testers, who use their creativity, intuition, or experience to explore the software and discover any defects, risks, or opportunities for improvement. Exploratory testing is more concerned with the behavior, quality, or value of the software, rather than its internal structure or implementation. Reference = ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, Chapter 4: Test Techniques, Section 4.3: Structural Testing Techniques, Pages 51-54; Chapter 1: Fundamentals of Testing, Section 1.4: Testing Throughout the Software Development Lifecycle, Pages 11-13; Chapter 3: Static Testing, Section 3.4: Exploratory Testing, Pages 40-41.
Question 118
A number of characteristics are given for impact of SDLC on the testing effort. i.Finishing of requirements review leading to test analysis ii.Both - static and dynamic testing performed at unit testing level iii.Frequent regression testing may need to be performed iv.Extensive product documentation v.More use of exploratory testing Which of the following statements is MOST correct?
Correct Answer: B
Sequential models, such as the Waterfall model, typically involve completing the requirements review before moving on to test analysis, as well as producing extensive product documentation (i and iv). Iterative and incremental models, like Agile and Spiral models, often involve both static and dynamic testing at the unit testing level, frequent regression testing due to continuous integration and changes, and more use of exploratory testing (ii, iii, and v). References: * ISTQB CTFL Syllabus V4.0, Section 2.1 on software development lifecycle models and their impact on testing, which discusses the characteristics and testing practices of different lifecycle models.
Question 119
Which ONE of the following options MOST ACCURATELY describesbranch testing?
Correct Answer: C
Branch testingis a structural testing technique that ensures eachbranch (decision point)in the control flow is executed at least once. The goal is to measurebranch coverage, which is the number of branches exercised divided by the total number of branches. * (A) describes statement testing, not branch testing. * (B) and (D) introduce confusion between decisions and statements, whereas branch testing focuses on control flow branches. In simple terms,branch testing checks that all possible decision outcomes (true/false) are executed, whereas statement testing only ensures that each line of code is executed. Reference:ISTQB CTFL v4.0 Syllabus, Section 4.3.2 - Branch Testing
Question 120
Which of the following is not an example of a typical content of a test completion report for a test project?
Correct Answer: D
This answer is correct because the test procedures of all test cases that have been executed are not a typical content of a test completion report for a test project. A test completion report is a document that summarizes the test activities and results at the end of a test project. It usually includes information such as the test objectives, scope, approach, resources, schedule, results, deviations, issues, risks, lessons learned, and recommendations for improvement. The test procedures of all test cases that have been executed are part of the test documentation, but they are not relevant for the test completion report, as they do not provide a high-level overview of the test project outcomes and performance. References: ISTQB Foundation Level Syllabus v4.0, Section 2.5.3.2
