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

Test cases derived from the knowledge of the testers and the knowledge of testers, developers and users are used to drive testing apply to experience-based techniques1. Experience-based techniques are techniques that use the skill, intuition, and experience of testers, developers, and users to derive test cases, using error guessing and exploratory testing1. Error guessing is a technique that uses common sense and previous experience to guess where defects might occur in a system1. Exploratory testing is an approach that involves simultaneous learning, test design, and test execution1. Experience-based techniques are typically used when there is insufficient information or time to apply other more formal techniques1. Therefore, test cases derived from the knowledge of the testers and the knowledge of testers, developers and users are used to drive testing apply to experience-based techniques.

• An incident report is a document that records any event occurring during testing that requires investigation1. An incident report should contain sufficient information to enable reproduction of the incident and resolution of the defect1. According to IEEE 829 Standard for Software Test Documentation, an incident report should contain the following information:

Therefore, among the options given in this question, only D provides the best detail on an incident report. It contains a clear title, a reproducibility indicator, a description that includes both expected and actual results, a reference to the specification document, and a screen shot of the failure. The other options are either missing some important information or providing inaccurate or irrelevant information

Statement coverage is not a black box technique, because it requires knowledge of the internal structure of the code. Black box techniques are based on the external behavior and specification of the software, without looking at the code. Equivalence partitioning, state transition testing, and boundary value analysis are all examples of black box techniques12

 The other details that should be included in the incident report when it is first submitted are B. Status of the incident, degree of impact, Test Case Number. These details are important to provide information about the current state of the incident, the severity of its effect on the system or user, and the test case that detected the incident. Other details, such as suggested solution, priority, history, related defects, expected fix time, line of code, etc., can be added later during the incident management process. A detailed explanation of incident report can be found in A Study Guide to the ISTQB® Foundation Level 2018 Syllabus, pages 99-1001.

Metrics are quantitative measures that can be used to monitor and control various aspects of software testing processes and products1. Metrics can be used to monitor progress along with test preparation and execution by providing information about the status of testing activities, such as test planning, test design, test execution, test evaluation, defect management, etc1. Among the options given in this question, only C is a suitable metric for monitoring progress along with test preparation and execution. The failure rate in testing already completed is a metric that measures how many tests have failed out of the total number of tests executed1. This metric can indicate the quality of the software product under test and the effectiveness of the test cases1. It can also help to identify areas that need more attention or improvement in testing1. Therefore, this metric can be used to monitor progress along with test preparation and execution.

The question asks which of the test cases will ensure that the statement ‘Print ‘Hold’’ is exercised. The statement ‘Print ‘Hold’’ is executed when X > Y and Z < Y. Therefore, to exercise this statement, we need to choose a test case that satisfies these conditions. Among the options given in this question, only C satisfies these conditions. X = 42 > Y =43 and Z =42 < Y =43. Therefore, C is the correct answer.

Screen-dialog flows are sequences of screens and dialogs that represent the user interface and interaction of a system. Use case testing is a technique that uses use cases as a test basis to derive test cases1. A use case is a description of interactions between actors and a system to achieve a goal1. Use case testing is the most effective technique in testing screen-dialog flows, as it can capture the user requirements, scenarios, and expected outcomes of the system. Boundary value testing is a technique that uses boundary values as a test basis to derive test cases1. A boundary value is an input value or output value on the edge of an equivalence partition or at the smallest or largest value of a range1. Boundary value testing is not the most effective technique in testing screen-dialog flows, as it is more suitable for testing numerical inputs and outputs. Statement testing and coverage is a technique that uses statements in the source code as a test basis to measure the coverage achieved by a test suite1. A statement is a minimal executable unit of source code1. Statement testing and coverage is not the most effective technique in testing screen-dialog flows, as it is more suitable for testing the internal logic and structure of the code. State transition testing is a technique that uses state transition diagrams as a test basis to derive test cases1. A state transition diagram shows the states of a system and the transitions between them triggered by events or conditions1. State transition testing is not the most effective technique in testing screen-dialog flows, as it is more suitable for testing systems that have complex or dynamic behavior based on different states.

 Testers identify defects, developers locate and correct defects, testers confirm the correction has cleared the original defect. Debugging is the process of finding and fixing defects in a software product by analyzing its code or behavior. Debugging is usually performed by developers who have access to and knowledge of the code or structure of the software product. Debugging involves locating and correcting defects identified by testers during testing activities, and verifying that the correction has cleared the original defect without introducing new defects. Testers can also participate in debugging by providing information about how to reproduce defects, what are the expected results, what are the actual results, etc., and by confirming that defects have been fixed after debugging. A detailed explanation of debugging can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], page 6.