Pass the iSQI CTFL2018 CTFL_Syll2018 Questions and answers with CertsForce

The correct answer is D, as it describes a task that is most likely to be performed by the tester. A tester is a person who performs testing activities such as planning, designing, executing, and evaluating tests2. Creating the detailed test execution schedule is one of these activities, as it involves defining the order and timing of test cases to be executed based on various factors such as dependencies, risks, priorities, and resources2. Option A is incorrect, as it describes a task that is most likely to be performed by the test manager. A test manager is a person who leads and manages testing activities such as establishing test policies and strategies, managing test teams and stakeholders, monitoring and controlling test progress and quality, and reporting on test results2. Developing a test strategy and test policy for the organization is one of these activities, as it involves defining the overall approach and objectives for testing at an organizational level2. Option B is incorrect, as it describes a task that is most likely to be performed by the test analyst. A test analyst is a person who supports testing activities such as analyzing requirements and risks, designing and prioritizing tests, evaluating test coverage and traceability, and reviewing work products2. Introducing suitable metrics for measuring test progress is one of these activities, as it involves defining and collecting quantitative data to monitor and control various aspects of testing such as efficiency, effectiveness, quality, and maturity2. Option C is incorrect, as it describes a task that is most likely to be performed by the test leader. A test leader is a person who coordinates testing activities such as planning and estimating tests, allocating tasks and resources, supervising test execution and evaluation, communicating with stakeholders, and resolving issues2. Promoting and advocating the test team within the organization is one of these activities, as it involves demonstrating the value and benefits of testing to other parties such as management, developers, customers, and users2. References: 2, Section 2.3

Statement testing and decision testing techniques are similar because both are structure-based testing techniques. Structure-based testing techniques, also known as white-box testing or code-based testing, are based on analyzing the internal structure and logic of the software code. Structure-based testing techniques aim to achieve a certain level of coverage of the code elements, such as statements, branches, paths, conditions, etc1 explains structure-based testing techniques as follows:

Structure-based testing techniques (also known as white-box testing techniques or code-based testing techniques) use the information of the internal structure of the component or system to derive test cases. They are commonly used at component testing and component integration testing levels, but can also be used at system and acceptance levels.

The main advantage of structure-based testing techniques is that they can reveal defects that are not easily found by other techniques, such as logic errors, incorrect assumptions, or incomplete paths. The main disadvantage of structure-based testing techniques is that they require access to the source code, which may not be available or feasible in some situations.

Statement testing is a structure-based testing technique that aims to cover all the executable statements in the code at least once. Decision testing is a structure-based testing technique that aims to cover all the possible outcomes of each decision in the code (true and false) at least once.

A, B, and D are incorrect answers. Specification-based testing techniques, experience-based testing techniques, and black box test design techniques are not similar to statement testing and decision testing techniques. Specification-based testing techniques are based on the requirements and functionality of the software rather than its structure and logic. Experience-based testing techniques are based on the knowledge and intuition of the testers rather than any formal analysis or criteria. Black box test design techniques are based on the external behavior and output of the software rather than its internal structure and logic.

The correct answer is C, as it is an example of a project risk. A project risk is a risk that affects the management and control of the testing project, such as planning, budget, schedule, resources, quality, or scope1. Team members’ skills may not be sufficient for the assigned work is a project risk, as it affects the quality and efficiency of the testing activities1. Option A is incorrect, as it is an example of a product risk. A product risk is a risk that affects the quality of the software product under test, such as functionality, reliability, usability, security, or performance1. A system architecture may not support some non-functional requirements is a product risk, as it affects the reliability and performance of the software product1. Option B is incorrect, as it is an example of a defect. A defect is a flaw in the software product that causes it to produce incorrect or unexpected results or behavior1. A computation is not always performed correctly in some situations is a defect, as it causes the software product to produce incorrect results1. Option D is incorrect, as it is an example of a defect. A defect is a flaw in the software product that causes it to produce incorrect or unexpected results or behavior1. Specific modules do not adequately meet their intended functions according to the user is a defect, as it causes the software product to produce unexpected behavior1. References: 1, Section 2.8

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.

According to the syllabus, decision coverage is a technique that measures the percentage of decision outcomes that have been exercised by a test suite. A decision outcome is the result of evaluating a boolean expression in a control structure, such as an if statement or a switch statement. The goal of decision coverage testing is to cover and validate all the accessible source code by checking and ensuring that each branch of every possible decision point is executed at least once. The answer C is incorrect because it is not a valid use of decision coverage testing. Decision coverage testing does not check that all decisions are based on a numeric value, as there can be other types of values involved in boolean expressions, such as strings or booleans. The other answers are correct because they are valid uses of decision coverage testing. Checking that all decisions have been exercised in a single program or a business process can help to identify defects or missing functionality in the code or process logic. Checking that at least 100% decision coverage has been achieved can help to ensure that all reachable code has been executed and that 100% statement coverage has been achieved as well.

References: Certified Tester Foundation Level Syllabus, Section 4.2.3, page 42-43.

I and II are false statements about static analysis. Static analysis cannot be used instead of dynamic testing (I), as it cannot verify the behavior or performance of the system under test at runtime. Static analysis can uncover defects like security vulnerabilities (II), as it can detect potential weaknesses or flaws in the source code that may lead to security breaches. defines static analysis as follows:

Static analysis is a type of software testing that analyzes the source code or other software artifacts without executing them. Static analysis can be used to check conformance to specifications and standards, detect syntax and logical errors, measure complexity and quality metrics, identify code smells and bad practices, find potential security vulnerabilities, and improve maintainability and readability.

III and IV are true statements about static analysis. Static analysis can be used to check conformance to specifications and standards (III), as it can compare the source code or other software artifacts against predefined rules or criteria. Static analysis typically detects failures prior to component testing (IV), as it can be performed early in the development cycle before compiling or executing the code.

The correct answer is D, as it describes a test summary report for executive-level employees. A test summary report is a document that summarizes the results and evaluation of testing activities for a specific activity or phase3. It may have different levels of detail and content depending on the intended audience and purpose3. A test summary report for executive-level employees is typically high-level and includes a status summary of defects by priority or budget3. This type of report provides a concise overview of the quality and progress of testing without going into too much detail or technical information3. Option A is incorrect, as it describes a test summary report for technical-level employees. A test summary report for technical-level employees is typically detailed and includes specific information on defects and trends3. This type of report provides a comprehensive analysis of the quality and progress of testing with relevant data and metrics3. Option B is incorrect, as it describes a test summary report that is neither suitable for executive-level nor technical-level employees. A test summary report that is detailed and includes a status summary of defects by priority or budget is too detailed for executive-level employees and too vague for technical-level employees3. Option C is incorrect, as it describes a test summary report that is neither suitable for executive-level nor technical-level employees. A test summary report that is high-level and includes specific information on defects and trends is too high-level for technical-level employees and too specific for executive-level employees3. References: 3, Section 2.7

Variables that are not used or improperly declared are defects that are more likely to be found by a static analysis tool than by other testing techniques, because they are syntactic or structural errors in the code that can be detected without executing the software13. A static analysis tool can analyse the code or design of the software under test and identify errors such as missing declarations, undefined variables, unused variables, or unreachable code13. The other options are not defects that are more likely to be found by a static analysis tool than by other testing techniques. Option A is not a defect that can be found by a static analysis tool, but rather by a requirements review or specification-based testing technique1 . Option B is not a defect that can be found by a static analysis tool, but rather by a structure-based testing technique or a coverage measurement tool1 . Option C is not a defect that can be found by a static analysis tool, but rather by a dynamic analysis tool or a monitoring tool1 .

Error, fault, failure is the option that describes the causal chain in the correct sequence1 . The causal chain is a model that explains how defects are introduced and manifested in software1 . An error is a human action or decision that produces an incorrect result1 . A fault is a defect in the software caused by an error1 . A failure is an incorrect behaviour of the software caused by a fault1 . The other options do not describe the causal chain in the correct sequence. Option B uses synonyms for error (mistake), fault (bug), and failure (defect), but does not follow the correct order. Option C uses synonyms for error (mistake) and fault (failure), but does not follow the correct order and confuses fault with failure. Option D uses synonyms for fault (bug) and error (error), but does not follow the correct order and confuses failure with error.

According to the syllabus, exploratory testing is a technique that involves simultaneous learning, test design and test execution. A tester dynamically designs and executes tests based on their knowledge, exploration of the test item and the results of previous tests. A time-boxed test session is a fixed period of time during which testing is performed. A test charter is a document that contains test objectives, scope, risks and other information to guide the testing. The answer A is correct because it describes an approach that can be used for exploratory testing. The other answers are incorrect because they describe other techniques, such as error guessing (B), compliance testing © and user acceptance testing (D).

References: Certified Tester Foundation Level Syllabus, Section 4.5.2, page 51-52.