ISTQB CTFL-2018 Practice Test - Questions Answers, Page 3

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 correct logical order for the test cases is 3, 1, 4, 2, 6, 5. This order follows the logical sequence of actions that a user would perform to book a flight using a web-based airline booking system. The order also respects the dependencies between test cases, such as logging in before searching for flights or booking a flight before printing a confirmation receipt . The other options are incorrect logical orders for the test cases. Option A does not follow the logical sequence of actions and does not respect the dependencies between test cases. For example, it starts with confirming details and booking a flight before logging in or selecting a flight. Option B does not follow the logical sequence of actions and does not respect the dependencies between test cases. For example, it starts with selecting a flight before logging in or searching for flights. Option C does not follow the logical sequence of actions and does not respect the dependencies between test cases. For example, it starts with viewing selected items in My Flights before selecting any flights.

Exploratory testing would be a good test technique to use when under severe time pressure, because it is a type of experience-based technique that allows testers to design and execute tests based on their intuition, knowledge, and skills, without following a predefined test plan or test cases . Exploratory testing can be useful when testing time is very limited, as it can help to find important defects quickly and adapt to changing requirements or situations . The other options are not good test techniques to use when under severe time pressure. Option B is not a good option, because structure-based testing is a type of technique that requires analysing the code or design of the software under test to measure aspects such as code coverage, complexity, or coupling . Structure-based testing can be time-consuming and may not be feasible or effective when testing time is very limited . Option C is not a good option, because specification-based testing is a type of technique that requires analysing the requirements or specifications of the software under test to design test cases that verify the expected functionality or behaviour . Specification-based testing can also be time-consuming and may not be suitable or efficient when testing time is very limited . Option D is not a good option, because use case testing is a type of technique that requires analysing the use cases or scenarios of the software under test to design test cases that verify the end-to-end user interactions and outcomes . Use case testing can also be time-consuming and may not be relevant or effective when testing time is very limited .

The test execution schedule would not be expected to see on an incident report from test execution, because it is not related to the incident itself, but rather to the overall plan and progress of testing . An incident report is a document that records any event that deviates from the expected or desired behaviour of the software under test . The other options are information that would be expected to see on an incident report from test execution. Option A is expected, because the version(s) of the software under test can help to identify and reproduce the incident . Option C is expected, because the expected results and actual results can help to describe and demonstrate the incident . Option D is expected, because the precise steps to reproduce the problem can help to analyse and resolve the incident .

Event B from S2 is an invalid transition, because it does not exist in the state table. The state table shows the possible transitions between states based on events. For each state, there is a corresponding row that indicates the next state for each event. For example, for state S1, the next state for event A is S2, for event B is S3, and so on.However, for state S2, there is no next state for event B, which means that this transition is invalid

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.

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.

Decision testing is a white box (structure-based) test case design technique1.White box (structure-based) test case design techniques are techniques that use the structure or logic of the source code as a test basis to derive test cases and measure test coverage1.Decision testing is a technique that uses decisions (or branches) in the source code as a test basis to measure the coverage achieved by a test suite1.A decision (or branch) is a point in the source code where the control flow can take two or more alternative paths based on a condition1.Decision testing requires every decision (or branch) in the source code to take both true and false outcomes at least once by a test suite1. Therefore, decision testing is a white box (structure-based) test case design technique.

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.