CTFL-Foundation Exam Dumps - ISTQB Certified Tester Foundation Level

The test-planning phase involves deciding on schedules and deliverables, hardware and software requirements, and entry and exit criteria. However, the specific types of test cases to be used are typically defined during the test design phase, not during the test planning phase. Test planning focuses on the overall approach and resources needed for testing. Reference: ISTQB CTFL Syllabus V4.0, Section 5.1.1​​.

Walkthroughs are a type of static technique used in software testing. According to the ISTQB CTFL syllabus v4.0, static techniques include activities such as reviews, inspections, and walkthroughs, where the evaluation of the software product is done without executing the code​​.

Structure-based (white-box) test case design techniques involve deriving test cases systematically from the delivered code. The ISTQB CTFL syllabus v4.0 describes that these techniques focus on the internal structure of the software, using knowledge of the code to create test cases that ensure comprehensive coverage of the code's pathways and logic​​.

Static analysis tools analyze the program code to identify potential issues such as syntax errors, unreachable code, and variables that are never used. These tools perform their analysis without executing the code, thus allowing early detection of defects. The ISTQB CTFL syllabus v4.0 highlights that static analysis tools focus on the code itself to find these types of defects​​.

(i) Executing component integration tests is usually done by developers. Developers are usually responsible for unit and component integration testing. Independent testing usually follows at system and acceptance test levels.

(ii) Static analysis is usually done by developers because: it requires an understanding of the code and therefore the person doing this needs skills in the programming language; and it can be done as soon as the code is written. Therefore it is quick and effective for the developer to do it. The risk of a lack of test independence can be mitigated by performing independent system and acceptance testing.

(iii) Setting up the test environment is an activity typically performed by a tester. It may require support from developers and staff from other departments and on some occasions environmentscould be set up by developers. However, it is a task that could be done by a tester rather than a developer.

(iv) Deciding how much testing should be automated is typically a decision made by the test leader, who will consult other staff in the decision-making process. Developers may be involved and their skills may be required to automate some tests. However, the decision on how much to automate should not be made by developers.

The three decisions are in sequence and the conditions are all mutually exclusive (if any one is true the others must be false). Hence a test case that makes the first decision true will make the second and third decisions false and so on.

So test case 1 (say Time = 6) would exercise the path True, False, False, test case 2 (say Time = 15) would exercise the path False, True, False. Test case 3 would have to be Time = 12. This combination achieves 100 per cent decision coverage because each decision has been exercised through its true and its false outcomes.

A valuable objective for a test team is to cause as many failures as possible so that faults can be identified and corrected. This approach is essential because the primary goal of testing is to uncover defects that could potentially lead to failures in the software. By intentionally causing failures, testers can identify and document faults, which can then be fixed to improve the overall quality of the software.

The ISTQB CTFL Syllabus, version 4.0, emphasizes that finding and fixing defects is a core purpose of testing. It is more important to identify and address issues than to prove the absence of defects. Therefore, causing failures to find faults aligns with the fundamental objectives of software testing​​.

A driver is a piece of code that calls a function or module to be tested and passes it the necessary test data. It is commonly used in bottom-up integration testing to simulate the higher-level modules thatinvoke the function being tested. Stubs, on the other hand, are used to simulate lower-level modules. Reference: ISTQB CTFL Syllabus V4.0, Section 4.3.1​​.