System testing

This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages) This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "System testing" – news · newspapers · books · scholar · JSTOR (January 2013) (Learn how and when to remove this message) This article may be unbalanced toward certain viewpoints. Please improve the article by adding information on neglected viewpoints, or discuss the issue on the talk page. (October 2018) (Learn how and when to remove this message)

System testing, a.k.a. end-to-end (E2E) testing, is testing conducted on a complete software system.

System testing describes testing as at the system level to contrast to testing at the integration or unit level.

System testing often serves the purpose of evaluating the system's compliance with its specified requirements ^{[citation needed]} – often from a functional requirement specification (FRS), a system requirement specification (SRS), another type of specification or multiple.

System testing can detect defects in the system as a whole.^{[citation needed] [1]}

System testing can verify the design, the behavior and even the believed expectations of the customer. It is also intended to test up to and beyond the bounds of specified software and hardware requirements.^{[citation needed]}