ISTQB-CTFL-FOUNDATION Practice Questions

:

A driver is a piece of code that calls a function or module to be tested and passes it the necessary

test data. It is commonly used in bottom-up integration testing to simulate the higher-level modules

that invoke the function being tested. Stubs, on the other hand, are used to simulate lower-level

modules. Reference: ISTQB CTFL Syllabus V4.0, Section 4.3.1​​.

Boundary value testing focuses on testing at the boundaries between partitions. It tests conditions

on, below, and above the edges of input and output equivalence classes to identify defects that occur

at the boundaries. This technique is different from equivalence partitioning, which divides input data

into partitions but does not specifically target boundary conditions. Reference: ISTQB CTFL Syllabus

V4.0, Section 4.2.1​​.

In a review meeting, the moderator is responsible for ensuring the meeting runs smoothly,

mediating between participants, and managing time effectively. The moderator's role includes

facilitating communication and making sure all participants have the opportunity to contribute.

Taking minutes of the meeting is typically done by a recorder or scribe, not the moderator.

Reference: ISTQB CTFL Syllabus V4.0, Section 3.2.4​​.

A test case defines the expected result of a test. The ISTQB CTFL syllabus v4.0 explains that a test case

includes a set of input values, execution preconditions, expected results, and execution

postconditions developed for a particular objective or test condition​​.

Failures in software can be caused by various reasons, including testing faults, software faults, design

faults, environment faults, and documentation faults. The ISTQB CTFL syllabus v4.0 discusses that

these types of issues can all contribute to failures in software, highlighting the importance of

thorough testing and review processes throughout the software development lifecycle​​.

Retesting, also known as confirmation testing, involves executing a previously failed test case after

the defect has been fixed. The objective is to ensure that the original defect has been successfully

removed. This type of testing is critical in verifying that the defect fixes are effective and that the

software now operates as expected under the same conditions that previously caused the failure.

Reference: ISTQB CTFL Syllabus V4.0 - Section 1.4.2, Retesting

Assessing organizational maturity (i) is very important when deciding whether to introduce a test

tool, as implementing a tool in an immature test organization with poor processes is unlikely to

produce any benefits.

A quick return on the initial investment (ii) in a test tool is rare.

Having a requirement that a tool should be easy to use for untrained and unskilled testers (iii) is

generally a false hope. This is comparable with expecting someone who has never driven a car to be

able to drive safely and effectively.

Agreeing requirements before evaluating tools (iv) is essential. Not to do so would be comparable

with building and testing a system without requirements.

In conclusion, (i) and (iv) are good principles to follow when introducing a tool and (ii) and (iii) are

not.

Iterative development involves users in the testing throughout the development process. This

approach allows for continuous feedback from users, ensuring that the evolving system meets user

requirements and expectations. Unlike the traditional waterfall model, iterative development

accommodates changes and improvements based on user feedback, making it suitable for dynamic

environments like website development. Reference: ISTQB CTFL Syllabus V4.0, Section 2.1.3​​.

Providing support for the test team using the tool is crucial for successful deployment. This includes

training the test team on how to effectively use the tool, offering ongoing support to address any

issues, and integrating the tool into existing processes. By ensuring that the team is well-equipped

and confident in using the tool, the organization can maximize the benefits of the tool and improve

overall testing efficiency​​.