CTFL_Syll2018 Exam Dumps - ISTQB Certified Tester Foundation Level (Syllabus 2018)

Both functional and structural approaches are used in integration tests. Functional testing verifies that the integrated components work together as expected, while structural testing checks the internal structure and logic of the integrated components1 explains this in more detail:

Integration testing is a level of software testing where individual units are combined and tested as a group. The purpose of this level of testing is to expose faults in the interaction between integrated units. Test drivers and test stubs are used to assist in Integration Testing.

Integration testing can be done in two ways:

• Bottom-up Integration Testing: Bottom up integration testing begins with unit testing, followed by tests of progressively higher-level combinations of units called modules or builds.
• Top-down Integration Testing: In top down integration testing, the highest-level modules are tested first and progressively lower-level modules are tested after that.

Statement testing is a white box test technique2. A white box technique is a technique that uses the internal structure or logic of a system as a test basis to derive test cases and measure test coverage2. Statement testing is a technique that uses executable statements in the source code as a test basis to measure the coverage achieved by a test suite2. A statement is an instruction or command that performs an action or calculation in the source code2. Statement testing requires every statement in the source code to be executed at least once by a test suite2. Therefore, statement testing is a white box test technique.

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

Test control is a test management activity that involves making decisions based on information from test monitoring and test progress reporting. Test control activities include:

• Re-prioritizing tests because of time pressure
• Changing the test schedule due to availability of a test environment
• Setting entry and exit criteria for test levels or test activities
• Initiating corrective actions to resolve deviations from the test plan

Writing test suspension and resumption criteria in the test plan is not a test control activity, but rather a test planning activity. Test suspension and resumption criteria are used to define when to stop and resume testing in case of unforeseen events or issues that affect the test execution.

References: Certified Tester Foundation Level Syllabus, Section 2.4.2 and 2.4.3

Priority is an important item of information that is missing from the incident report. Priority indicates the importance or urgency of resolving the incident, based on the business needs and the impact on the stakeholders. Priority is usually assigned by the project manager or the customer, and it helps to determine the order in which incidents should be addressed. Priority may differ from severity, which indicates the degree of impact of the incident on the system or the component under test. Severity is usually assigned by the tester or the developer, and it helps to assess the risk of the incident. For example, an incident may have a high severity but a low priority, if it affects a critical function but only occurs in a rare situation. Conversely, an incident may have a low severity but a high priority, if it affects a minor function but occurs frequently or affects many users. Therefore, both priority and severity are useful information for incident management and resolution.

The other options are not essential information for the incident report, although they may be helpful or desirable in some cases. Recommendations are suggestions or proposals for resolving the incident, which may be provided by the tester, the developer, or other stakeholders. However, recommendations are not mandatory, and they may not be feasible or acceptable in some situations. Name of tester is the identifier of the person who reported the incident, which may be useful for communication or accountability purposes. However, name of tester is not critical, and it may be replaced by other identifiers, such as email address, employee number, or role. Change history is the record of the changes made to the incident report, such as status, resolution, or comments. Change history is valuable for tracking and auditing purposes, but it is not part of the initial incident report, rather it is updated as the incident progresses.

References: ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 5.3.2, p. 49-50 1; ISTQB Glossary v4.0, p. 38-39 2

2400, 1000, 2301 are test case inputs that each fall into a different equivalence partition1. Equivalence partitioning is a black box test design technique that divides the input domain of a system into partitions of equivalent data2. Each partition should contain data that is expected to be treated the same by the system2. Therefore, only one test case input from each partition is needed to test the system’s behaviour2. In this question, the input domain of the system is the time of travel, which can be divided into three partitions based on the fare rules:

• Peak-time tariff: This partition contains all the times between 0600 and 1000 (inclusive), which are subject to a higher fare.
• Off-peak tariff: This partition contains all the times between 1001 and 2259 (inclusive), which are subject to a lower fare.
• No service: This partition contains all the times between 2300 and 0559 (inclusive), which are not valid for travel.

Therefore, to test the system’s behaviour for each partition, we need to choose one test case input from each partition. Among the options given in this question, only D contains one test case input from each partition. 2400 belongs to the no service partition, 1000 belongs to the peak-time tariff partition, and 2301 belongs to the off-peak tariff partition. Therefore, D is the correct answer.

The correct answer is A, as it describes error guessing. Error guessing is an experience-based test technique that involves designing tests based on experience, defect data, or common knowledge about why software fails1. Error guessing can be used to complement other more formal test techniques by focusing on areas that are more likely to contain defects1. Option B is incorrect, as error guessing does not involve building test cases based on the various experiences of developers, architects, users, and other stakeholders on project teams, but based on the tester’s own experience and knowledge1. Option C is incorrect, as error guessing is not a suitable test technique that can be used effectively in place of more formal techniques, but a supplementary technique that can be used in addition to more formal techniques1. Option D is incorrect, as error guessing is not a valid and useful white-box test technique due to its high degree of statement coverage, but an experience-based test technique that does not rely on the structure of the software1. References: 1, Section 4.2.6

The extent of testing required for a software product or feature depends on several factors that influence the level of quality and risk involved in delivering or deploying it. Some of these factors are:

• Budget to do testing: This factor indicates how much money is available or allocated for conducting the test activities, which affects the scope, depth, duration, and resources of testing.
• Time available to do testing: This factor indicates how much time is available or allocated for conducting the test activities, which affects the schedule, frequency, speed, and coverage of testing.
• Level of risk of the product or feature: This factor indicates how much impact or harm a failure or defect in the product or feature can cause to the users, customers, stakeholders, or environment, which affects the priority, intensity, complexity, and rigor of testing.
• Complexity of the product or feature: This factor indicates how difficult or challenging it is to understand, design, implement, or maintain the product or feature, which affects the effort, skill, technique, and tool required for testing.

A particular tester involved in testing is not a deciding factor in determining the extent of testing required because it does not affect the quality or risk level of the product or feature being tested. Rather, it is an outcome or consequence of deciding how much testing is needed based on other factors such as budget, time, risk, and complexity. You can find more information about determining the extent of testing in Software Testing Foundations: A Study Guide for the Certified Tester Exam, Chapter 2, Section 2.12.