iSQI CTFL_Syll2018 - ISTQB Certified Tester Foundation Level (Syllabus 2018)

Dynamic analysis tools are used to find defects, such as memory leaks, while software is executing. Dynamic analysis tools monitor the behavior and performance of the software under various conditions and report on any anomalies or errors. Dynamic analysis tools are not used to determine differences between files or databases, which is a function of comparison tools. Dynamic analysis tools are not used to measure the percentage of specific types of code structure that have been exercised, which is a function of code coverage tools.

Exhaustive testing is a technique that covers all possible combinations of inputs and preconditions2. However, it is not recommended to perform exhaustive testing, as it is usually impractical and impossible due to the large number of test cases required2. Instead, risk analysis and priorities should be used to focus testing efforts on the most important and critical aspects of the system under test2.

It can be done without reference to the internal structure of the component or system. Black-box testing techniques are based on the external behavior and functionality of the system, not on its internal structure or code. Black-box testing techniques include equivalence partitioning, boundary value analysis, decision table testing, state transition testing, use case testing, etc. A detailed explanation of black-box testing techniques can be found in A Study Guide to the ISTQB® Foundation Level 2018 Syllabus, pages 25-601.

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.

This is the definition of a data driven approach to test automation design, which allows for reusability and maintainability of test scripts. Option A describes a keyword driven approach, which uses action words to describe the test steps and data. Option B is not related to test automation design, but rather to performance testing. Option C is also not related to test automation design, but rather to a testing technique.

 According to the 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 (i), (iii), and (iv) are part of an incident report based on IEEE 829.

Testing has several objectives that aim to provide information and confidence about the quality and risk level of the software product and to support decision-making and improvement processes. Some of these objectives are:

Finding defects: Testing is the process of finding defects or failures in the software product that do not meet its requirements or expectations.

Providing information for decision-making: Testing is the process of providing information about the quality and risk level of the software product based on the observed behavior and results under certain conditions and assumptions. This information can help stakeholders make informed decisions about releasing, deploying, accepting, or improving the software product.

Gaining confidence about the level of quality of the software: Testing is the process of gaining confidence that the software product meets its requirements and expectations and provides value to the users and customers.

Analyzing and removing the cause of failures: Testing is not only the process of finding defects but also the process of analyzing and removing the cause of failures that lead to defects. This objective is related to debugging, which is a development activity that involves locating, diagnosing, and fixing errors in the code or design of the software product.

You can find more information about the objectives of testing in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], Chapter 1, Section 1.2.

Maintenance testing is a type of testing that is performed after a software product has been delivered and deployed to ensure that it still meets its requirements and functions correctly after changes have been made to it or to its environment. Changes can include corrective changes (fixing defects), adaptive changes (adapting to new platforms or environments), perfective changes (improving performance or usability), or preventive changes (avoiding potential problems). One of the appropriate reasons for maintenance testing is to verify that the software product works as expected after upgrading the operating system, which is an example of an adaptive change. Other reasons for maintenance testing can include verifying that the software product works as expected after fixing defects, adding new features, improving performance, or preventing future issues. You can find more information about maintenance testing in Software Testing Foundations: A Study Guide for the Certified Tester Exam, Chapter 12.

Confirmation testing, also known as re-testing, is the process of testing a defect that has been fixed to verify that it has been resolved and does not affect other parts of the system. Confirmation testing is usually done by the same tester who reported the defect and using the same test case that revealed the defect. You can find more information about confirmation testing in A Study Guide to the ISTQB® Foundation Level 2018 Syllabus, Chapter 3, Section 3.21.