Unit 1: Fundamentals of Testing Vocabulary

Software Testing

The process of evaluating and verifying that a software product or application functions correctly, securely, and efficiently according to its specific requirements, and identifying differences between expected and actual results.

Verification

The process of evaluating work-products of a development phase to determine whether they meet the specified requirements, addressing the question: "Are we building the product right?"

Validation

The process of evaluating software to determine whether it satisfies user needs and expectations in real-world use, addressing the question: "Are we building the right product?"

Verification vs. Validation Comparison

A comparative overview detailing the distinct purposes, focus areas, primary performers, and key questions associated with verification and validation activities.

Static Testing

Testing activities performed without executing code, such as reviewing requirements, design documents, user stories, inspecting code or models, and static analysis.

Dynamic Testing

Testing activities performed by executing code, inputting test data, observing results, and comparing actual outcomes against expected outcomes.

Test Objective

The overall goal or purpose of performing a specific test activity, derived from the requirements specification and test basis (e.g., finding defects, gaining confidence, reducing risks).

Test Object

The component, system, or feature being tested, also referred to as the System Under Test (SUT).

Acceptance Criteria

Specific, measurable pass/fail conditions that a product must meet to be accepted by the customer or stakeholders.

Debugging

The process of identifying the cause of a defect, correcting the code, and confirming the fix, typically performed by developers.

Exhaustive Testing

The concept of testing all possible inputs, execution paths, and scenarios in a software system, which is practically impossible due to infinite combinations and time limits.

Prioritization in Testing

The process of deciding what to test first and most thoroughly based on factors like risk level, business impact, usage frequency, code complexity, and defect history.

Test Process in Software Testing

The end-to-end testing workflow consisting of Requirements Analysis, Test Planning, Test Design, Test Execution, Defect Reporting, Retesting, and Test Closure.

Cost of Defects

A model illustrating that defect repair costs increase exponentially as a product moves further through the software development cycle, ranging from $1\times$