Pass the iSQI CTFL2018 CTFL_Syll2018 Questions and answers with ExamsMirror

 The correct roles and responsibilities in a formal review are as follows1:

Review Leader - Plans and leads the review process

Scribe - Documents all issues raised during the review meeting

Author - Creates the work product under review

Facilitator - Supports the review leader in conducting the review process

Reviewers - Identify potential defects in the work product under review

Therefore, option B is the correct answer, as it correctly matches the role of scribe with the responsibility of collating potential defects found during the individual review activity. Options A, C, and D are incorrect, as they do not match the roles and responsibilities correctly. References: 1, Section 3.2.3

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

Using boundary analysis for x, the test cases are required to cover the values on and around the boundaries of x > 0 and x < 100. Therefore, the test cases should include -1, 0, 1, 99, 100, and 101. The value 0.1 is not a boundary value, and the values -500 and 500 are too far from the boundaries to be relevant.

References: Certified Tester Foundation Level (CTFL) Syllabus - ASTQB, Section 4.2.2, Page 34

Test design is the process of transforming general testing objectives into tangible test conditions and test cases that can be executed and verified against expected results. Test design involves identifying test techniques, coverage criteria, input data, expected outcomes and other test parameters.

  A bug report is a document that records the details of a defect or failure found during testing, such as the steps to reproduce, the expected and actual results, the severity and priority, etc. A bug report should also include any observations or suggestions that may help correct the bug, such as the possible cause, the affected components, the related requirements, etc. This information can help the developers to locate and fix the bug more efficiently and effectively. Therefore, if a tester thinks of a likely cause for a specific bug, they should make a comment about it in the bug report.

References: Certified Tester Foundation Level Syllabus, Section 6.

The order in which the specifications for test cases, test conditions and test procedures are developed as a part of the test development process is as follows:

Test Condition: A test condition is an item or event of a component or system that could be verified by one or more test cases, such as a function, transaction, feature, quality attribute, or structural element.

Test Case: A test case is a set of input values, execution preconditions, expected results and execution postconditions, developed for a particular objective or test condition, such as to exercise a particular program path or to verify compliance with a specific requirement.

Test Procedure: A test procedure is a document providing detailed instructions for the execution of one or more test cases.

Therefore, the correct order is test condition --> test case --> test procedure.

References: [Certified Tester Foundation Level Syllabus], Section 4.2.1 and Glossary

 The three ages that would test all valid equivalence partitions and therefore test rate A, B and C are 20, 35 and 65. Equivalence partitioning is a technique to divide a set of possible inputs or outputs into classes that are expected to behave similarly or produce similar results. For each equivalence class, only one test case is required to represent the whole class. In this case, we can identify the following equivalence classes for the age of the driver:

Valid age between 17 and 25 inclusive (rate A)

Valid age between 26 and 50 inclusive (rate B)

Valid age over 50 (rate C)

Invalid age below 17

Invalid age above 100

Therefore, three test cases are required to test all valid equivalence partitions, and any value within each class can be used as a representative value. For example, 20 for rate A, 35 for rate B, and 65 for rate C.

References: Certified Tester Foundation Level Syllabus, Section 4.4.1

Maintenance testing is triggered by changes, such as migration, retirement, or enhancement of a system1. Therefore, option A is the best example of a trigger for maintenance testing. Options B, C, and D are examples of triggers for development testing, not maintenance testing1. References: 1, Section 2.3.2

Statement I is true, as test planning activities include defining the test object, which is the component or system to be tested. Statement II is false, as test strategy implementation is part of test planning and involves defining the test approach and test levels to be applied. Statement III is true, as test design activities include choosing appropriate test techniques to derive test cases from test conditions. Statement IV is true, as test planning activities include defining and updating the test schedule and exit criteria throughout the project lifecycle. References: ISTQB Certified Tester Foundation Level Syllabus 2018, Section 2.1

The correct answer is C, as it describes a benefit of test automation. Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions1. Test automation can have many benefits, such as reduction in repetitive manual work1. This can improve the efficiency and effectiveness of testing by saving time, effort, and resources1. Option A is incorrect, as it does not describe a benefit of test automation, but a factor that influences the selection of test automation tools. Availability of the test automation tool vendor is a factor that affects the availability and support of the tool, which may affect the success of test automation1. Option B is incorrect, as it does not describe a benefit of test automation, but a misconception. Negligible effort to maintain the test assets generated by the tool is not true, as test automation requires regular maintenance and update of the test scripts, data, and expected results to cope with changes in the software under test1. Option D is incorrect, as it does not describe a benefit of test automation, but a drawback. More subjective assessment is not a benefit, as test automation may introduce bias and errors in the test results due to human factors such as lack of skills, knowledge, or experience1. References: 1, Section 2.10