System testing

Testing conducted on a complete software system

See also: System integration 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]

## Approaches

[edit]

* 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.[2][3][4]

## See also

[edit]

* Automated testing
* Automatic test equipment
* Mobile-device testing
* Quality control
* Software testing
* Test case
* Test fixture
* Test plan

## Notes

[edit]

1. ^ "ISTQB Standard glossary of terms used in Software Testing".
2. ^ Moradi, Mehrdad; Van Acker, Bert; Vanherpen, Ken; Denil, Joachim (2019). Chamberlain, Roger; Taha, Walid; Törngren, Martin (eds.). "Model-Implemented Hybrid Fault Injection for Simulink (Tool Demonstrations)". Cyber Physical Systems. Model-Based Design. Lecture Notes in Computer Science. 11615. Cham: Springer International Publishing: 71–90. doi:10.1007/978-3-030-23703-5_4. ISBN 978-3-030-23703-5. S2CID 195769468.
3. ^ "Optimizing fault injection in FMI co-simulation through sensitivity partitioning | Proceedings of the 2019 Summer Simulation Conference". dl.acm.org: 1–12. 22 July 2019. Retrieved 2020-06-15.
4. ^ Moradi, Mehrdad, Bentley James Oakes, Mustafa Saraoglu, Andrey Morozov, Klaus Janschek, and Joachim Denil. "Exploring Fault Parameter Space Using Reinforcement Learning-based Fault Injection." (2020).

## References

[edit]

* Black, Rex (2002). Managing the Testing Process (2nd ed.). Wiley Publishing. ISBN 0-471-22398-0.

* v
* t
* e

Software testing

The "box" approach|

* Black-box testing
* All-pairs testing
* Exploratory testing
* Fuzz testing
* Model-based testing
* Scenario testing
* Grey-box testing
* White-box testing
* API testing
* Mutation testing
* Static testing

Testing levels|

* Acceptance testing
* Integration testing
* System testing
* Unit testing

Testing types, techniques,
and tactics|

* A/B testing
* Benchmark
* Compatibility testing
* Concolic testing
* Concurrent testing
* Conformance testing
* Continuous testing
* Destructive testing
* Development testing
* Differential testing
* Dynamic program analysis
* Installation testing
* Negative testing
* Random testing
* Regression testing
* Security testing
* Smoke testing (software)
* Software performance testing
* Stress testing
* Symbolic execution
* Test automation
* Usability testing

See also|

* Graphical user interface testing
* Manual testing
* Orthogonal array testing
* Pair testing
* Soak testing
* Software reliability testing
* Stress testing
* Web testing

*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template