System testing: Difference between revisions

Revision as of 13:37, 30 September 2019

Revision as of 16:15, 4 October 2019

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}}

{{Multiple issues|

{{refimproveMore citations needed|date=January 2013}}

{{unbalanced|date=October 2018}}

}}

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

'''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}} The actual result is the behavior produced or observed when a component or system is tested.<ref>{{Cite web|url=http://glossar.german-testing-board.info/|title=ISTQB Standard glossary of terms used in Software Testing|last=|first=|date=|website=|archive-url=|archive-date=|dead-url=|access-date=}}</ref>

System testing is performed on the entire system in the context of either [[Functional requirements|functional requirement]] specifications (FRS) or [[Requirements analysis|system requirement]] specification (SRS), or both. 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 or hardware requirements specification(s).{{Citation needed|date=April 2008}}