Pass the iSQI CTFL2018 CTFL_Syll2018 Questions and answers with CertsForce

 Equivalence partitioning is a black box test design technique2. A black box technique is a technique that uses the external behaviour or specification of a system as a test basis to derive test cases without referring to its internal structure or logic2. Equivalence partitioning is a technique that divides the input domain of a system into partitions of equivalent data2. Each partition should contain data that is expected to be treated the same by the system2. Therefore, only one test case input from each partition is needed to test the system’s behaviour2. Therefore, equivalence partitioning is a black box test design technique.

The fundamental test process consists of five main activities: test planning and control, test analysis, test design, test implementation and execution, and test evaluation and reporting. During the test analysis activity, the testability of requirements is evaluated, meaning that the requirements are checked for clarity, completeness, consistency, verifiability, etc. Test analysis also involves identifying test conditions based on the test basis, such as requirements, specifications, user stories, or use cases.

References: Certified Tester Foundation Level Syllabus, Section 2.4.1 and 4.2.2

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

 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 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

According to the syllabus, test design is the activity of deriving and specifying test cases from test conditions to test software. Test design involves processes such as identifying test data, designing test scenarios, creating test procedures, and defining expected results. The answer A is correct because it is an example of a task most associated with the test design activity. Test data, derived from production data, is developed for use during testing. The other answers are incorrect because they are examples of tasks associated with other test activities, such as test planning (B), test implementation ©, and test monitoring and control (D).

References: Certified Tester Foundation Level Syllabus, Section 1.4.2, page 16-17.

A peer review is a review done by colleagues at the same organizational level, such as developers, testers, or managers. An informal review without moderator is called a walkthrough. A review done by developers and testers together is called an inspection. A review done by developers only is not a specific type of review.

References: Certified Tester Foundation Level (CTFL) Syllabus - ASTQB, Section 3.1.1, Page 18

According to the syllabus, root cause analysis is a technique that aims to identify and address the underlying causes of defects or problems in a process or system. Root cause analysis involves finding the effect (the observable symptom or outcome of the problem), finding the cause (the factor or factors that directly influence the effect), and finding the root cause (the fundamental reason why the cause exists). The answer C is correct because it most accurately reflects this scenario. The incorrect customer discount is the effect and the reason for the requirement error is the root cause. The other answers are incorrect because they either confuse the effect, cause, and root cause or use incorrect terms.

References: [Certified Tester Foundation Level Syllabus], Section 5.2.1, page 58.

The statement that independent testing is necessary because developers don’t know any testing is wrong. Developers do know some testing, as they perform unit testing and component testing on their own code. However, independent testing is beneficial because it can provide a different perspective and a higher degree of objectivity than testing done by developers. Independent testers may have different skills, knowledge, experience, and expectations than developers, which can help them find different types of defects and improve the quality of the system.

References: Certified Tester Foundation Level Syllabus, Section 2.2

Static testing can prevent defects later in design and coding by uncovering issues in requirements1. This is the best statement of the value of static testing, as it can save time and money by finding defects early in the development process1. Option B is incorrect, as static testing is most effective when performed before dynamic testing1. Option C is incorrect, as static testing can detect different types of defects than those found by dynamic testing, such as inconsistencies, ambiguities, omissions, and incompleteness1. Option D is incorrect, as static testing can improve team member communication by facilitating reviews and inspections1. References: 1, Section 3.1