Software Testing Techniques

Methods for deriving test cases from requirements, specifications, and code to ensure well-structured tests.

Testing the software without knowledge of its internal structure, based on requirements and specifications.

Dividing input data into classes expected to be processed similarly; one test case represents each partition.

Testing values at the edges of equivalence partitions, including minimum, maximum, and values just inside/outside boundaries.

A structured way to represent all possible combinations of conditions and their corresponding actions in a system.

Testing based on system states and transitions between them, covering all possible state transitions.

Testing software with knowledge of its internal structure and code, covering specific paths.

Ensuring every statement in the code is executed at least once.

Ensuring every branch (outcome of a decision) in the code is executed at least once.

Ensuring that every possible path through the code is executed at least once.

Relying on the tester's knowledge and experience to design test cases, anticipating potential errors.

Anticipating potential errors based on past experiences and domain knowledge to create targeted test cases.

A dynamic approach where test design, execution, and evaluation are performed concurrently.

Testing non-functional aspects like performance, security, reliability, and usability.

Evaluating speed, stability, and scalability under various conditions.

Assesses the system's performance under normal and peak load conditions

Evaluating the system's behavior under extreme load conditions to identify breaking points.

Assessing the system's performance over a prolonged period to identify memory leaks or other issues.

Evaluating the software's ability to protect data and prevent unauthorized access.

Evaluating the software's ability to perform its intended function without failure for a specified period.

Evaluating the ease of use and user-friendliness of the software.

Evaluating the ease with which software can be modified, corrected, adapted, and enhanced.

A set of activities designed to ensure that software meets specified quality standards, preventing defects.

Planning, organizing, and controlling the testing process to align with project goals.

Defining the scope, objectives, and approach of testing, outlining activities, resources, and schedule.

Defining the roles and responsibilities of the testing team, and establishing communication channels.

Tracking the progress of testing activities and taking corrective actions when necessary.

Managing the versions of software, hardware, and documentation used in testing.

Tracking, reporting, and resolving defects identified during testing.

Fundamental guidelines that help testers perform their work effectively.

Testing can demonstrate the presence of defects, but cannot prove software is defect-free.

Testing all possible combinations of inputs is not feasible except for trivial cases; focus on important areas using risk analysis.

Testing activities should start as early as possible in the software development lifecycle.

Defects tend to cluster in specific areas of the software; a small number of modules usually contain most of the defects.

If the same tests are repeated, they will eventually stop finding new defects; tests need to evolve.

Testing is dependent on the context of the software being tested; different systems require different approaches.

Finding and fixing defects does not guarantee the software is fit for purpose; testing should meet stakeholder needs.