System testing
testing conducted on a complete integrated system to evaluate the system's compliance with its specified requirements
System testing, a.k.a. end-to-end (E2E) testing, is testing conducted on a complete software system.
System testing describes testing at the system level to contrast to testing at the system integration, integration or unit level.
System testing often serves the purpose of evaluating the system's compliance with its specified requirements – 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.
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.
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.
Nondestructive testing: analysis techniques to evaluate the properties of a material, component or system without causing damage.
Fault injection: A testing technique which stress the system in an unusual way to examine the system behavior.
“System testing” enters the record as testing conducted on a complete integrated system to evaluate the system's compliance with its specified requirements. Crown Archives preserves that source wording while asking what System, testing and conducted can confirm, complicate or overturn.
Why this record matters
“System testing” is worth following because a concise public description often conceals a longer documentary argument. Here, System, testing and conducted provides the most credible route into that argument.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Mar 24, 2026. The linked authority identifier is Q1199682. None of the 0 selected statements returned an explicit reference.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “System testing”, its source revision and the description used here.
- Expand the search: follow System testing primary sources, System testing archive and System research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “System testing”?
- Which institution is responsible for the underlying evidence?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “System testing” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.