ISTQB Certified Tester Foundation Level (CTFL) v4.0 Questions and Answers
Question 13
Which of the following BEST describes checklist-based testing?
Options:
A.
Checklist-based testing includes formal tests from detailed lists of test conditions, allowing much repeatability
B.
Checklist-based testing may involve a list of tests based on what is important to the user as well as an understanding of why and how software fails
C.
Checklist-based testing, while popular, provides little consistency and few guidelines concerning test case development
D.
Checklist-based testing is restricted to non-functional testing, including usability, performance, and security test
Answer:
B
Explanation:
Checklist-based testing involves using checklists that contain items, such as potential test conditions, that should be tested. These checklists are often based on insights into what is important to the user, potential areas where software might fail, and specific aspects that need to be tested. It provides a structured yet flexible approach to testing, ensuring key areas are covered while allowing testers to use their experience and understanding of the system. Checklist-based testing is not limited to non-functional testing but can be applied to various types of testing, including functional testing.References:
ISTQB Certified Tester Foundation Level Syllabus v4.0, Section 4.4.5.
Question 14
A test status report SHOULD:
Options:
A.
Specify the impediments to carrying out the planned test activities in the reporting period and the corresponding solutions put in place to remove them
B.
Be produced as part of test completion activities and report unmitigated product risks to support the decision whether or not to release the product
C.
Always be based on the same template within an organisation, as its structure and contents should not be affected by the audience to which the report is presented.
D.
Specify the lines of communication between testing, other lifecycle activities, and within the organisation that were chosen at the outset of the test project.
Answer:
A
Explanation:
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.
Question 15
In which of the following cases you would NOT execute maintenance testing?
Options:
A.
Retirement of the software or system
B.
Modifications to a released software or system
C.
Migration of the system data to a replacement system
D.
Update to the Maintainability requirements during the development phase
Answer:
D
Explanation:
Maintenance testing is testing performed on a software product after delivery to correct defects or improve performance or other attributes. Maintenance testing can be triggered by various situations, such as modifications to a released software or system, migration of the system data to a replacement system, or retirement of the software or system. Maintenance testing is not executed when there is an update to the maintainability requirements during the development phase, as this is not a maintenance situation but rather a change request that should be handled by the development process. Verified References: [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus - Springer], Chapter 2, page 18-19.
Question 16
Which of the following activities does NOT belong to a typical technical review?
Options:
A.
Pre-meeting preparation by reviewers
B.
Using checklists during the meeting
C.
Inviting end-users to the meeting
D.
Preparation of a review report
Answer:
C
Explanation:
Technical reviews are structured meetings that aim to examine various aspects of a product or project to identify any defects or improvements. Options A (Pre-meeting preparation by reviewers), B (Using checklists during the meeting), and D (Preparation of a review report) are typical activities in a technical review process. Inviting end-users to the meeting (C), however, is generally not part of a typical technical review, as these reviews are usually more focused on the technical aspects and are conducted by peers or experts within the development or testing teams rather than end-users.