Software Testing Concepts Quiz

The primary goal of structural testing is to test as much of the program as possible.

Nodes represent sequential statements or blocks of code, while edges represent the transfer of processing control.

Test coverage is the minimal set of test cases that ensure certain criteria are satisfied, and it is important to determine how effectively a set of tests validates the program.

<p>Statement testing involves designing test cases to execute every source statement in the software at least once.</p> Signup and view all the answers

<p>Iterations introduce multiple unique routes as each loop iteration can be considered a different path.</p> Signup and view all the answers

<p>Software testing is the process of evaluating and verifying that a piece of software meets its pre-determined purpose.</p> Signup and view all the answers

<p>An error is a mistake made by a person, while a fault is a defect in the software caused by that error.</p> Signup and view all the answers

<p>A good test case is designed to have a high probability of detecting any undiscovered errors in the software.</p> Signup and view all the answers

<p>Structural testing, also known as white-box or glass-box testing, involves testing based on the internal code structure of the software.</p> Signup and view all the answers

<p>A test plan should include the testing approach, responsibilities, specific tests to run, and organization of the testing effort.</p> Signup and view all the answers

<p>A fault may cause a software failure, but it does not always lead to one, as failure is the observed departure from expected behavior.</p> Signup and view all the answers

<p>Testing at different stages helps identify defects early, ensuring better quality and reducing costs related to fixing errors later.</p> Signup and view all the answers

<p>'Fit for purpose' means that the software meets and exceeds the outlined requirements effectively.</p> Signup and view all the answers

<p>Branch testing ensures each decision has both TRUE and FALSE outcomes executed. In the example, 2 tests are sufficient.</p> Signup and view all the answers

<p>Three test cases are necessary to cover all conditions: A TRUE, B TRUE; A FALSE, B TRUE, C TRUE; A FALSE, B FALSE.</p> Signup and view all the answers

<p>Decision/condition testing requires that both each condition and each decision outcome are executed at least once, ensuring robust testing of logic.</p> Signup and view all the answers

<p>The goal of multiple condition testing is to design test cases that invoke all possible combinations of TRUE and FALSE outcomes in each decision.</p> Signup and view all the answers

<p>Path testing involves designing test cases that execute each unique path from start to end within the program at least once.</p> Signup and view all the answers

<p>The issue with loops is that each iteration is a different path, and if N is infinite, it can lead to a complex testing scenario.</p> Signup and view all the answers

<p>Data flow classifies variable occurrences into definitions and uses, specifically identifying when a variable is defined or referenced.</p> Signup and view all the answers

<p>You would apply path testing to guarantee that each unique route through the program is tested.</p> Signup and view all the answers

<p>A d-u pair represents the definition (D) of a variable and its subsequent use (U) in program statements.</p> Signup and view all the answers

<p>Data flow testing analyzes the use of variables to find issues like undeclared variables or those that are defined multiple times before being used.</p> Signup and view all the answers

<p>The primary advantage is its ability to identify variables that are declared but not used or declared multiple times.</p> Signup and view all the answers

<p>A main weakness is that it does not effectively handle compound variables, such as arrays.</p> Signup and view all the answers

<p>Equivalence partitioning divides input data into subsets to reduce the number of test cases while ensuring coverage of all possible scenarios.</p> Signup and view all the answers

<p>Boundary value analysis is important because it focuses on values at the edges of input ranges, which are often where errors occur.</p> Signup and view all the answers

<p>Deriving tests from the unit specification ensures that the tests are aligned with the intended functionality and requirements of the unit.</p> Signup and view all the answers

<p>A potential issue is that the quality of functional testing heavily relies on the clarity, completeness, and accuracy of the requirement specifications.</p> Signup and view all the answers

A representation of a program's execution flow using nodes (code blocks) and edges (control transfers).

A unique path through the program from start to finish, considering each iteration of a loop as a separate path.

A minimum set of test cases required to meet coverage criteria.

A technique that aims to execute every line of code in a program at least once.

Tests based on the requirements specification of the software, without necessarily knowing the internal code structure.

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

The process of evaluating and verifying that a piece of software meets its intended purpose.

Mistakes made by humans during software development.

Problems in software caused by errors. They can lead to failures, but not always.

When software fails to operate as expected.

A test that has a high chance of finding a previously undetected error.

A static examination of software output, typically done early in the development process.

Tests based on analyzing the internal structure of the software. The source code is visible.

Each branch in a decision (e.g., an IF statement) is executed at least once with both TRUE and FALSE outcomes.

Each condition within a decision is tested, both TRUE and FALSE, at least once.

Combines branch and condition testing, ensuring all conditions and decisions are covered.

All possible combinations of TRUE and FALSE for conditions within a decision are tested.

Each unique path through the program, from start to end, is executed at least once.

Loops can present a challenge because each iteration creates a new path, potentially leading to an infinite number of tests. Strategies are needed to address this.

Each variable's usage in a program is classified as a 'Definition' if it's assigned a value for the first time.

Data flow testing analyzes how variables are used throughout a program to identify potential errors.

A variable is defined when it is declared, and given an initial value. It is used when it is referenced in a program statement, such as an output statement, an expression, or a condition. For example, if a variable 'x' is declared as x = 5, it is defined, and if it is later used in a statement like 'print(x)', it is being used.

A test case is a specific input or set of inputs that is used to test a piece of software. To ensure thorough testing, we want to design test cases that exercise every d-u pair at least once. This means that each variable is both defined and used at least once in our tests. This helps ensure that each variable is working correctly throughout the code.

This technique partitions the possible inputs into subsets that the software is expected to handle in the same way according to the requirements document. It helps you choose a representative test input from each subset, ensuring your tests cover a wide range of potential usage scenarios.

This testing technique focuses on the boundaries between equivalence partitions – the 'edges' of input values. It helps you find errors that may occur when the input values are at or near these boundaries. Select test values that fall right on the boundary and one value on either side of it.

This type of testing analyzes software units, the smallest testable part of a program, to ensure each unit functions correctly. This is done by deriving test cases from the unit's specifications.

This method creates test cases by analyzing the requirements specification. However, its reliability depends heavily on the quality of the requirements document. If the documentation is unclear, incomplete, inconsistent, inaccurate, or untestable, the resulting tests might not accurately reflect the intended functionality of the software.