Menu
Home Explore People Places Arts History Plants & Animals Science Life & Culture Technology
On this page
Robustness testing
Quality assurance testing to determine the robustness of software

Robustness testing is any quality assurance methodology focused on testing the robustness of software. Robustness testing has also been used to describe the process of verifying the robustness (i.e. correctness) of test cases in a test process. ANSI and IEEE have defined robustness as the degree to which a system or component can function correctly in the presence of invalid inputs or stressful environmental conditions.

The term "robustness testing" was first used by the Ballista project at Carnegie Mellon University. They performed testing of operating systems for dependability based on the data types of POSIX API, producing complete system crashes in some systems. The term was also used by OUSPG and VTT researchers taking part in the PROTOS project in the context of software security testing. Eventually the term fuzzing (which security people use for mostly non-intelligent and random robustness testing) extended to also cover model-based robustness testing.

We don't have any images related to Robustness testing yet.
We don't have any YouTube videos related to Robustness testing yet.
We don't have any PDF documents related to Robustness testing yet.
We don't have any Books related to Robustness testing yet.
We don't have any archived web articles related to Robustness testing yet.

Methods

Fault injection

Fault injection is a testing method that can be used for checking the robustness of systems. During the process, testing engineers inject faults into systems and observe the system's resiliency.4 Test engineers can develop efficient methods which aid fault injection to find critical faults in the system.56

See also

References

  1. "Standard Glossary of Software Engineering Terminology (ANSI)". The Institute of Electrical and Electronics Engineers Inc. 1991.

  2. Kropp, Koopman, Siewiorek. 1998. Automated Robustness Testing of Off-the_Shelf Software Components. Proceedings of FTCS'98. http://www.ece.cmu.edu/~koopman/ballista/ftcs98/ftcs98.pdf http://www.ece.cmu.edu/~koopman/ballista/ftcs98/ftcs98.pdf

  3. Kaksonen, Rauli. 2001. A Functional Method for Assessing Protocol Implementation Security (Licentiate thesis). Espoo. Technical Research Centre of Finland, VTT Publications 448. 128 p. + app. 15 p. ISBN 951-38-5873-1 (soft back ed.) ISBN 951-38-5874-X (on-line ed.). https://www.ee.oulu.fi/research/ouspg/PROTOS_VTT2001-functional /wiki/ISBN_(identifier)

  4. Moradi, Mehrdad; Van Acker, Bert; Vanherpen, Ken; Denil, Joachim (2019). "Model-Implemented Hybrid Fault Injection for Simulink (Tool Demonstrations)". In Chamberlain, Roger; Taha, Walid; Törngren, Martin (eds.). Cyber Physical Systems. Model-Based Design. Lecture Notes in Computer Science. Vol. 11615. Cham: Springer International Publishing. pp. 71–90. doi:10.1007/978-3-030-23703-5_4. ISBN 978-3-030-23703-5. S2CID 195769468. 978-3-030-23703-5

  5. "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. https://dl.acm.org/doi/abs/10.5555/3374138.3374170

  6. 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).