CTFL4 Practice Questions

A typical entry criterion for testing is the availability of testable requirements. Testable requirements

provide a basis for designing and executing test cases. Without clear and testable requirements, it is

challenging to determine what needs to be tested and to create effective test cases. Entry criteria

ensure that the necessary preconditions are met before testing begins, which helps in conducting

efficient and effective testing.

Reference: ISTQB CTFL Syllabus, Section 5.1.3, "Entry and Exit Criteria."

Checklist-based testing is a technique where testers use pre-determined checklists to ensure that

important aspects of a work product are evaluated. Over time, these checklists should be reviewed

and updated periodically to maintain their effectiveness in detecting defects. As systems evolve,

outdated checklists may miss new types of defects, thus diminishing their usefulness. Therefore,

statement D is true according to the ISTQB CTFL syllabus  .

The correct matching of the topics with their descriptions is as follows:

Functional behaviour: The externally observable behaviour with user actions as input operating

under certain configurations (A to C).

Quality characteristics: How the system performs the specific behaviour (B to A).

Scenarios: A sequence of actions between an external actor and the system, to accomplish a specific

goal or business task (C to B).

Business rules: Activities that can only be performed in the system under certain conditions defined

by outside procedures and constraints (D to E).

External interfaces: Description of the connections between the system to be developed and the

outside world (E to D)  .

When writing a defect report, the tester can specify the expected result and the actual result based

on the observation. The expected result is what the requirements specify, and the actual result is

what was observed during testing. These elements are crucial for clearly communicating the nature

of the defect to developers and other stakeholders. The other items such as test environment, test

level, and root cause may not be clear or necessary at this stage of defect reporting.

Reference: ISTQB CTFL Syllabus, Section on defect management and reporting.

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.

One of the primary objectives of testing is to ensure that the software or system being tested meets

all regulatory requirements. This is crucial in many industries where compliance with laws and

standards is mandatory. According to the ISTQB CTFL Syllabus v4.0, testing aims to evaluate the

quality of the software product and verify that it complies with specified requirements, including

regulatory requirements  .

To determine the optimal test execution schedule that minimizes the number of configuration

switches and respects the dependencies, we start with the initial configuration, CONF1.

TC4: It has no dependencies and runs on CONF1 (initial configuration).

TC3: Depends on TC4 and runs on CONF1. Since TC4 is already executed, we can proceed with TC3.

TC2: Depends on TC4 and runs on CONF2. We switch to CONF2 after TC3.

TC1: No dependencies and runs on CONF2. Since we are already in CONF2, we can execute TC1 next.

TC5: Depends on TC1 and runs on CONF2. Since TC1 is already executed, we can proceed with TC5

without additional configuration switches.

By following this sequence (TC4, TC3, TC2, TC1, TC5), we respect the dependencies and minimize the

number of configuration switches

In a planning poker session, if there is a significant difference in the estimations, it indicates that

there may be misunderstandings or different perspectives on the complexity of the user story.

According to the agile principles, the team should discuss these differences to reach a common

understanding. The goal is to ensure that all team members have a shared understanding of the user

story's scope and complexity before finalizing the estimate  .

A successful review process involves all participants being trained in the review type and

understanding its objectives. This ensures that everyone can contribute effectively and understand

what is expected from the review. Proper training helps to identify defects accurately and facilitates

constructive feedback, leading to a more efficient and effective review process. Hence, statement C

is correct according to the ISTQB CTFL syllabus  .

Retrospectives are a crucial part of Agile practices, aiming to identify process improvements and

determine how to implement them effectively. They should involve participants discussing not only

what improvements could be made but also how to integrate and sustain those improvements

within the project context, including the software development lifecycle. This makes statement D

accurate according to the ISTQB CTFL syllabus  .