Software Testing Principles and Practices

An approach to software testing that emphasizes applying general, well-defined test criteria to analyze the software's structure or model.

A type of software testing that involves evaluating code and design to uncover potential errors.

A type of software testing that involves executing the software with various inputs to observe its actual behavior.

Types of software such as object-oriented (OO) systems, web applications, and embedded systems.

Materials that supplement the textbook for instructors, offering solutions, presentation slides, and additional learning resources.

A digital platform hosting supplemental resources such as solutions, presentations, and test tools for the book.

A professional who designs, develops, and maintains software systems.

A recognized professional achievement awarded for exceptionally high teaching quality.

A type of software testing that uses pre-defined criteria to assess the software's structure or model, enabling systematic and thorough testing.

Testing software by analyzing the design and structure, much like understanding a machine's blueprints.

Testing software by focusing on what the software is supposed to do, similar to checking a recipe for its intended outcome.

Software testing that focuses on preventing defects, like wearing a helmet to prevent injury.

Software testing performed to identify and isolate defects, like fixing a broken car engine.

Testing a new software feature or update, just like testing a new software release.

A method of testing that ensures different parts of a software system work together harmoniously.

A structured approach to testing that outlines the procedures, methods, and objectives for testing a software system.

Detailed documents that define the goals, scope, and procedures for different phases of software testing.

Identifying the expected and correct outputs for various test cases.

A type of testing that focuses on the unique characteristics and complexities of object-oriented software. It assesses object interactions, inheritance, and polymorphism.

This involves assessing the functionality, performance, and usability of web applications and services.

It entails testing the usability, accessibility, and responsiveness of the graphical user interface of an application.

The process of creating, executing, and analyzing software tests to identify and fix defects.

A test engineer creates test designs based on the software's requirements. These designs are then turned into executable tests, which are run on the software to evaluate its functionality.

A person who manages and oversees the overall software testing process, ensuring it follows established procedures and meets project goals.

These are specific criteria used to guide the selection of test cases, ensuring thorough testing and adequate coverage of the software's functionality.

These criteria provide stopping rules for the test engineers, indicating when enough testing has been done to reach a desired level of confidence in the software's quality.

Running executable test cases on the software under test (P) and evaluating the outputs to determine if any faults are present.

A type of testing that examines whether the software meets the user's expectations and requirements.

The process of breaking down a software system into components and connectors to fulfill its requirements.

A type of testing that verifies if the assembled system functions as intended after individual components have been tested.

The design stage where individual subsystems are defined to implement specific functions within the overall architecture.

A testing level focused on examining the functionality of individual software components.

A phase where specific details of the software are implemented.

A level of testing that examines the functionality of individual code units or functions.

A model that visualizes the software development process, showing how different testing levels correspond to various design phases.

Mistakes in requirements and high-level design can manifest as faults in the software, often discovered only through extensive testing.

Faults arising from requirements and design errors are often dispersed across multiple software components, making them difficult to isolate and costly to fix.

The process of defining test cases itself can reveal a significant number of requirements and design errors, even if the tests are not actually executed.

A method that helps ensure software functionality aligns with user expectations and needs. It involves understanding how users interact with the software.

The infamous Pentium bug, a flaw in a processor's floating-point unit, highlights the difference between unit testing and system testing. The bug only surfaced during system-wide testing but would not have been detectable during unit testing.