CTFL_Syll_4.0 iSQI ISTQB Certified Tester Foundation Level (CTFL) v4.0 Free Practice Exam Questions (2025 Updated)

To determine the number of partitions using one-dimensional equivalence partitioning, we need to consider each aspect of the ID requirement individually.

Length of the ID:

Valid partitions: 5 to 10 characters (1 partition)

Invalid partitions: Less than 5 characters, more than 10 characters (2 partitions)

Type of characters:

Valid partitions: Alphanumeric characters (1 partition)

Invalid partitions: Non-alphanumeric characters (1 partition)

Type of first character:

Valid partitions: First character is a letter (1 partition)

Invalid partitions: First character is not a letter (1 partition)

Adding these together, we have a total of 1 (valid length) + 2 (invalid lengths) + 1 (valid type) + 1 (invalid type) + 1 (valid first character) + 1 (invalid first character) = 7 partitions.

The tests at the bottom layer of the test pyramid run faster than the tests at the top layer of the pyramid because they are more focused, isolated, and atomic. They usually test individual units or components of the software system, such as classes, methods, or functions. They are also easier to maintain and execute, as they have fewer dependencies and interactions with other parts of the system. The tests at the top layer of the test pyramid, on the other hand, are slower because they cover larger pieces of functionalities, such as user interfaces, workflows, or end-to-end scenarios. They also have more dependencies and interactions with other systems, such as databases, networks, or external services. They are more complex and costly to maintain and execute, as they require more setup and teardown procedures, test data, and test environments. References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:

ISTQB® Certified Tester Foundation Level Syllabus v4.0, Chapter 3.2.1, Test Pyramid1

ISTQB® Glossary of Testing Terms v4.0, Test Pyramid2

To determine the correct execution order that minimizes the number of configuration switches and respects the dependencies, we need to consider the following:

Initial Configuration:CONF1.

Dependencies:

TC1 depends on nothing.

TC2 depends on TC4.

TC3 depends on TC4.

TC4 depends on nothing.

TC5 depends on TC1.

Configuration Requirements:

TC1 requires CONF2.

TC2 requires CONF2.

TC3 requires CONF1.

TC4 requires CONF1.

TC5 requires CONF2.

Given the initial configuration is CONF1, start with test cases that can run on CONF1 and respect the dependencies. Then switch to CONF2 only when necessary. The optimal order to minimize configuration switches is:

Start withTC4(no dependencies, CONF1).

Continue withTC3(depends on TC4, CONF1).

Switch to CONF2.

ExecuteTC2(depends on TC4, CONF2).

Continue withTC1(no dependencies, CONF2).

Finally, executeTC5(depends on TC1, CONF2).

Therefore, the correct order is:

TC4(CONF1)

TC3(CONF1)

TC2(CONF2)

TC1(CONF2)

TC5(CONF2)

Thus, the answer isA. TC4, TC3, TC2, TC1, TC5.

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.

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.

Acceptance criteria for user stories are crucial in defining the specific requirements that a piece of software must meet to be accepted by the user or stakeholder. These criteria often include data definitions such as format, allowed values, and default values, ensuring that the software behaves correctly with the expected data inputs.

Option A is incorrect because user acceptance tests are not usually automated; they are often conducted manually by end-users. Option C is incorrect because acceptance criteria should cover both positive and negative scenarios to ensure comprehensive testing. Option D is incorrect because tests derived from acceptance criteria can indeed be included in the testing quadrants, particularly in the quadrant related to business-facing tests that critique the product.

The primary objectives of testing, as outlined in the ISTQB CTFL v4.0 syllabus, include verifying whether specified requirements are met (A), detecting failures and defects (B), and validating that the test object functions as expected (D). However, "finding errors" (C) is not a direct objective. Errors result from human mistakes, but testing primarily identifies defects, which are flaws in the system that cause failures. Testing aims to reveal defects rather than directly identify errors in the code.

Option D correctly explains what is represented by the lines A, B and the axes X, Y in a testing metrics chart. According to option D:

X-axis represents Time

Y-axis represents Count

Line A represents Number of open bugs

Line B represents Total number of executed tests

This information is essential in understanding and analyzing the testing metrics of a completed project.

One of the generic skills required for the role of a tester is the ability to use tools to make the execution of repetitive testing tasks more efficient. This includes using various test automation tools to streamline the testing process, reduce manual effort, and improve the consistency and accuracy of test results. Testers should be proficient in leveraging these tools to enhance productivity and ensure comprehensive test coverage.

This answer is correct because equivalence partitioning is a test design technique that divides the input domain of a system or component into partitions of equivalent data, such that each partition is expected to produce the same output or behavior. Equivalence partitioning aims to reduce the number of test cases by selecting one representative value from each partition. In this case, the input domain of the TAS can be divided into four partitions based on the bonus rules: less than 50k€, between 50k€ and 80k€, between 80k€ and 120k€, and more than 120k€.The test cases in the answer belong to the same partition, which is between 80k€ and 120k€, and they are expected to produce the same output, which is a bonus of 15%. References: ISTQB Glossary of Testing Terms v4.0, ISTQB Foundation Level Syllabus v4.0, Section 2.3.2.1

Maintenance testing is performed to ensure that the application continues to function correctly after changes have been made. These changes can include modifications due to new regulations, bug fixes, enhancements, or any other updates. In this case, the change in the protocol for connecting to the payment gateway due to new regulations falls under maintenance testing, as itinvolves testing the application to ensure it works correctly after the implementation of the required changes​​.

Top of Form

Bottom of Form

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.

The statement "Achieving full code coverage for a component or a system ensures that it has been fully tested" is false because achieving full code coverage does not necessarily mean that all possible defects have been identified or that the system is free of bugs. Code coverage metrics, such as statement coverage, branch coverage, or path coverage, only measure the extent to which the source code has been executed during testing, but they do not guarantee that all logical paths or use cases have been exercised or that the code behaves correctly under all conditions.

Full code coverage indicates that every line of code has been executed at least once, but it does not account for the quality of the test cases or their ability to detect defects. There can still be issues related to performance, usability, security, and other non-functional aspects that are not addressed by code coverage alone.

Exploratory testing is characterized by its reliance on the skills and experience of the tester. The effectiveness of exploratory testing depends heavily on the tester's ability to design and execute tests basedon their intuition and knowledge of the application. This type of testing is often performed without predefined test cases, making the individual tester's expertise crucial.

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).

Test exit criteria are the conditions that must be fulfilled before concluding a particular testing phase. These criteria act as a checkpoint to assess whether we have achieved the testing objectives and are done with testing1. Test exit criteria are typically defined in the test plan document, which is one of the outputs of the test planning phase. The test plan document describes the scope, approach, resources, and schedule of the testing activities. It also identifies the test items, the features to be tested, the testing tasks, the risks, and the test deliverables2. According to the ISTQB® Certified Tester Foundation Level Syllabus v4.0, the test plan document should include the following information related to the test exit criteria3:

The criteria for evaluating test completion, such as the percentage of test cases executed, the percentage of test coverage achieved, the number and severity of defects found and fixed, the quality and reliability of the software product, and the stakeholder satisfaction.

The criteria for evaluating test process improvement, such as the adherence to the test strategy, the efficiency and effectiveness of the testing activities, the lessons learned and best practices identified, and the recommendations for future improvements.

Therefore, the test plan document is the most appropriate test document to find the test exit criteria described. The other options, such as test design specification, project plan, and requirements specification, are not directly related to the test exit criteria. The test design specification describes the test cases and test procedures for a specific test level or test type3. The project plan describes the overall objectives, scope, assumptions, risks, and deliverables of the software project4. The requirementsspecification describes the functional and non-functional requirements of the software product5. None of these documents specify the conditions for ending the testing process or evaluating the testing outcomes. References = ISTQB® Certified TesterFoundation Level Syllabus v4.0, Entry and Exit Criteria in Software Testing | Baeldung onComputer Science, Entry And Exit Criteria In Software Testing - Rishabh Software, Entry and Exit Criteria in Software Testing Life Cycle - STLC [2022 Updated] - Testsigma Blog, ISTQB® releases Certified Tester Foundation Level v4.0 (CTFL).

This answer is correct because shift-left in testing is an approach that aims to perform testing activities as early as possible in the software development lifecycle, in order to find and fix defects faster and cheaper, and to improve the quality of the software product. Continuous integration is a practice that supports shift-left in testing, as it involves integrating and testing the software components frequently, usually several times a day, using automated tools and processes. Continuous integration can reduce the time between the introduction of a defect and its detection, thereby reducing the cost to fix it and the risk of accumulating defects that could affect the functionality or performance of the software product. References: ISTQB Foundation Level Syllabus v4.0, Section 3.1.1.3, Section 3.2.1.3

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.

Sequential models, such as the Waterfall model, typically involve completing the requirements review before moving on to test analysis, as well as producing extensive product documentation (i and iv). Iterative and incremental models, like Agile and Spiral models, often involve both static and dynamic testing at the unit testing level, frequent regression testing due to continuous integration and changes, and more use of exploratory testing (ii, iii, and v).