System testing: Difference between revisions

Revision as of 20:46, 20 December 2018

Revision as of 20:49, 20 December 2018

Line 1:

{{refimprove|date=January 2013}}

{{unbalanced|date=October 2018}}<!-- the emphasis of the prose in the body is on software -->

{{see also|System integration testing}}

'''System testing''' is testing conducted on a complete integrated system to evaluate the system's compliance with its specified [[requirements]].{{Citation needed|date=April 2008}}

System testing takes, as its input, all of the integrated components that have passed [[integration testing]]. The purpose of integration testing is to detect any inconsistencies between the units that are integrated together (called ''assemblages''). System testing seeks to detect defects both within the "inter-assemblages" and also within the system as a whole.{{Citation needed|date=April 2008}}

System testing is performed on the entire system in the context of a [[Functional requirements|Functional Requirement]] Specification(s) (FRS) and/or a [[Requirements analysis|System Requirement]] Specification (SRS). System testing tests not only the design, but also the behaviour and even the believed expectations of the customer. It is also intended to test up to and beyond the bounds defined in the software/hardware requirements specification(s).{{Citation needed|date=April 2008}}

==Approaches==

* [[Destructive testing]]: tests are carried out to the specimen's failure, in order to understand a specimen's performance or material behaviour under different loads.