In context of software testing, which of the following testing is not a level or type of development testing?

Question

Accepted Answer

The correct option is (3):
Release testing is not considered a core *level* or *type* of software *development* testing but rather an activity performed *after* the main development and system testing phases. The established levels of structural and functional testing within the Software Development Life Cycle (SDLC) are Unit Testing, Integration Testing, System Testing, and Acceptance Testing. Release testing specifically focuses on operational assurance—validating a particular version of the system is fit for deployment and customer use outside of the development environment. Its primary goal is to convince the customer or stakeholders that the system is good enough for live use, making it a final quality gate, not a developmental stage for building the software itself.

The incorrect option is (1):
System testing is a recognized, essential level of development testing. It is a form of black-box testing conducted on a complete, fully integrated software system. The purpose is to evaluate the system's compliance with all specified requirements, including both functional aspects (what the system does) and non-functional aspects (performance, security, usability). It acts as a critical validation gateway that follows Unit and Integration testing before the final acceptance phase.

The incorrect option is (2):
Unit testing is the first and most fundamental level of development testing. It is typically performed by the developers who wrote the code and focuses on testing the smallest testable parts of the application, such as individual methods, functions, or modules, in complete isolation. This early-stage testing is crucial for ensuring that the basic building blocks of the application are correct and free from defects before they are combined.

The incorrect option is (4):
Component testing is a recognized type of testing that falls under the lower-level categories, often aligning closely with Unit Testing. It involves testing individual, well-defined components or modules separately without integrating them with the rest of the system. This practice is integral to the early development phases, ensuring the robustness and correct internal functionality of the software's structural elements.