Try our Free Demo Practice Tests for Comprehensive CTFL4 Exam Preparation

Only developers and testers should be involved in retrospectives, as involving people in other roles is very likely to prevent developers and testers from having open and constructive discussions that really help identify process improvements.

Retrospectives can be very effective in identifying process improvements and can also be very efficient and cost-effective especially since, unlike reviews, they do not require any follow-up activities

On Agile projects, well-conducted retrospectives at the end of each iteration can help the team reduce and sometimes even eliminate the need for dairy stand-up meetings.

During retrospectives, in addition to identifying relevant process improvements, participants should also consider how to implement these improvements and retain them based on the context of the project, such as the software development lifecycle. 

a defect is fixed and after other tests do not find any side-effect introduced in the software as a result of such fix

a failed test, and aims to run that test again to confirm that the same behavior still occurs and thus appears to be reproducible

the execution of an automated regression test suite to confirm the absence of false positives in the test results

 Therefore, as a functional tester, you have the responsibility to report the performance issue as a defect, and provide as much information as possible to help the developers or the performance testers to investigate and resolve it. Question #:79 Which of the following statements about white-box test techniques is true? Achieving full statement coverage and full branch coverage for a software product means that such software product has been fully tested and there are no remaining bugs within the code Code-related white-box test techniques are not required to measure the actual code coverage achieved by black-box testing, as code coverage can be measured using the coverage criteria associated with black-box test techniques Branch coverage is the most thorough code-related white-box test technique, and therefore applicable standards prescribe achieving full branch coverage at the highest safety levels for safety-critical systems Code-related white-box test techniques provide an objective measure of coverage and can be used to complement black-box test techniques to increase confidence in the code Answer: D Explanation This answer is correct because code-related white-box test techniques are test design techniques that use the structure of the code to derive test cases. They provide an objective measure of coverage, such as statement coverage, branch coverage, or path coverage, which indicate how much of the code has been exercised by the test cases. Code-related white-box test techniques can be used to complement black-box test techniques, which are test design techniques that use the functional or non-functional requirements of the system or component to derive test cases. By combining both types of techniques, testers can increase their confidence in the code and find more defects. References: ISTQB Glossary of Testing Terms v4.0, ISTQB Foundation Level Syllabus v4.0, Section 2.3.2.2 Question #:80 Confirmation testing is performed after: a defect is fixed and after other tests do not find any side-effect introduced in the software as a result of such fix a failed test, and aims to run that test again to confirm that the same behavior still occurs and thus appears to be reproducible the execution of an automated regression test suite to confirm the absence of false positives in the test results a defect is fixed, and if such testing is successful then the regression tests that are relevant for such fix can be executed

Traceability between test basis items and the test cases designed to cover them, makes it possible to determine which test basis items have been covered by the executed test cases.

Traceability between test basis items and the test cases designed to cover them, enables experience-based test techniques to be applied

Traceability between test basis items and the test cases designed to cover them, enables identification of which test cases will be affected by changes to the test basis items.

Traceability can be established and maintained through all the test documentation for a given test level, such as from test conditions through test cases to test scripts.