iSQI CTFL_Syll2018 Practice Test Questions Answers

Checklist-based testing is an experience-based test technique whereby the experienced tester uses a high-level list of items to be noted, checked or remembered, or a set of rules or criteria against which a product has to be verified. Checklist-based testing can help the tester to focus on important aspects of the test object and to ensure that nothing is overlooked or forgotten. Checklist-based testing can also help the tester to communicate and report the test results and coverage more effectively.

References: Certified Tester Foundation Level Syllabus, Section 4.6.1

According to the user story checklist, the user story must contain the reason for the need, which is usually expressed by using the word “so that” or “because”. For example, the user story could be rewritten as:

User Story US2018 As a bank account customer, I would like to transfer money from one account to another using the mobile banking application by using the drag and drop feature, so that I can easily manage my finances.

This way, the user story provides a clear value proposition and a justification for the need. The reason also helps to define the scope and priority of the user story, as well as to verify the acceptance criteria.

References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 Syllabus, Chapter 5.2.1 User Stories, p. 62-631; ISTQB Certified Tester Foundation Level (CTFL) v4.0 Sample Exam Questions and Answers, Question 83, p. 232

The software not being able to meet the desired response time is an example of a failure. A failure is an event in which a component or system does not perform a required function within specified limits. A failure is observable by end users or testers as a deviation from expected results. defines a failure as follows:

Failure: Deviation of the component or system from its expected delivery, service or result.

B, C, and D are incorrect answers. The software not being able to meet the desired response time is not an example of a defect (B), an error ©, or not a defect (D). A defect is a flaw in a component or system that can cause it to fail to perform its required function. An error is a human action that produces an incorrect result. Not a defect is a term used to describe an incident report that is rejected or closed as invalid or out of scope. defines these terms as follows:

Defect: A flaw in a component or system that can cause the component or system to fail to perform its required function.

Error: A human action that produces an incorrect result.

Not a defect: An incident report status indicating that there is no defect in relation to this incident report.

A test harness is a test environment comprised of stubs and drivers needed to execute a test, especially when testing components or interfaces. Therefore, option D is correct. Option A is incorrect, as a test harness is not a topic for the final Test Report. Option B is incorrect, as a test harness is not a general name for test data. Option C is incorrect, as a test harness is not a detailed description of a test case.

References: Certified Tester Foundation Level Syllabus, Section 5.3

Every executable statement is covered is the statement that is guaranteed to be true if a program got 100% decision coverage in a test. Decision coverage is a structure-based testing technique that measures how many decision outcomes have been exercised by a set of test cases. A decision is a control structure that has two or more possible outcomes (e.g., if-then-else, switch-case, etc.). Decision coverage requires that each decision outcome is executed at least once by a test case. If a program got 100% decision coverage in a test, it means that every possible outcome of every decision in the code has been covered by at least one test case. This also implies that every executable statement in the code has been covered by at least one test case, since every statement belongs to some decision outcome2 explains decision coverage as follows:

Decision Coverage (also known as Branch Coverage) is a white box testing technique which measures how many decision outcomes have been tested by a set of test cases.

A decision is any control structure where there are two or more possible paths through it (e.g., if-then-else statements, switch-case statements, etc.). Each path through such control structures represents an outcome.

Decision Coverage requires that each outcome from each decision point be executed at least once by one or more test cases.

Decision Coverage can be calculated as follows:

Decision Coverage = (Number of Decision Outcomes Executed / Total Number of Decision Outcomes) * 100%

If Decision Coverage is 100%, it means that every possible outcome from every decision point has been tested by at least one test case. This also means that every executable statement has been tested by at least one test case.

A, B, and C are incorrect answers. Every output equivalence class has been tested (A), every input equivalence class has been tested (B), and the “dead” code has not been covered © are statements that are not guaranteed to be true if a program got 100% decision coverage in a test. Equivalence classes are groups of inputs or outputs that are expected to produce similar results or behavior from the system under test. Equivalence partitioning is a specification-based testing technique that uses equivalence classes to design test cases. Decision coverage is a structure-based testing technique that does not consider equivalence classes, but only the outcomes of the decisions in the code. Therefore, achieving 100% decision coverage does not ensure that every output or input equivalence class has been tested. Dead code is code that can never be executed, regardless of the input values or conditions. Dead code can be caused by logic errors, redundant statements, unreachable branches, etc. Decision coverage does not detect or cover dead code, since it only considers the outcomes of the decisions that can be executed. Therefore, achieving 100% decision coverage does not imply that the dead code has not been covered.