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

The correct answer is A, as it provides the best test execution schedule that takes into account the priorities and technical and logical dependencies.A test execution schedule is a plan that defines the order and timing of test cases to be executed based on various factors such as dependencies, risks, priorities, and resources1. In this case, the factors are the priorities and technical and logical dependencies of the test cases.The priorities are the levels of importance or urgency assigned to the test cases, such as low, medium, or high1.The technical dependencies are the relationships between the test cases that require one test case to be executed before another test case can be executed1.The logical dependencies are the relationships between the test cases that make sense to execute one test case after another test case for better understanding or efficiency1. Option A provides the best test execution schedule that takes into account these factors, as it follows these rules:

Execute high priority test cases before medium or low priority test cases

Execute test cases that have technical dependencies in the correct order

Execute test cases that have logical dependencies in a sensible order

The following table shows how option A follows these rules:

Option B does not follow these rules, as it executes TC1 before TC2, which violates the technical dependency. Option C does not follow these rules, as it executes TC5 before TC6, which violates the logical dependency.Option D does not follow these rules, as it executes TC2 before TC3, which violates the technical dependency.

Reference:1, Section 2.5

The combination of the conditions Valid Card Number (NO) + Purchase Approved (YES) is not feasible, as a purchase cannot be approved with an invalid card number. Therefore, this combination can be ignored in the equivalence partitioning for the different types of credit card. Each type of credit card has two valid equivalence partitions: Valid Card Number (YES) + Purchase Approved (YES) and Valid Card Number (YES) + Purchase Approved (NO). Each type of credit card also has one invalid equivalence partition: Valid Card Number (NO) + Purchase Approved (NO). Therefore, to cover all the combinations of equivalence partitions for the four types of credit card, we need 4 x (2 + 1) = 12 test cases.

A, B, and D are incorrect answers. A implies that there are two equivalence partitions for each type of credit card, which is not true as there are three. B implies that there is only one equivalence partition for each type of credit card, which is not true as there are two valid ones and one invalid one. D implies that there are four equivalence partitions for each type of credit card, which is not true as there are only three.

The user interface being complicated and confusing is not an appropriate part of an incident report covering the observation of a failure during testing, as it is a subjective opinion and not a factual description of the failure.An incident report should include objective and relevant information that can help to identify, reproduce, and resolve the failure3defines an incident report as follows:

An incident report is a document that records the occurrence of an abnormal or unexpected event during testing, such as a deviation from expected results, a defect in the system under test, or a problem in the test environment. An incident report typically includes the following information:

Identifier: A unique identifier for the incident report.

Summary: A brief description of the incident.

Incident details: A detailed description of the incident, including the inputs, expected results, actual results, environment, date and time, severity, priority, and any other relevant information.

Steps to reproduce: A sequence of steps that can be followed to reproduce the incident.

Attachments: Any screenshots, logs, files, or other artifacts that can help to understand or reproduce the incident.

I and II, are false statements about static analysis. Static analysis cannot be used instead of dynamic testing (I), as it cannot verify the behavior or performance of the system under test at runtime. Static analysis can uncover defects like security vulnerabilities (II,), as it can detect potential weaknesses or flaws in the source code that may lead to security breaches. defines static analysis as follows:

Static analysis is a type of software testing that analyzes the source code or other software artifacts without executing them. Static analysis can be used to check conformance to specifications and standards, detect syntax and logical errors, measure complexity and quality metrics, identify code smells and bad practices, find potential security vulnerabilities, and improve maintainability and readability.

II,I and IV are true statements about static analysis. Static analysis can be used to check conformance to specifications and standards (II,I), as it can compare the source code or other software artifacts against predefined rules or criteria. Static analysis typically detects failures prior to component testing (IV), as it can be performed early in the development cycle before compiling or executing the code.