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

A testing design technique based in the system requirements. Decision table testing is a black-box testing technique that is used to test complex business rules or logic that involve multiple conditions and actions. Decision table testing uses a tabular format to represent all possible combinations of inputs (conditions) and outputs (actions) for a given decision. Decision table testing helps to ensure that all scenarios are covered and tested. A detailed explanation of decision table testing can be found in A Study Guide to the ISTQB® Foundation Level 2018 Syllabus, pages 47-511.

Testing is the process of evaluating a software product by learning about it through exploration and experimentation, which includes running tests, observing outcomes, making inferences, and creating and refining test ideas. Testing has many objectives, such as finding defects, providing information, improving quality, reducing risks, etc. One of the objectives of testing is preventing defects, which means avoiding or minimizing the occurrence of defects in the software product by applying good practices and techniques throughout the software development life cycle. Preventing defects can help to save time, cost, and effort in testing and development, and improve customer satisfaction and confidence. A detailed explanation of testing objectives can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], pages 7-8.

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 analysis and design is the activity in the fundamental test process that includes identifying necessary test data. Test data are the inputs that are used to execute the test cases and verify the expected results2 defines this activity as follows:

Test analysis and design has the following major tasks:

• Reviewing the test basis (such as requirements, risk analysis reports, design documents or code).
• Identifying test conditions based on analysis of test items, specifications, behavior and structure of the software.
• Designing high-level test cases based on test conditions and designing techniques.
• Evaluating testability of requirements and system under test.
• Defining exit criteria.

Evaluating exit criteria and reporting (A) is part of the test closure activities, where the results of testing are evaluated against the defined objectives. Test implementation and execution (B) is where the test cases are executed using the identified test data and deviations from expected results are documented. Test planning and control © is where the overall approach and resources for testing are defined and monitored.

According to the syllabus, traceability between the test basis and test work products is the ability to link each element of the test basis to the various test work products associated with that element, such as test conditions, test cases, test procedures, and test results. Traceability between the test basis and test work products has several benefits, such as evaluating the extent of test coverage, analyzing the impact of changes, making testing auditable, meeting IT governance criteria, improving the understandability of test reports, and providing information to assess product quality, process capability, and project progress. The answer B is incorrect because it is not a benefit of traceability between the test basis and test work products. It obscures the impact of changes. On the contrary, traceability helps to reveal the impact of changes by showing which elements of the test basis are affected by a change and which test work products need to be updated or executed accordingly. The other answers are correct because they are examples of benefits of traceability between the test basis and test work products.

References: Certified Tester Foundation Level Syllabus, Section 1.4.4, page 18-19.

b & c are debugging activities, because they involve locating the cause of failure and fixing the defect in the software . Debugging is the process of finding and removing the causes of software failures . The other options are not debugging activities, but rather testing activities. Option A is a testing activity, because it involves identifying a failure in the software by comparing the expected and actual results . Option D is a testing activity, because it involves checking the fix has resolved the failure by re-testing the software .

To achieve 100% statement coverage, we need to execute every statement in the code at least once. To achieve 100% decision coverage, we need to execute every possible outcome of every decision in the code at least once. In this case, we can use the following test cases to cover both statement and decision coverage:

• A = 5, B = 4, C = 3, D = 2, E = 1
• A = 1, B = 2, C = 3, D = 4, E = 5
• A = 3, B = 4, C = 5, D = 2, E = 1
• A = 3, B = 2, C = 1, D = 4, E = 5

These four test cases will cover all the statements and all the possible outcomes of the decisions in the code. Therefore, the minimum number of test cases required to achieve both statement and decision coverage is four.

References: Certified Tester Foundation Level Syllabus, Section 4.3.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