Software Quality and Testing Overview

<p>Executing every source statement in the software at least once (A)</p> Signup and view all the answers

<p>To accommodate the inherent flaws of the technique (B)</p> Signup and view all the answers

<p>To evaluate and verify that software fulfills its pre-determined purpose (B)</p> Signup and view all the answers

<p>Failure (B)</p> Signup and view all the answers

<p>High probability of detecting undiscovered errors (A)</p> Signup and view all the answers

<p>Testing derived from analysis of the internal code structure (C)</p> Signup and view all the answers

<p>A mistake made by the developer that may cause failures (C)</p> Signup and view all the answers

<p>Responsibilities and the test approach (A)</p> Signup and view all the answers

<p>You cannot test everything; all testing is sampling (C)</p> Signup and view all the answers

<p>Static examination of an output (A)</p> Signup and view all the answers

<p>Definition-use pair (D)</p> Signup and view all the answers

<p>It can identify variables that are declared but not used. (D)</p> Signup and view all the answers

<p>It does not address multiple paths between d-u pairs. (A)</p> Signup and view all the answers

<p>Unit testing (B)</p> Signup and view all the answers

<p>Identifying categories of inputs that a system treats the same way. (B)</p> Signup and view all the answers

<p>Testing values at the edge and just within or outside the boundaries. (D)</p> Signup and view all the answers

<p>To avoid memory leaks by freeing up resources. (A)</p> Signup and view all the answers

<p>All values from a partition are equal in their likelihood of revealing faults. (D)</p> Signup and view all the answers

<p>Each decision has both TRUE and FALSE outcomes executed at least once. (C)</p> Signup and view all the answers

<p>Two tests covering all combinations. (A)</p> Signup and view all the answers

<p>Both TRUE and FALSE outcomes of every decision and condition are executed at least once. (C)</p> Signup and view all the answers

<p>To cover all possible combinations of TRUE and FALSE outcomes in each decision. (B)</p> Signup and view all the answers

<p>It ensures that every path through the code is executed at least once. (D)</p> Signup and view all the answers

<p>Each loop iteration represents a different path that must be tested. (C)</p> Signup and view all the answers

<p>Definition. (D)</p> Signup and view all the answers

<p>Verifying that all paths in the program are executed. (D)</p> Signup and view all the answers

A list of instructions executed on a computer to achieve a specific goal.

The process of examining and validating if a software product meets its intended purpose.

Human mistakes that can lead to errors in software code.

Problems caused by errors in the software code.

When software doesn't behave as expected.

A planned set of tests to execute, with documented input, output, and expected results.

The specific data used in each test, including input, initial conditions, and expected outcomes.

Analyzing the internal structure of software to design tests that cover all possible code paths.

A visual representation of the program's flow of control, where nodes represent code segments and edges represent transitions between them.

Every possible route through a directed graph, starting from the program's beginning and reaching its end. Loops (iterations) can create multiple paths for each loop iteration.

A set of test cases that aim to cover as much of the program's structure as possible. This can include executing every line of code, reaching every decision point, or ensuring all possible paths are tested.

A testing technique that focuses on executing every line of code at least once. It ensures that all statements are covered, but doesn't necessarily test different execution paths or branches.

A set of test cases derived from the software's requirements specification, ensuring the software functions as intended. The internal code structure is not necessarily known.

A testing technique that ensures each decision point in a code block is executed with both TRUE and FALSE outcomes at least once.

A testing technique where each condition within a decision statement is tested with both TRUE and FALSE outcomes at least once.

Testing technique where each condition and decision in a program is tested at least once with both TRUE and FALSE outcomes.

A testing technique where all possible combinations of TRUE and FALSE outcomes for all conditions within a decision are tested at least once.

A testing technique that aims to execute every possible path through a program at least once. A path refers to a unique sequence of instructions from the start to the end of the program.

A testing technique that categorizes variables based on their role in a piece of code. "D" stands for "Definition" indicating where a variable is initially assigned a value.

A data flow testing path is a pair of program statements: one defining a variable (d) and one using the variable (u).

Each test case should be designed to exercise at least one d-u pair for a specific variable. This ensures that the variable's definition and usage are tested.

Data flow testing focuses on analyzing how data is used within a program. The goal is to ensure that each variable is defined and used correctly within the code.

Finding unused variables, variables used without being declared, variables defined multiple times before use, and problems with deallocating variables are common advantages.

Data flow testing doesn't effectively handle more complex data structures like arrays, and it might miss issues if there are multiple paths between a d-u pair.

Equivalence Partitioning (EV) divides input values into groups that the application processes similarly. Test cases are chosen from each partition for the same way the application processes the given input.

Boundary Value Analysis (BVA) tests values at the edges of each partition identified by Equivalence Partitioning. For example, if a partition is ages 0–18, BVA tests 0, 17, 18, and values just outside the range.

Functional testing aims to verify that the software meets the requirements specified in the user documentation. It ensures the software performs according to intended functionality.