iSQI CTFL_Syll2018 - ISTQB Certified Tester Foundation Level (Syllabus 2018)

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

State transition testing is the most suitable test technique for this situation. State transition testing is a technique that uses scenarios based on state diagrams to test the behavior of a system or component that can change its state in response to events or inputs. A state diagram is a graphical representation of the states that a system or component can be in, the events or inputs that can trigger a change of state (transitions), and the actions or outputs that can occur as a result of a change of state. In this case, the vending machine for light drinks can be modeled as a state diagram with states such as “idle”, “coins inserted”, “drink selected”, “drink dispensed”, “change returned”, “sold out”, etc., and transitions triggered by events such as “button pressed”, “coins inserted”, “drink dispensed”, “change returned”, etc. State transition testing can help design test cases that cover all the possible states and transitions of the vending machine and verify its functionality and usability.

References: Certified Tester Foundation Level Syllabus, Section 4.5.1

Statement coverage is a white-box test technique which focuses on the percentage of executable statements that has been executed by a test suite. This is the best description of statement coverage, as it measures how many statements in the source code have been covered by one or more test cases. Option A is incorrect, as it describes state transition testing, which is a black-box test technique that uses a state table to derive test cases. Option B is incorrect, as it describes error guessing, which is an experience-based test technique in which test cases are based on the tester’s knowledge of past failures. Option D is incorrect, as it describes decision coverage, which is a white-box test technique that covers the decision results which determine the next statement to be executed.

References: , Section 4.2.2

Test implementation and execution is the activity in the fundamental test process that includes test script generation. Test script generation is the process of creating executable test cases from test conditions and test data2 defines this activity as follows:

Test implementation and execution has the following major tasks:

Develop and prioritize test cases, creating test data and writing test procedures.

Check test environment has been set up correctly.

Execute test cases, evaluate results and document deviations from expected results.

Use exit criteria to report on suitability of system under test.

Test closure activities (A) include finalizing and archiving test results, evaluating the test process, identifying areas for improvement, and celebrating achievements. Test analysis and design (B) include reviewing test basis, identifying test conditions, designing high-level test cases, and defining exit criteria. Test planning and control © include defining test objectives, scope, strategy, resources, schedule, risks, and metrics.

 According to the syllabus, there are two main approaches for estimating test effort: metrics-based and expert-based. The metrics-based approach uses metrics from previous similar projects or industry data to calculate the test effort based on the size and complexity of the software under test. The expert-based approach relies on the experience and judgment of the owners of the testing tasks or subject matter experts who provide their estimates based on their knowledge of the software under test. The answer B is correct because it accurately describes the expert-based approach. The other answers are incorrect because they either confuse the metrics-based and expert-based approaches or describe them incorrectly.

References: Certified Tester Foundation Level Syllabus, Section 2.3.1, page 24-25.

The ideal number of regression test cycles is as many as time and budget allow, because regression testing is done to ensure that no new defects have been introduced by changes or fixes in the software, and that all previously fixed defects are still fixed. Therefore, more regression test cycles can increase the confidence in the software quality and reliability.

The correct answer is B, as it defines risk level correctly. Risk level is determined by the likelihood of an event happening and the impact or harm from that event4. Likelihood is the probability or frequency of the event occurring4. Impact is the severity or consequence of the event occurring4. Risk level can be calculated by multiplying likelihood and impact, or by using a risk matrix that assigns risk levels based on different combinations of likelihood and impact4. Option A is incorrect, as it does not define risk level correctly. Risk level is not calculated by adding the probabilities of all planned risks to a project, but by assessing the likelihood and impact of each individual risk4. Option C is incorrect, as it does not define risk level correctly. Risk level is not calculated by dividing the sum of all known risks by the sum of all unknown risks, but by assessing the likelihood and impact of each individual risk4. Option D is incorrect, as it does not define risk level correctly. Risk level is not determined by calculating the absolute value of the sum of all potential issues that may occur on the project, but by assessing the likelihood and impact of each individual risk4. References: 4, Section 2.8

The test execution schedule should follow the priority order of the tests, as well as the dependency constraints. The priority order is given by the user value column, where higher values indicate higher priority. The dependency constraints are given by the dependency column, where a test ID indicates that the test cannot be run until the test with that ID has been successfully completed. Therefore, the test execution schedule should start with the highest priority test that has no dependency, which is test 5. Then, it should continue with the next highest priority test that has no dependency or has a satisfied dependency, which is test 1. Then, it should proceed with test 2, which depends on test 1, and then test 3, which depends on test 2. Finally, it should end with test 4, which depends on test 3. Thus, the test execution schedule that best meets the prioritisation and dependency conditions is 5,1,2,3,4.

References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 Syllabus, Chapter 6.1.2 Test Execution, p. 781; ISTQB Certified Tester Foundation Level (CTFL) v4.0 Sample Exam Questions and Answers, Question 87, p. 242

Exploratory testing is by definition a reactive test approach, because it involves designing and executing tests based on the tester’s knowledge, experience and intuition, and reacting to the actual behavior and feedback of the system under test. Exploratory testing does not follow a predefined test plan or test cases, but rather adapts to the situation and learns from the results.