Software Testing Principles and Techniques

False (B)

High probability of finding an error

<p>pareto</p> Signup and view all the answers

<p>Developer = Understands the system, tests gently, driven by delivery Independent Tester = Learns the system, attempts to break it, driven by quality</p> Signup and view all the answers

<p>Customer requirements (C)</p> Signup and view all the answers

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

<p>Controllability</p> Signup and view all the answers

<p>Evaluating inputs and outputs without internal knowledge (B)</p> Signup and view all the answers

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

<p>It is a technique that divides input values into valid and invalid partitions to select representative values for testing.</p> Signup and view all the answers

<p>Equivalence Partitioning</p> Signup and view all the answers

<p>Branch And Decision Coverage (B)</p> Signup and view all the answers

<p>Equivalence Partitioning = Black Box Testing Statement Coverage = White Box Testing Boundary Value Analysis = Black Box Testing Path Coverage = White Box Testing</p> Signup and view all the answers

<p>Glass Box Testing (B)</p> Signup and view all the answers

<p>Stability refers to having few changes requested during testing.</p> Signup and view all the answers

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

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

<p>Tom Macabe</p> Signup and view all the answers

<p>control</p> Signup and view all the answers

<p>Independent Paths = Paths executed during testing Logical Decisions = True and false sides exercised Loops = Boundaries and operational bounds exercised Internal Data Structures = Validity checks performed</p> Signup and view all the answers

<p>Input values at and around boundaries (B)</p> Signup and view all the answers

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

<p>To test the functionality of the program without considering the internal structure.</p> Signup and view all the answers

<p>input conditions</p> Signup and view all the answers

<p>Black Box Testing = Focus on external functionality White Box Testing = Examine internal logical paths Boundary Value Analysis = Test at value boundaries Exhaustive Testing = Test all possible paths</p> Signup and view all the answers

<p>The number of paths can be as high as $10^{14}$. (D)</p> Signup and view all the answers

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

<p>An integrated testing approach</p> Signup and view all the answers

The process of deliberately executing a program with the goal of uncovering errors before it's delivered to users.

The idea that the software developer should not assume their code is perfect, but instead should actively seek out errors.

The primary goal of software testing is to identify different types of errors with minimal effort and time. However, it cannot prove the absence of errors; it can only indicate their presence.

Testing should be designed to identify errors that are most critical to the customer, as their satisfaction is paramount.

The principle that 80% of errors stem from 20% of a program's code. This emphasizes targeted testing efforts.

Testing should be planned well in advance of actual execution. This ensures a systematic and comprehensive approach.

A good test has a high chance of finding an error and doesn't duplicate the purpose of other tests. It should strike a balance between simplicity and complexity.

Testability refers to how easily a software system can be tested. It encompasses four key characteristics: operability, observability, controllability, and decomposability.

Testing where you only focus on the inputs and outputs of a system, without knowing the internal workings.

Test cases are carefully designed to cover a wide range of input values, making sure to test both valid and invalid inputs.

A test case design technique targeting the boundaries between valid and invalid input values, as errors often occur at these transitions.

A technique that uses a table to identify all possible combinations of inputs and their corresponding outputs, leading to a comprehensive set of test cases.

In contrast to black box testing, this focuses on the internal structure and logic of the software, aiming to test individual units, modules, and code paths.

A type of white box testing that measures how much of the program's code has been executed by the tests.

A type of coverage testing that aims to execute each line of code at least once.

A type of coverage testing that goes beyond statement coverage to test every branch and decision point in the code, ensuring all possible execution paths are covered.

Testing that examines the internal workings of a software program by analyzing its logical structure and code paths.

This type of testing aims to exhaustively test all possible execution paths within a software program.

Testing that strategically focuses on selected paths within a program, considering factors such as critical functionalities or potential error-prone areas.

A testing technique that focuses on the software's functionality from the user's perspective, without examining its internal structure or code.

Combines the strengths of both white-box and black-box testing, validating the software interface while also ensuring the internal workings are correct.

The number of possible paths within a program can be astronomically large, making it impractical or impossible to exhaustively test all paths.

A structured approach to white-box testing that ensures all statements in a program are executed at least once during testing. It uses flow-graph notation to visualize the program's structure and identify all possible execution paths.

It guarantees that every possible path within a module is tested, ensuring all logical decisions are checked in both true and false conditions. It also verifies loop execution boundaries and the validity of internal data structures.

Logical errors are more likely to occur in less-traveled execution paths, which often involve 'special case' processing. White-box testing helps uncover these hidden bugs by meticulously examining all code paths, including those that might seem unlikely to be executed.

White-box testing focuses on ensuring that all statements and conditions within the program are executed at least once during testing. This comprehensive approach helps reveal potential errors and ensure code quality.