CTFL_Syll2018 iSQI ISTQB Certified Tester Foundation Level (Syllabus 2018) Free Practice Exam Questions (2025 Updated)

Use case testing does not find defects caused by interaction of different components is the statement that is false about use case testing. Use case testing is a technique to create test cases based on use cases, which are descriptions of how a system interacts with one or more actors (users or other systems) to achieve a specific goal or function. Use case testing can find defects caused by interaction of different components, as use cases often involve multiple components working together to provide a service or functionality to an actor2 explains use case testing as follows:

Use case testing is a technique that helps us identify test cases that exercise the whole system on a transaction by transaction basis from start to finish. It is a functional black box testing technique.

Use cases are prepared by analysts and domain experts who document the functional requirements of a system from an end-user perspective. Each use case typically has a mainstream scenario and may have alternate or exceptional scenarios that describe different paths or outcomes.

Use case testing can help to verify that all the interactions between actors and the system under test work as expected and meet the user requirements. It can also help to detect integration defects between different components or subsystems.

A, B, and D are correct statements about use case testing. Use case generally has a mainstream scenario and may have many alternate or exceptional scenarios (A), as use cases describe different paths or outcomes depending on various conditions or events. A use case can be defined at different levels of abstraction, such as user goal level, summary level, subfunction level, etc., but not at the abstract level detached from the implementation or at the system level describing a set of executed functions (B), as use cases always describe interactions between actors and systems rather than abstract concepts or functions. Each use case has preconditions which need to be met for the use case to work successfully (D), as preconditions specify what must be true before a use case can begin.

The introduction of a test management tool does not represent one of the three triggers for maintenance testing an operational system, because it does not affect the functionality or performance of the system itself. Maintenance testing is triggered by system modification (such as corrective, adaptive, perfective or preventive changes), data migration (such as moving data from one platform or format to another), or system retirement (such as decommissioning or replacing an old system)1 .

Providing developers with information to isolate the failure is the incident report objective that this excerpt satisfies. The excerpt provides the name and location of the test file that was used to recreate the failure, which can help developers to reproduce and debug the failure in their own environment. defines this objective as follows:

One of the objectives of an incident report is to provide developers with information to isolate the failure. This means providing enough details and evidence for developers to understand what caused the failure and how to fix it. This may include information such as:

Steps to reproduce: A sequence of steps that can be followed to recreate the failure.

Test data: The inputs that were used to execute the test case that caused the failure.

Test environment: The configuration and settings of the hardware and software that were used to execute the test case that caused the failure.

Attachments: Any screenshots, logs, files, or other artifacts that can help to demonstrate or explain the failure.

B, C, and D are incorrect answers. Providing ideas for test process improvement (B) is not an incident report objective that this excerpt satisfies, as it does not provide any suggestions or feedback on how to improve the test process or prevent similar failures in the future. Not belonging in an incident report © is not true, as this excerpt belongs in an incident report as part of the incident details section. Providing test leaders with information to report test progress (D) is not an incident report objective that this excerpt satisfies, as it does not provide any metrics or indicators on how much testing has been done or how many failures have been found.

According to the syllabus, an independent test team is a group of testers who are not involved in the development of the software system under test. They perform testing activities from an external perspective, without any bias or influence from the developers or users. An independent test team can have various benefits and drawbacks, depending on the context and situation. The answer C is correct because it lists two benefits and two drawbacks of an independent test team. The benefits are:

Independent testers can find different defects, because they have a different view and knowledge of the system than the developers or users.

Independent testers can verify assumptions made during the specification of a system, because they can challenge and validate the requirements and design decisions.

The drawbacks are:

Developers may put less emphasis on quality, because they may rely on the independent testers to find and fix the defects.

Independent testers can be seen as the reason for delayed projects, because they may report defects late in the development cycle or demand more time for testing.

The other answers are incorrect because they mix benefits and drawbacks or list incorrect statements.

References: Certified Tester Foundation Level Syllabus, Section 1.4.1, page 14-15.

Assigning resources for the planned activities is an activity that is appropriate to the test planning stage, because it involves estimating and allocating the necessary human and physical resources for testing . Test planning is the process of defining the objectives, scope, approach, and resources for testing . The other options are not activities that are appropriate to the test planning stage, but rather to other stages of testing. Option A is an activity that is appropriate to the test analysis stage, because it involves analysing the test basis (such as requirements, design, or code) to identify test conditions . Option C is an activity that is appropriate to the test implementation stage, because it involves designing and preparing the test environments (such as hardware, software, network, or data) for test execution . Option D is an activity that is appropriate to the test execution stage, because it involves writing a test execution schedule that defines the order and dependencies of test cases or procedures .

The pesticide paradox principle of testing states that if we do not regularly review and revise our tests, we’ll stop finding defects, because the same tests will no longer be effective at detecting new or different defects in the software12. The other options do not explain the pesticide paradox principle of testing. Option B is false, because repeatedly running a set of tests will not ensure that a system is defect free, but rather that it meets the same quality criteria as before12. Option C is related to the defect clustering principle of testing, which states that defects are often contained in a small number of modules12. Option D is a metaphor that compares testing to spraying pesticide, but it does not explain the paradoxical effect of using the same tests over and over again

The correct answer is B, as it categorizes them as entry and exit criteria correctly. Entry criteria are conditions that must be met before testing can begin or continue with a specific activity or phase3. Exit criteria are conditions that must be met before testing can conclude or stop for a specific activity or phase3. The following table shows how each example can be categorized:

Therefore, option B is the correct answer. Options A, C, and D are incorrect, as they do not categorize them as entry and exit criteria correctly. References: 3, Section 2.4

Agile development can be classified as an iterative incremental life cycle model, where each iteration delivers a working product increment that can be evaluated by stakeholders and users. describes this as follows:

Iterative Incremental Development Model is a process where creating requirements, designing, building and testing a system in small parts. This model divided into small parts which will help to make modules very easily.In this model, module passes through some phases like requirements, coding, designing, testing.

Agile Model mostly recommended to use for current software development industries because it is very realistic approach to develop any kind of software.It follows iterative approach which means whole project divided into small iterations or modules.

Agile development is not related to any life cycle model (A), RAD (B), or V model ©.

Equivalence Partitioning is a black-box test design technique that divides input data of a software module into partitions of equivalent data from which test cases can be derived. In this context, the valid equivalence partitions are:

Silver Tier: 0 to 400 Credits

Gold Tier: 401 to 800 Credits

Platinum Tier: 801 to 1400 Credits

Concierge Tier: 1401+ Credits

The test cases provided cover all these partitions:

TC1 covers the Silver Tier boundary at 400 Credits.

TC2 covers within the Gold Tier at 500 Credits.

TC3 covers the Gold Tier boundary at 800 Credits.

TC4 covers within the Concierge Tier at 1500 Credits.

Since all valid partitions are covered by the test cases, 100% of the valid Equivalence Partitions have been achieved.

Maintenance testing is important after migration, retirement or enhancement of an existing system. defines maintenance testing as follows:

Maintenance testing is a type of software testing that occurs after changes have been made to a system in order to ensure that no new defects have been introduced and that the system still meets its original requirements and specifications.

Regression testing (A) is important after any change in the system that may affect existing functionality. Operational acceptance testing (B) is important before deploying a system into production environment. System testing © is important after integrating all components of a system into a complete system.

II, III, and V are true statements about test reports. Test reports shall give stakeholders information as basis for decisions (II), as they provide an overview of the test results, the test coverage, the remaining risks, and the recommendations for the next steps. Test reports shall summarize what happened through a period of testing (III), as they describe the test activities, the test objectives, the test methods, the test environment, and the test incidents. Test reports shall include information about remaining risks (V), as they identify the areas of uncertainty or potential failure that may affect the quality or performance of the system under test1 defines a test report as follows:

A test report is a document that summarizes and communicates the outcomes of testing to stakeholders. A test report typically includes the following information:

Test summary: A brief overview of the testing process, including the scope, objectives, approach, and results.

Test evaluation: An evaluation of the testing process against the exit criteria and quality standards, including the test coverage, defect status, and risk assessment.

Test conclusion: A conclusion on the suitability of the system under test for release or deployment, based on the test results and evaluation.

Test recommendations: A recommendation on the actions to be taken after testing, such as fixing defects, conducting further testing, or implementing improvements.

I and IV are false statements about test reports. Test reports shall not be approved by the test team (I), as they are usually approved by a higher authority or a designated stakeholder who has the responsibility and authority to make decisions based on the test report. Test reports shall not be approved by the development team, the test team and the customer (IV), as this may cause conflicts of interest or delays in decision making.

Checking that at least 50% of decisions have been exercised by a test case suite is not a valid use of decision coverage, because it does not meet the minimum criterion of decision coverage, which is to exercise all possible outcomes of each decision in the software under test1 . Decision coverage is a technique that measures how much of the logic or branching of the software under test has been exercised by the test cases1 . The other options are valid uses of decision coverage. Option A is a valid use of decision coverage, because it can check that all decisions have been exercised in a single program1 . Option B is a valid use of decision coverage, because it can check that all decisions have been exercised in a business process1 . Option C is a valid use of decision coverage, because it can check that all calls from one program module to another have been made correctly1 .

According to the syllabus, non-functional testing is a type of software testing that verifies non-functional aspects or attributes of a software product or system, such as performance, usability, reliability, security, etc. Non-functional testing evaluates how well a system operates or behaves under certain conditions or scenarios, rather than what functions or features it provides. The answer D is correct because it best exemplifies non-functional testing. Tests which capture the time it takes to save a file are examples of performance testing, which is a type of non-functional testing that measures how fast or responsive a system is under various workloads or situations. The other answers are incorrect because they exemplify functional testing or structural testing, which are not types of non-functional testing. Tests based on the internal structure of a component or system (A) are examples of structural testing, which is a type of software testing that verifies the implementation or code of a software product or system. Tests related to ‘what’ the system should do (B) are examples of functional testing, which is a type of software testing that verifies the functionality or behavior of a software product or system. Tests which calculate overtime pay for those employees entitled to such © are also examples of functional testing, as they verify a specific function or feature of a software product or system.

References: Certified Tester Foundation Level Syllabus, Section 1.2.1, page 10-11.

The correct matching of the review process main activities with the appropriate specific review activities is as follows1:

Planning: Estimating effort and timeframe (2), Selecting the people to participate (4)

Initiate review: Distributing the work product and other material (5)

Issue communication and analysis: Evaluating the review findings (6)

Fixing and reporting: Creating defect reports (1), Recording updated status of defects (3)

Therefore, option B is the correct answer. Options A, C, and D are incorrect, as they do not match the review process main activities with the appropriate specific review activities correctly. References: 1, Section 3.2.2

TC1 - £23 total charges including buggy hire; TC2 - £16 total charge but no buggy allowed. This answer can be derived from the decision table by matching the conditions of each test case with the corresponding rules and actions. For TC1, the conditions are: Loyalty Card holder = Y, 18 Holes = Y, Buggy/Cart Request = Y. These conditions match Rule 1, which has the actions: Green Fee = £18, Buggy Hire = £5, Total Charge = £23. For TC2, the conditions are: Loyalty Card holder = N, 18 Holes = N, Buggy/Cart Request = Y. These conditions match Rule 3, which has the actions: Green Fee = £16, Buggy Hire = Not Allowed, Total Charge = £16

Variables that are not used or improperly declared are defects that are more likely to be found by a static analysis tool than by other testing techniques, because they are syntactic or structural errors in the code that can be detected without executing the software13. A static analysis tool can analyse the code or design of the software under test and identify errors such as missing declarations, undefined variables, unused variables, or unreachable code13. The other options are not defects that are more likely to be found by a static analysis tool than by other testing techniques. Option A is not a defect that can be found by a static analysis tool, but rather by a requirements review or specification-based testing technique1 . Option B is not a defect that can be found by a static analysis tool, but rather by a structure-based testing technique or a coverage measurement tool1 . Option C is not a defect that can be found by a static analysis tool, but rather by a dynamic analysis tool or a monitoring tool1 .

How to fix the defect is not needed to specify in a defect report because it is not part of the information that is required to describe, reproduce, and prioritize the defect. How to fix the defect is part of the solution or resolution that is provided by the developers or maintainers who are responsible for correcting the defect. A defect report is a document that records and communicates the details of a defect found during testing. A defect report typically includes the following information:

Defect ID: A unique identifier for the defect

Summary: A brief description of the defect

Severity and priority: An indication of how serious and urgent the defect is

Test environment details: A description of the hardware, software, network, data, tools, etc., that were used when the defect was found

How to reproduce the defect: A step-by-step procedure to recreate the defect

Expected and actual results: A comparison of what should have happened and what actually happened when the defect occurred

Attachments: Any additional information or evidence that can help understand or resolve the defect, such as screenshots, logs, files, etc.

You can find more information about defect reports in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], Chapter 5.

Test techniques are methods or procedures that can be used to design, execute, or evaluate test cases. Test techniques can be classified into two categories: specification-based and structure-based. Specification-based test techniques, also known as black-box test techniques, are based on the requirements, specifications, or expectations of the system under test. They do not require any knowledge of the internal structure or implementation of the system. Some examples of specification-based test techniques are use case testing, state transition testing, decision table testing, etc. Structure-based test techniques, also known as white-box test techniques, are based on the code, architecture, or design of the system under test. They require some knowledge of the internal structure or implementation of the system. Some examples of structure-based test techniques are control flow testing, data flow testing, branch testing, statement testing, etc. You can find more information about test techniques in A Study Guide to the ISTQB® Foundation Level 2018 Syllabus, Chapter 41.

Pair programming is a software development technique where two programmers work together on the same code at the same workstation. One programmer, called the driver, writes the code while the other programmer, called the navigator, reviews the code and provides feedback and suggestions. Pair programming is not only a coding technique but also an informal review method because it involves constant communication and collaboration between the programmers who check each other’s work and share their knowledge and skills. Pair programming can improve the quality and productivity of software development by reducing defects, increasing code readability, enhancing learning opportunities, and fostering creativity and innovation. Pair programming is usually used in agile methods such as Extreme Programming (XP), Scrum, or Kanban. It is not an alternative term for code inspection, which is a formal review method where a group of reviewers examine a piece of code in a structured and systematic way following predefined rules and roles. It is also not done with developer and tester pairing together because pair programming requires both programmers to have similar levels of expertise and familiarity with the code they are working on. You can find more information about pair programming in A Study Guide to the ISTQB® Foundation Level 2018 Syllabus, Chapter 31.