Pass the iSQI CTFL2018 CTFL_Syll2018 Questions and answers with CertsForce

Statement coverage is not a black box technique, because it requires knowledge of the internal structure of the code. Black box techniques are based on the external behavior and specification of the software, without looking at the code. Equivalence partitioning, state transition testing, and boundary value analysis are all examples of black box techniques12

UAT stands for user acceptance testing, which is a type of testing that verifies that the software product meets the acceptance criteria and expectations of the end users or customers1. A UAT specification is a document that defines the scope, objectives, approach, and criteria for UAT1. Testers should be involved in reviewing a UAT specification at any time before UAT begins, as this can help to ensure that the UAT specification is clear, complete, consistent, testable, and aligned with the user requirements1. Testers can also provide feedback and suggestions to improve the UAT specification and avoid potential issues or conflicts during UAT execution1. Therefore, testers should be involved in reviewing a UAT specification at any time before UAT begins.

These are examples of exit criteria, which are the conditions that must be met before testing can be completed. Exit criteria may also include test coverage measures, residual risk assessment, or stakeholder approval. The other options are not exit criteria, but rather test planning activities.

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.

Boundary Value Analysis is a black-box testing technique that is used to test the boundaries or limits of input or output values for a given system or component. Boundary Value Analysis helps to identify errors at the edges of an input or output domain. For example, in a system designed to work out the employee tax to be paid, there are four boundaries for the salary input: $4,000 (lower boundary for tax free), $5,500 (upper boundary for tax free and lower boundary for 10% tax), $34,000 (upper boundary for 10% tax and lower boundary for 22% tax), and any value above $34,000 (upper boundary for 22% tax and lower boundary for 40% tax). A valid Boundary Value Analysis test case would test one value below, on, and above each boundary. For example, $33,501 is a valid test case because it is one value above the boundary of $34,000. A detailed explanation of Boundary Value Analysis can be found in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], pages 38-41.

Finding defects, gaining confidence about the level of quality and providing information, and preventing defects are all valid test objectives according to the ISTQB Foundation Level syllabus. Debugging the code is not a test objective, because debugging is the process of finding and fixing defects, which is done by developers, not testers3

Metrics are quantitative measures that can be used to monitor and control various aspects of software testing processes and products1. Metrics can be used to monitor progress along with test preparation and execution by providing information about the status of testing activities, such as test planning, test design, test execution, test evaluation, defect management, etc1. Among the options given in this question, only C is a suitable metric for monitoring progress along with test preparation and execution. The failure rate in testing already completed is a metric that measures how many tests have failed out of the total number of tests executed1. This metric can indicate the quality of the software product under test and the effectiveness of the test cases1. It can also help to identify areas that need more attention or improvement in testing1. Therefore, this metric can be used to monitor progress along with test preparation and execution.

Use-case testing is a technique that uses use-cases as a test basis to derive test cases2. A use-case is a description of interactions between actors and a system to achieve a goal2. An actor represents a type of user or anything that interacts with the system2. Use-cases are not the most common test basis for unit testing, as they are more suitable for higher levels of testing such as system or acceptance testing3. An actor is not always a human user, as it can also be another system or device2. Test cases can be based on use-case scenarios, which are sequences of actions and events that occur during a use-case execution2. Use-case testing will often identify gaps not found by testing individual components, as it can reveal missing or incorrect requirements, integration issues, and usability problems.

An incident report is a document that records any event occurring during testing that requires investigation1. An incident report should contain sufficient information to enable reproduction of the incident and resolution of the defect1. According to IEEE 829 Standard for Software Test Documentation, an incident report should contain the following information:

Identifier: A unique identifier for the incident report

Summary: A brief summary of the incident

Incident description: A description of the incident, including:

Date: The date when the incident was observed

Author: The name of the person who reported the incident

Source: The software or system lifecycle process in which the incident was observed

Version: The identification of configuration items of the software or system

Test case: The identification of the test case that caused the incident

Execution phase: The phase of test execution when the incident was observed

Environment: The hardware and software environment in which the incident was observed

Description: A description of the anomaly to enable reproduction of the incident

Expected result: The expected result of the test case

Actual result: The actual result of the test case

Reproducibility: An indication of whether the incident can be reproduced or not

Impact analysis: An analysis of the impact of the incident on other aspects of the software or system

Incident resolution: A description of how the incident was resolved, including:

Resolution date: The date when the incident was resolved

Resolver: The name of the person who resolved the incident

Resolution summary: A brief summary of how the incident was resolved

Status: The current status of the incident (e.g., open, closed, deferred)

Classification information: A classification of the cause and effect of the incident for metrics and reporting purposes

Therefore, among the options given in this question, only D provides the best detail on an incident report. It contains a clear title, a reproducibility indicator, a description that includes both expected and actual results, a reference to the specification document, and a screen shot of the failure. The other options are either missing some important information or providing inaccurate or irrelevant information

Software testing contributes to the quality of delivered software by identifying root causes of defects from past projects and using the lessons learned to improve processes and thus help to reduce the defect count. Software testing is a process of verifying and validating that a software product meets the specified requirements and expectations of the stakeholders1. Software testing can detect defects in the software product and provide information about its quality1. Software testing can also identify root causes of defects from past projects and use the lessons learned to improve processes and thus help to reduce the defect count1. This can be done by using techniques such as root cause analysis, defect prevention, causal analysis, process improvement, etc1. These techniques can help to identify and eliminate the sources of defects in the software development lifecycle and prevent them from recurring in future projects1. Therefore, software testing contributes to the quality of delivered software by identifying root causes of defects from past projects and using the lessons learned to improve processes and thus help to reduce the defect count.