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

It describes how test cases are derived from a use case. A use case is a description of a set of sequences of actions, including variants, that a system performs to yield an observable result of value to an actor1. An actor can be a human user or another system. Test cases are designed to cover various user behaviors, including basic, exceptional or alternative and error behaviors associated with each use case1. Option A is incorrect, as test cases derived from a use case are not based on non-functional requirements such as usability, but on functional requirements that describe what the system does1. Option C is incorrect, as test cases derived from a use case are not created using white-box test techniques, but using black-box test techniques that focus on the inputs and outputs of the system1. Option D is incorrect, as test cases derived from a use case are not based on pair testing, which is a technique that involves two testers working together to find defects1. References: 1, Section 4.2.4

An item or event that could be verified by one or more test cases. A test condition is a general term that refers to anything that can be tested by a test case, such as a requirement, a function, a feature, a use case, a user story, etc. A test condition is derived from the test basis (the source of information for testing) and serves as an input for test design and test case creation. A test condition can be expressed in natural language or in a formal notation. A detailed explanation of test condition can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], pages 17-18.

100% branch coverage means 100% statement coverage, but not vice-versa. Branch coverage is a stronger criterion than statement coverage, as it requires that every possible outcome of each decision point is executed at least once. Statement coverage only requires that every executable statement is executed at least once1 explains this as follows:

Branch Coverage (also known as Decision Coverage) measures which possible branches in flow control structures are followed. Branch Coverage is a testing method, which aims to ensure that each one of the possible branch from each decision point is executed at least once and thereby ensuring that all reachable code is executed.

Statement Coverage measures the number of statements in the source code that are executed during the test. Statement Coverage is a metric, which is used to calculate and measure the number of statements in the source code which have been executed during testing.

B, C, and D are false statements. 100% statement coverage does not mean 100% branch coverage (B), as there may be some branches that are not covered by the test cases. 100% branch coverage does not mean 100% statement coverage and vice-versa ©, as branch coverage implies statement coverage but not the other way around. It is possible to achieve 100% statement coverage (D), but it may not be feasible or cost-effective for some systems.