Which description best defines a system test?

Which description best defines a system test?

• A. Tests only a single unit in isolation.
• B. Validates the complete system end-to-end.
• C. Checks only integration between components.
• D. Verifies cosmetic aspects of the interface.

Answer: (B)

System testing focuses on evaluating the entire application as a cohesive, release-ready system, validating that all parts work together to deliver end-to-end functionality. It runs real-world workflows from start to finish, across the full stack and external interfaces, in an environment that resembles production and checks both functional and non-functional requirements. This goes beyond testing a single unit in isolation, which only proves that one piece works by itself; or testing just the interfaces between components, which covers integration points but not the whole user journey; or checking cosmetic aspects, which looks at appearance rather than behavior. So end-to-end validation of the whole system is what system testing is about.

System testing focuses on evaluating the entire application as a cohesive, release-ready system, validating that all parts work together to deliver end-to-end functionality. It runs real-world workflows from start to finish, across the full stack and external interfaces, in an environment that resembles production and checks both functional and non-functional requirements. This goes beyond testing a single unit in isolation, which only proves that one piece works by itself; or testing just the interfaces between components, which covers integration points but not the whole user journey; or checking cosmetic aspects, which looks at appearance rather than behavior. So end-to-end validation of the whole system is what system testing is about.