CTFL_Syll_4.0 ISTQB Certified Tester Foundation Level (CTFL) v4.0 Questions and Answers

The question is about identifying an example of testing contributing to higher quality. Quality is the degree to which a component, system or process meets specified requirements and/oruser/customer needs and expectations1. Testing is the process consisting of all lifecycle activities, both static and dynamic, concerned with planning, preparation and evaluation of software products and related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects2.

Therefore, testing contributes to higher quality by verifying and validating that the software products and related work products meet the specified requirements, are fit for purpose and have no defects, or at least have a reduced number of defects. Testing also provides information about the quality of the software products and related work products to the stakeholders, who can make informed decisions based on the test results3.

Out of the four given statements, only option D is an example of testing contributing to higher quality, as it shows that testing has detected a defect (a flaw in a component or system that can cause the component or system to fail to perform its required function4) and that the defect has been resolved (fixed and confirmed) prior to release (delivery of the software product to the customer or end user). This means that testing has prevented a potential failure (an event in which a component or system does not perform a required function within specified limits) from occurring in the operational environment, and thus has improved the quality of the software product.

Option A is not an example of testing contributing to higher quality, as it is a reporting activity that summarizes the test results and evaluates the test objectives, but does not directly affect the quality of the software product or related work products. A test summary report is a document that records and communicates the outcomes of testing activities, including test completion criteria, test results, incident reports, test summary and evaluation, and lessons learned.

Option B is not an example of testing contributing to higher quality, as it is a planning activity that estimates the resources and time needed for testing activities, but does not directly affect the quality of the software product or related work products. A test effort estimate is an approximation of the amount of work and/or the duration of time required to perform testing activities.

Option C is not an example of testing contributing to higher quality, as it is a preparation activity that sets up the test environment (an environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test), but does not directly affect the quality of the software product or related work products. A test environment installation is a process of installing and configuring the test environment according to the test environment specification.

References:

1: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 10

2: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 11

3: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 12

4: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 13

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 13

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 77

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 78

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 79

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 80

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 81

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 82

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 83

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 84

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 85

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 86

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 87

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 88

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 89

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 90

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 91

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 92

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 93

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 94

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 95

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 96

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 97

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 98

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 99

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 100

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 101

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 102

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 103

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 104

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 105

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 106

: ISTQB Certified Tester Foundation Level Syllabus 2018, Version 4.0, p. 107

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.

According to the ISTQB Certified Tester Foundation Level (CTFL) v4.0, the life cycle of a defect typically follows a sequence from its discovery to its closure. In the provided figure, it starts with S0 (New), moves to S1 (Assigned), then to S2 (Resolved), followed by S3 (Verified). If the defect is not fixed, it can be Re-opened (S5) and goes back for verification (S3). Once verified, it is Closed (S4). References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 Syllabus, Section 1.4.3, Page 17.

The decision table provides conditions and corresponding actions. For C2:

The user is logged in (Yes).

The user is not authorized to view the profile (No).

The correct action should be not to display the profile (No) and to display an error message (Yes).

This matches the actions listed for C2, making it the correct condition with the proper actions​​.

Test analysis involves identifying the features to be tested and deriving test conditions. It is the phase where testers analyze the test basis (e.g., requirements, specifications) to identify testable aspects of the system. Test design (A) focuses on creating test cases, test implementation (C) involves preparing the test environment, and test execution (D) runs the tests.

Confirmation testingis performed after a defect is fixed to confirm it no longer exists (A).Regression testingensures new defects have not been introduced in unchanged parts of the system. Regression testing is broader than confirmation testing and covers unmodified areas affected by the changes. Options B, C, and D misrepresent the relationship and scope of these tests.

Static analysis requires access towork products like source code, models, or documentation, making itimpossible to analyze Commercial off-the-shelf (COTS) software(A) because its source code is typically unavailable. Static analysis is applicable to source code (B), BPMN models (C), and UML diagrams (D).

State transition testing validatesvalid and invalid state transitionsbased on defined rules.

D is invalidbecause it transitionsfrom DIAGNOSTIC MODE directly to EMERGENCY MODE, which isnot a valid state changein most systems.

Other options follow valid sequences according tostate transition rules.

Effort estimate does not depend on the budget of the project, but rather on the scope, complexity, and quality of the software product and the testing activities1. Budget is a constraint that may affect the feasibility and accuracy of the effort estimate, but it is not a factor that determines the effort estimate. Effort estimate is the amount of work required to complete the testing activities, measured in terms of person-hours, person-days, or person-months2.

The other options are correct because:

A. Once the test effort is estimated, resources can be identified and a schedule can be drawn up, as they are interrelated aspects of the test planning process3. Resources are the people,tools, equipment, and facilities needed to perform the testing activities4. Schedule is the time frame and sequence of the testing activities, aligned with the project milestones and deadlines5.

B. Effort estimate can be inaccurate because the quality of the product under tests is not known, as it affects the number and severity of the defects that may be found and the rework that may be needed to fix them6. Quality is the degree to which the software product satisfies the specified requirements and meets the needs and expectations of the users and clients7.

D. Experience based estimation is one of the estimation techniques, which relies on the judgment and expertise of the testers and other project stakeholders to estimate the test effort based on similar projects or tasks done in the past. Experience based estimation can be useful when there is a lack of historical data, formal methods, or detailed information about the software product and the testing activities.

References =

1 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 154

2 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 155

3 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 156

4 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 157

5 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 158

6 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 159

7 ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 16

[8] ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 160

[9] ISTQB® Certified Tester Foundation Level Syllabus v4.0, 2023, p. 161

During iteration planning, testers provide input on risk analysis, testability, and the feasibility of test automation.Participating in risk analysis (B)helps identify areas needing more extensive testing.

(A) is incorrectbecause the test strategy is usually set at a higher level (project or release level).

(C) is incorrectas release planning is broader than iteration planning.

(D) is incorrectsince writing user stories is mainly the responsibility of theproduct owner, though testers contribute to defining acceptance criteria.

Risk-based test prioritizationensures testing efforts are aligned with business needs and software risks.

As a functional tester, you should open a defect report providing detailed information on which devices and by running which tests you observed the issue. A defect report is a document that records the occurrence, nature, and status of a defect detected during testing, and provides information for further investigation and resolution. A defectreport should include relevant information such as the defect summary, the defect description, the defect severity, the defect priority, the defect status, the defect origin, the defect category, the defect reproduction steps, the defect screenshots, the defect attachments, etc. Opening a defect report is a good practice for any tester who finds a defect in the software system, regardless of the type or level of testing performed. The other options are not recommended, because:

The issue is related to performance efficiency, not functionality, but that does not mean that as a functional tester, you should not open any defect report as all the functional tests passed. Performance efficiency is a quality characteristic that measures how well the software system performs its functions under stated conditions, such as the response time, the resource utilization, the throughput, etc. Performance efficiency is an important aspect of the user experience, especially for web applications that run on different devices and networks. Even if the functional tests passed, meaning that the software system met the functional requirements, the performance issue observed on some devices could still affect the user satisfaction, the usability, the reliability, and the security of the software system. 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.

A static analysis tool is best suited for determining source code compliance with the guidelines provided by a coding standard. Static analysis tools analyze code without executing it, checking for adherence to coding standards, potential errors, and code quality issues. They are designed to detect deviations from predefined coding standards and ensure that the code conforms to best practices and guidelines.

References:

ISTQB CTFL Syllabus V4.0, Section 3.2.3 on Static Analysis and its applications

The syllabus explains that static analysis tools are used to enforce coding standards and improve code quality by detecting issues early in the development process​​.

CTFL NEW

The problem described involves a software implementation error in a decision statement for calculating a bonus based on the Total Amount of Sales (TAS). The requirement states that if TAS is 300,000€ or more, a bonus should be paid. However, the software incorrectly implements this with "IF (TAS = 300000)" instead of "IF (TAS >= 300000)".

Applying Boundary Value Analysis (BVA) to this situation involves selecting test cases at the boundaries of the input domain, including just below, at, and just above the boundary conditions.

Test Case TC1 = 299999:

This value is just below the boundary (300,000).

Expected Result: No bonus should be paid.

Actual Result: No bonus paid.

TC1does not highlight the fault because the implemented condition "IF (TAS = 300000)" and the correct condition "IF (TAS >= 300000)" both yield the same result (no bonus).

Test Case TC2 = 300000:

This value is exactly at the boundary.

Expected Result: Bonus should be paid.

Actual Result: Bonus paid.

TC2does not highlight the fault because the implemented condition "IF (TAS = 300000)" and the correct condition "IF (TAS >= 300000)" both yield the same result (bonus paid).

Test Case TC3 = 300001:

This value is just above the boundary.

Expected Result: Bonus should be paid.

Actual Result: No bonus paid due to the incorrect implementation.

TC3highlights the fault because the implemented condition "IF (TAS = 300000)" fails to pay the bonus, whereas the correct condition "IF (TAS >= 300000)" would pay the bonus.

BVA focuses on the edges of input ranges where errors are more likely.

The critical values are just below, at, and just above the boundary.

Boundary Value Analysis (BVA):Verification:According to the ISTQB CTFL syllabus, BVA is an essential technique for identifying potential errors at the boundaries of input ranges. This is because developers are more likely to make mistakes at these extremes​​.

Therefore,TC3 (300001)is the test case that would highlight the fault in the software's implementation of the decision condition.

Based on the given user story and acceptance criteria, the ATDD (Acceptance Test-Driven Development) approach focuses on defining acceptance tests before development begins. The first test written typically covers the "happy path" or the most straightforward scenario to ensure the primary functionality works as expected.

The registration form must be filled with valid values.

The user must accept terms and conditions.

An email with a confirmation link must be sent after submission.

Given Acceptance Criteria:The most likely first ATDD test would ensure that a new user can successfully register by filling in all fields with valid data and confirming the registration through an email link. This ensures that the basic and most crucial functionality of the registration feature is working correctly before handling edge cases or error conditions.

References:

ISTQB CTFL Syllabus Section 2.3 on acceptance test-driven development (ATDD)​​.

The "absence-of-defects fallacy" in software development refers to the mistaken belief that if a software system has been thoroughly tested and all requirements have been met without any defects, it guarantees the success of the system. However, this is not necessarily true. Even if no defects are found, the system might still fail to meet the user's needs or business objectives. This fallacy highlights the importance of validation in addition to verification to ensure that the system fulfills the intended use and requirements​​.

The document that describes the test procedures, including the order in which test cases are to be executed according to dependencies described by preconditions and postconditions, is typically produced during the test implementation phase. During this phase, detailed test procedures and scripts are developed, organized, and prioritized for execution. The main goal of test implementation is to ensure that all test cases are prepared and structured in a way that supports efficient and effective test execution.

References:

ISTQB® CTFL Syllabus 4.0, Chapter 5.1.6, page 49: Test Implementation

Statement coverage is a structural coverage metric that measures the percentage of executable statements in the source code that are executed by a test suite1. Decision coverage is another structural coverage metric that measures the percentage of decision outcomes (such as branches or conditions) in the source code that are executed by a test suite1. Decision coverage is a stronger metric than statement coverage, because it requires that every possible outcome of each decision is tested, while statement coverage only requires that every statement is executed at least once2. Therefore, if a test suite achieves 100% decision coverage, it also implies that it achieves 100% statement coverage, because every statement in every branch or condition must have been executed. However, the converse is not true: 100% statement coverage does not guarantee 100% decision coverage, because some branches or conditions may have multiple outcomes that are not tested by the test suite2. For example, consider the following pseudocode:

if (x > 0) then print(“Positive”) else print(“Non-positive”) end if

A test suite that executes this code with x = 1 and x = -1 will achieve 100% statement coverage, because both print statements are executed. However, it will not achieve 100% decision coverage, because the condition x > 0 has only been tested with two outcomes: true and false. The third possible outcome, x = 0, has not been tested by the test suite. Therefore, the test suite may miss a potential bug or error in the condition or the branch.

The other options, such as stale transition coverage, equivalence class coverage, and boundary value coverage, are not guaranteed to be 100% by achieving 100% decision coverage. Stale transition coverage is a structural coverage metric that measures the percentage of transitions between states in a state machine that are executed by a test suite3. Equivalence class coverage is a functional coverage metric that measures the percentage of equivalence classes (or partitions) of input or output values that are tested by a test suite4. Boundary value coverage is another functional coverage metric that measures the percentage of boundary values (or extreme values) of input or output ranges that are tested by a test suite4. These metrics are independent of decision coverage, because they are based on different aspects of the system under test, such as its behavior, functionality, or specification. Therefore, achieving 100% decision coverage does not imply achieving 100% of any of these metrics, and vice versa. References = ISTQB® Certified Tester Foundation Level Syllabus v4.0, Test Coverage in Software Testing - Guru99, Structural Coverage Metrics - MATLAB & Simulink - MathWorks India, Test Design Coverage in Software Testing - GeeksforGeeks.

Both black-box test techniques and experience-based test techniques can be applied to functional and non-functional testing. Functional testing focuses on what the system does, while non-functional testing examines how the system performs. These techniques provide flexible and effective methods for assessing various aspects of the system.

References:

ISTQB® CTFL Syllabus 4.0, Chapter 4.4, page 42: Experience-Based Testing Techniques​

In the V-model project described in the question, the tester can identify the following based on the provided information:

Expected result (II):The requirements specification clearly states that the app should only ask for access permissions to the camera and photos stored on the device during and after installation. This expected behavior is defined by the requirements.

Actual result (III):The tester observes that the app also requests access to all contacts on the device, which deviates from the expected result. This actual observation can be recorded accurately.

Given these details, the tester can specify the expected result (II) and the actual result (III) in the defect report. However, without more information, the tester cannot determine the test environment (I), the test level (IV), or the root cause (V).

References:

ISTQB CTFL Syllabus V4.0, Section 5.5 on Defect Reporting

Typical contents of a defect report as mentioned in the syllabus include the expected result and the actual result observed during testing​​.

BDD emphasizes collaboration between developers, testers, and business stakeholders to define system behavior in a readable format (A). It typically uses theGiven-When-Thensyntax. Unlike unit testing (B), BDD is at a higher level of abstraction. It does not focus solely on non-functional testing (C) and encourages early testing rather than post-development validation (D).

DevOps practices emphasize the importance of testing non-functional characteristics such as performance, security, and reliability. This focus ensures that the system not only meets functional requirements but also performs well under various conditions and is secure. DevOps promotes a continuous testing approach, which includes both functional and non-functional testing integrated into the development and deployment pipelines.

References:

ISTQB CTFL Syllabus V4.0, Section 2.1.4 on DevOps and testing, which highlights the role of DevOps in emphasizing non-functional characteristics​​.

Regression testing is the re-running of functional and non-functional tests to ensure that previously developed and tested software still performs as expected after a change1 It does not involve retesting of a fixed defect, testing of new functionality, or applying only to functional testing. Tests that are used for regression testing should be repeatable, because they are used to verify the stability of the software after each change2 References = ISTQB Certified Tester Foundation Level (CTFL) v4.0 Syllabus, Chapter 4, Section 4.2.2, Page 291; ISTQB Glossary of Testing Terms v4.0, Page 292

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

White-box testing, also known as structural testing, involves testing the internal structures or workings of an application, as opposed to its functionality (which is tested by black-box testing). The correct statement about white-box testing is that it helps find defects by measuring aspects such as statement coverage.

Statement Coverage: White-box testing techniques like statement coverage measure whether each statement in the code has been executed at least once. This helps ensure that all parts of the code are tested and can reveal defects in areas that might not be reached by black-box testing alone​​.

Other statements are less accurate in the context of white-box testing:

Specifications being vague: White-box testing is code-focused, not requirement-focused. If specifications are vague, it affects both white-box and black-box testing. The main advantage of white-box testing is that it allows testers to create tests based on the code's structure and logic​​.

Requirements-based coverage: This is typically associated with black-box testing, which derives tests from specifications and requirements. White-box testing, on the other hand, derives tests from the code itself​​.

Focus on defects rather than failures: Both white-box and black-box testing aim to identify defects, but white-box testing does this through code coverage and examining the code paths directly. It does not focus exclusively on defects rather than failures; it is just another method to identify potential issues​​.

When deciding on the order of test execution based on priorities and dependencies, the correct sequence should consider both the priority levels and any dependencies between test cases. Here’s the analysis:

Test Bhas the highest priority (1) and depends onTest D.

Test Dshould be executed beforeTest B.

Test Chas a medium priority (2) and depends onTest A.

Test Acan be executed at any time since it has no dependencies.

Considering these dependencies and priorities,Test Dshould be executed first, followed byTest B. After that,Test Aand finallyTest C. Therefore, the correct sequence isD-B-A-C​​.

The three-point test estimation technique is a method of estimating the test effort based on three initial estimates: the most optimistic, the most likely, and the most pessimistic. The technique uses a weighted average of these three estimates to calculate the final estimate, which is also known as the expected value. The formula for the expected value is:

Expected value = (most optimistic + 4 * most likely + most pessimistic) / 6

Using the given values, the expected value is:

Expected value = (6 + 4 * 30 + 54) / 6 Expected value = 30 person hours

However, the expected value is not the only factor to consider when estimating the test effort. The technique also calculates the standard deviation, which is a measure of the variability or uncertainty of the estimates. The formula for the standard deviation is:

Standard deviation = (most pessimistic - most optimistic) / 6

Using the given values, the standard deviation is:

Standard deviation = (54 - 6) / 6 Standard deviation = 8 person hours

The standard deviation can be used to determine a range of possible values for the test effort, based on a certain level of confidence. For example, using a 68% confidence level, the range is:

Expected value ± standard deviation

Using the calculated values, the range is:

30 ± 8 person hours

Therefore, the final estimate is between 22 person hours and 38 person hours, which is option A.

References: ISTQB® Certified Tester Foundation Level Syllabus v4.01, Section 2.3.2, page 24-25; ISTQB® Glossary v4.02, page 33.

When a document management system is decommissioned, maintenance testing must include data migration testing to ensure that all documents are correctly transferred to a state archive, meeting legal requirements for long-term storage. This process verifies that data integrity is maintained during migration.

References:

ISTQB® CTFL Syllabus 4.0, Chapter 2.3, page 29: Maintenance Testing and Data Migration​

This answer is correct because a typical objective of testing is to ensure that a software has been tested using a combination of test techniques, such as black-box, white-box, or experience-based techniques, that are appropriate for the test objectives, test levels, and test types. Testing using a combination of test techniques can increase the effectiveness and efficiency of testing, as different techniques can target different aspects of the software quality, such as functionality, usability, performance, security, reliability, etc. Testing using a combination of test techniques can also reduce the risk of missing defects that could be detected by one technique but not by another. References: ISTQB Foundation Level Syllabus v4.0, Section 2.3.1.1, Section 2.3.2

One of the primary benefits of using test automation tools is the reduction in time spent on repetitive tasks. Automation allows tests to be run quickly and consistently, freeing up testers to focus on morecomplex and exploratory testing tasks. While automation can help increase test coverage and improve efficiency, it does not necessarily reduce the number of found bugs or always decrease the total cost of the test project.

References:

ISTQB CTFL Syllabus V4.0, Section 6.2 on the benefits of test automation​​.

 State testing techniques are a type of dynamic testing techniques that are based on the behavior of the system under test for different input conditions and events. Dynamic testing techniques require the system to be executed with test cases, whereas static testing techniques do not. Static testing techniques can be applied before the code is ready for execution, such as reviews, inspections, walkthroughs, and static analysis. Static testing techniques can help find defects early in the development process, improve the quality of the code, and reduce the cost and effort of dynamic testing. References = ISTQB Certified Tester Foundation Level (CTFL) v4.0 Syllabus, Chapter 4, Section 4.2.1, Page 281; ISTQB Glossary of Testing Terms v4.0, Page 292

Test-driven development is not an example of a typical generic skill required for testing, but rather an example of a specific technical skill or a development practice that may or may not be relevant for testing, depending on the context and the objectives of the testing activities. Test-driven development is an approach to software development and testing, in which the developers write automated unit tests before writing the source code, and then refactor the code until the tests pass. Test-driven development can help to improve the quality, the design, and the maintainability of the code, as well as to provide fast feedback and guidance for the developers. However, test-driven development is not a skill that is generally expected or needed for testers, especially for testers who are not involved in unit testing or who do not have access to the source code. The other options are examples of typical generic skills required for testing, which are skills that are applicable and beneficial for testing in any context or situation, regardless of the specific testing techniques, tools, or methods used. The typical generic skills required for testing include:

Be able to use test management tools and defect tracking tools: These are tools that help testers to plan, organize, monitor, and control the testing activities and resources, as well as to record, track, analyze, and resolve the defects detected during testing. These tools can improve the efficiency, the effectiveness, and the communication of the testing process, as well as to provide traceability, metrics, and reports for the testing outcomes.

Be able to communicate defects and failures to developers as objectively as possible: This is a skill that involves the ability to report and describe the defects and failures found during testing in a clear, concise, accurate, and unbiased manner, using relevant information, evidence, and terminology, without making assumptions, judgments, or accusations. This skill can facilitate the collaboration, the understanding, and the resolution of the defects and failuresbetween the testers and the developers, as well as to prevent conflicts, misunderstandings, or blame games.

Possess the necessary social skills that support effective teamwork: These are skills that involve the ability to interact, cooperate, and coordinate with other people involved in or affected by the testing activities, such as the test manager, the test team, the project manager, the developers, the customers, the users, etc. These skills can include communication, negotiation, leadership, motivation, feedback, conflict resolution, etc. These skills can enhance the quality, the productivity, and the satisfaction of the testing process, as well as to foster a positive and constructive testing culture. References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:

ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 1.1.1, Testing and the Software Development Lifecycle

ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 1.1.2, Testing and Quality

ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 1.2.1, Testing Principles

ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 1.2.2, Testing Policies, Strategies, and Test Approaches

ISTQB® Glossary of Testing Terms v4.0, Test-driven Development, Test Management Tool, Defect Tracking Tool, Defect Report, Failure, Social Skill2

Branch coverage is a type of structural coverage metric that measures the percentage of branches or decision outcomes that are executed by the test cases. A branch is a point in the code where the control flow can take two or more alternative paths based on a condition. For example, an if-else statement is a branch that can execute either the if-block or the else-block depending on the evaluation of the condition. Branch coverage ensures that each branch is taken at least once by the test cases, and thus reveals the behavior of the software under different scenarios. Branch coverage is also known as decision coverage or all-edges coverage.

Branch coverage is suitable for testing the cases where a specific action is not allowed, because it can verify that the test cases cover all the possible outcomes of the conditions that determine the action. For example, if the program has a condition that checks if the manufacturing stage can be stopped, then branch coverage can ensure that the test cases cover both the cases where the stage can be stopped and where it cannot be stopped. This way, branch coverage can help identify any missing or incorrect branches that may lead to undesired or unsafe actions.

The other options are not correct because they are not suitable for testing the cases where a specific action is not allowed. Code coverage is a general term that encompasses various types of coverage metrics, such as statement coverage, branch coverage, data flow coverage, etc. Code coverage does not specify which type ofcoverage metric is used for the analysis. Data flow coverage is a type of structural coverage metric that measures the percentage of data flow paths that are executed by the test cases. A data flow path is a sequence of statements that define, use, or kill a variable. Data flow coverage is useful for testing the correctness and completeness of the data manipulation in the software, but not for testing the conditions that determine the actions. Statement coverage is a type of structural coverage metric that measures the percentage of statements or lines of code that are executed by the test cases. Statement coverage ensures that each statement is executed at least once by the test cases, but it does not reveal the behavior of the software under different scenarios. Statement coverage is a weaker criterion than branch coverage, because it does not account for the branches or decision outcomes in the code. References = ISTQB Certified Tester Foundation Level (CTFL) v4.0 syllabus, Chapter 4: Test Techniques, Section 4.3: Structural Testing Techniques, Pages 51-54.

Exploratory testing is an experience-based testing technique where test design and test execution occur simultaneously. It is characterized by the tester actively exploring the application, using their intuition and experience to uncover defects. Exploratory testing sessions are often guided by test charters, which are brief documents outlining the test objectives, scope, and areas to be explored during the session.

These test charters provide a flexible framework that directs the tester's exploration without being overly prescriptive, allowing testers to adapt and investigate new areas as they uncover issues. This approach is particularly useful in dynamic and complex systems where predefined test cases might not cover all scenarios.

References:

The official ISTQB® CTFL syllabus explains the structure and benefits of exploratory testing, highlighting how test charters guide the testing process while allowing for flexibility and adaptability in identifying defects​​.

A test plan is a document detailing the objectives, resources, schedule, and scope of testing activities. It also outlines the test strategy, environment, tools, and criteria for test completion and suspension.

Option A:Correct as it indicates resource planning which is a crucial part of a test plan.

Option B:Correct as it describes exit criteria which are essential for test completion.

Option C:Incorrect because a test plan typically addresses known risks and mitigation strategies but does not list unmitigated risks post-test execution.

Option D:Correct as it mentions suspension criteria which are also a part of a test plan.

Therefore, option C is false as it does not reflect the typical information found within a test plan.

The statement that the shift-left approach can only be implemented with test automation is false. The shift-left approach emphasizes early testing activities in the software development lifecycle to detect and address defects as soon as possible. While test automation can support shift-left practices, it is not the only method. The shift-left approach can also involve practices such as static analysis, early requirement reviews, and integrating security vulnerability assessments early in the development process.

Retrospectives provide value by fostering improvement and collaboration. The correct mapping is:

A2: Team bonding occurs when teams openly discuss issues.

B1: Test effectiveness increases when process improvements are implemented.

C4: Test basis improves by addressing requirement deficiencies.

D3: Cooperation improves through regular review of collaboration.

This answer is correct because static testing and dynamic testing are both types of testing that can be used to highlight issues associated with non-functional characteristics, such as usability, performance, security, reliability, etc. Static testing is a type of testing that involves the analysis of software work products, such as requirements, design, code, or test cases, without executing them. Dynamic testing is a type of testing that involves the execution of software work products, such as code or test cases, using inputs and verifying outputs. Both static testing anddynamic testing can be applied to different test levels and test types, and can use different test techniques and tools, to evaluate the non-functional characteristics of the software product. References: ISTQB Glossary of Testing Terms v4.0, ISTQB Foundation Level Syllabus v4.0, Section 2.2.1.1, Section 2.2.1.2

Business, development, and testing (C)are the three key perspectives inagile user story refinement:

Business (Product Owner, Stakeholders)– Ensures the story aligns with user needs and business goals.

Development (Developers)– Provides insights on feasibility and technical constraints.

Testing (Testers, QA)– Ensures testability, acceptance criteria, and risk identification.

(A) is incorrectbecause the product owner is part of business stakeholders.

(B) is incorrectbecause architecture is part of development, but not the primary driver of user stories.

(D) is incorrectbecauseacceptance testing is a process, not a stakeholder group.

Across-functional team collaborationensureswell-defined, testable, and feasibleuser stories.

Scenario-oriented acceptance criteria describe how a system should behave in a specific situation or scenario. These criteria are typically written from the end-user's perspective and focus on user interactions and system responses. Option D fits this description as it outlines a specific scenariowhere a user is already logged in and describes the expected behavior when the user navigates to a particular page, which is to show the report of the last test run. This type of criterion ensures that the system meets user expectations in that scenario​​.

Dynamic testing requires the execution of the software to evaluate its behavior and performance. In contrast, static testing involves examining the software's code, design, and documentation without executing the software. This makes static testing applicable to non-executable work products such as requirement documents, design documents, and source code.

Non-functional testing includes testing of both technical and non-technical quality characteristics. Non-functional testing is the process of testing the quality attributes of a system, such as performance, usability, security, reliability, etc. Non-functional testing can be applied at any test level and can use both black-box and white-box test techniques. Non-functional testing can cover both technical aspects, such as response time, throughput, resource consumption, etc., and non-technical aspects, such as user satisfaction, accessibility, compliance, etc. Therefore, option B is the correct answer.

References: ISTQB® Certified Tester Foundation Level Syllabus v4.01, Section 1.3.1, page 13; ISTQB® Glossary v4.02, page 40.

Experience-based test techniques are test design techniques that rely on the experience, knowledge, intuition, and creativity of the testers to identify and execute test cases that are likely to find defects in the software system. Experience-based test techniques are often useful to detect hidden defects that have not been targeted by black-box test techniques, which are test design techniques that use the external behavior and specifications of the software system as the test basis, without considering its internal structure or implementation. Experience-based test techniques can complement black-box test techniques by covering aspects that are not explicitly specified, such as usability, security, reliability, performance, etc. The other statements are false, because:

Experience-based test techniques do not rely on the experience of testers to identify the root causes of defects found by black-box test techniques, but rather to identify the potential sources of defects based on their own insights, heuristics, or exploratory testing. The root causes of defects are usually identified by debugging or root cause analysis, which are activities that involve examining the code or the development process to find and fix the errors that led to the defects.

Some of the most common test basis used by white-box test techniques include the source code, the design documents, the architecture diagrams, and the control flow graphs of the software system. White-box test techniques are test design techniques that use the internal structure and implementation of the software system as the test basis, and aim to achieve a certain level of test coverage based on the code elements, such as statements, branches, paths, etc. User stories, use cases, and business processes are examples of test basis used by black-box test techniques, as they describe the functional and non-functional requirements of the software system from the perspective of the users or the stakeholders.

The primary goal of experience-based test techniques is not to design test cases that can be easily automated using a GUI-based test automation tool, but rather to design test cases that can reveal defects that are not easily detected by other test techniques, such as boundary value analysis, equivalence partitioning, state transition testing, etc. Test automation is the use of software tools to execute test cases and compare actual results with expected results, without human intervention. Test automation can be applied to different types of test techniques, depending on the test objectives, the test levels, the test tools, and the test resources. However, test automation is not always feasible or beneficial,especially for test cases that require human judgment, creativity, or exploration, such as those designed by experience-based test techniques. References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:

ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 2.2.1, Black-box Test Design Techniques

ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 2.2.2, White-box Test Design Techniques

ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 2.2.3, Experience-based Test Design Techniques

ISTQB® Glossary of Testing Terms v4.0, Experience-based Test Technique, Black-box Test Technique, White-box Test Technique, Test Basis, Test Coverage, Test Automation

Statement coverage, also known as line coverage, is a metric used in white-box testing to measure the percentage of executable statements in the source code that have been executed by the test suite. Achieving a certain percentage of statement coverage means that an equivalent percentage of the executable statements in the code have been executed during testing.

For example, achieving 80% statement coverage indicates that 80% of the lines of code have been run through during the testing process. This metric helps in identifying parts of the code that have not been tested and may contain undetected defects.

It's important to note that achieving high statement coverage does not necessarily guarantee that all possible paths or scenarios within the code are tested, nor does it ensure the detection of all types of defects. Other coverage metrics, such as branch coverage or condition coverage, might also be necessary to achieve a more thorough testing process.

References:

The official ISTQB® CTFL syllabus clearly defines statement coverage and explains that it ensures that the corresponding percentage of all executable statements have been tested​​.

A test-first approach involves writing tests before writing the code. In this approach, initially, the tests fail because the corresponding functionality is not yet implemented. Afterward, the code is written or modified to make the tests pass. This cycle is repeated iteratively. This method ensures that the code is developed based on predefined tests and helps in identifying issues early in the development process​​.

Black-box testing techniques focus ontesting the functionality of the software without knowledge of its internal workings(D). They derive test cases fromspecifications, requirements, or expected behavior.Option Adescribes exploratory testing,Bcontradicts the definition by focusing on implementation, andCincorrectly includes "implied behavior," which is not a core characteristic of black-box testing.

A test status report communicates the current status, progress, and issues encountered during testing to stakeholders. It is crucial for effective test management and decision-making.

Option A:Correct as it involves reporting impediments and solutions, which are essential for ongoing test activities.

Option B:Incorrect because test status reports are not limited to test completion activities and focus more on ongoing test status rather than final unmitigated risks.

Option C:Incorrect as the structure and contents of reports should be tailored to the audience's needs to ensure effective communication.

Option D:Incorrect because specifying communication lines is typically done in the test plan, not the status report.

Thus, option A best describes a key aspect of a test status report.

A configuration management tool helps in maintaining and managing changes to software, including test cases. It ensures that changes are tracked and can be retrieved if needed. In this scenario, using a configuration management tool would have allowed Sam's updates to be stored in a central repository, preventing the loss of his work even if his PC's hard disk crashed.

References:

ISTQB CTFL Syllabus V4.0, Section 5.4 on configuration management, which describes the role of configuration management tools in maintaining control over changes​​.

TheModerator(D) plays a key role informal reviewsby facilitating discussions, ensuring that reviews stay on track, and creating an open environment for feedback. TheManager (A)is responsible for overseeing the testing process but does not directly facilitate reviews. TheReviewer (B)is responsible for examining the work product, while theReview Leader (C)organizes reviews but does not necessarily mediate them.

Exhaustive testing (testing all input combinations) is practically impossible except in trivial cases (C). Instead, testers focus on risk-based, prioritized, and efficient test techniques. The seven principles of testing in the ISTQB syllabus highlight that exhaustive testing is infeasible, and therefore, techniques such as equivalence partitioning, boundary value analysis, and risk-based testing are used to optimize test coverage.

Statement testingaims to executeevery executable statementin the source code at least once.

(D) is correctas statement testing ensuresmaximum statement execution.

(A) describes branch testing, which focuses on flow transfers.

(B) and (C) incorrectly mix decision testing and branch testing concepts.

According to the decision table in the image, a Preferred Guest Card holder with a Silver room is eligible for an upgrade to Gold Luxury (YES), while a non-Preferred Guest Card holder, regardless of room type, is not eligible for any upgrade (NO). Therefore, Customer A (a Preferred Guest Card holder with a Silver room) would be offered an upgrade to Gold Luxury, and Customer B (a non-Preferred Guest Card holder with a Platinum room) would not be offered anyupgrade. References = The answer is derived directly from the decision table provided in the image; specific ISTQB Certified Tester Foundation Level (CTFL) v4.0 documents are not referenced.

Traceability is an essential aspect of software testing that ensures each test case can be traced back to its corresponding test basis items, such as requirements, design documents, or user stories. This linkagehelps in determining which test basis items have been covered by executed test cases, identifying the impact of changes, and maintaining overall test documentation. However, the statement that traceability enables experience-based test techniques to be applied is false, as experience-based test techniques, such as exploratory testing, rely on the tester's skills and experience rather than documented traceability.

References:

ISTQB® CTFL Syllabus 4.0, Chapter 1.4.4, page 19: Importance of Traceability

Exercising at least one of the decision outcomes for all decisions within the code, ensures achieving full branch coverage, which is a test coverage criterion that requires that all branches in the control flow of the code are executed at least once by the testcases. A branch is a basic block of code that has a single entry point and a single exit point, and a decision is a point in the code where the control flow can take more than one direction, such as an if-then-else statement, a switch-case statement, a loop statement, etc. The decision outcomes are the possible paths that can be taken from a decision, such as the then branch or the else branch, the case branch or the default branch, the loop body or the loop exit, etc. The other statements are false, because:

The minimum number of test cases needed to achieve full branch coverage, is usually higher than that needed to achieve full statement coverage, which is a test coverage criterion that requires that all executable statements in the code are executed at least once by the test cases. This is because branch coverage is a stronger criterion than statement coverage, as it implies statement coverage, but not vice versa. For example, a single test case can achieve full statement coverage for an if-then-else statement, but two test cases are needed to achieve full branch coverage, as both the then branch and the else branch need to be exercised.

If full branch coverage has been achieved, then all unconditional branches within the code have not necessarily been exercised, as unconditional branches are branches that do not depend on any decision, and are always executed, such as a goto statement, a break statement, a return statement, etc. Unconditional branches are not part of the branch coverage criterion, as they do not represent different paths in the control flow of the code. However, they are part of the statement coverage criterion, as they are executable statements in the code.

If full branch coverage has been achieved, then all combinations of conditions in a decision table have not necessarily been exercised, as a decision table is a test design technique that represents the logical relationships between multiple conditions and their corresponding actions, in a tabular format. A decision table can have more combinations of conditions than the number of decision outcomes in the code, as each condition can have two or more possible values, such as true or false, yes or no, etc. For example, a decision table with four conditions can have 16 combinations of conditions, but the corresponding code may have only two decision outcomes, such as pass or fail. To exercise all combinations of conditions in a decision table, a stronger test coverage criterion is needed, such as condition combination coverage, which requires that all possible combinations of condition outcomes in the code are executed at least once by the test cases. References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:

ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 2.3.1, Test Coverage Criteria Based on the Structure of the Software

ISTQB® Glossary of Testing Terms v4.0, Branch Coverage, Statement Coverage, Branch, Decision, Decision Outcome, Unconditional Branch, Decision Table, Condition Combination Coverage

In the given decision table, Column 7 represents the following conditions and actions:

The patient is over 18 years old: True

The patient is allergic to Penicillin: True

The patient is taking anticoagulant therapy: True

When analyzing this column:

If the patient is over 18 years old, allergic to Penicillin, and taking anticoagulant therapy, the decision table suggests consultation with a hematologist and prescribing half of the full recommended dosage for 10 days.

This column does not represent an impossible situation based on the conditions provided. However, upon deeper inspection and understanding of medical practices, it can be argued that such a specificcombination of conditions could be highly unlikely, making it appear unnecessary or an edge case that might be considered for deletion.

Given the constraints of the conditions and the requirements of the decision table, the provided answer needs to be verified against real-world medical guidelines to confirm if this scenario is indeed impossible or just