System testing

Short description: Testing conducted on a complete integrated software system

System testing is testing conducted on a complete integrated system to evaluate the system's compliance with its specified requirements.^{[citation needed]}

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]} The actual result is the behavior produced or observed when a component or system is tested.^[1]

System testing is performed on the entire system in the context of either functional requirement specifications (FRS) or 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]}

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

Subject-specific test methods

Software testing

Software testing is an investigation conducted to provide stakeholders with information about the quality of the software product or service under test.^[5] Software testing can also provide an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Software testing involves the execution of a software component or system component to evaluate one or more properties of interest. In general, these properties indicate the extent to which the component or system under test meets the requirements that guided its design and development, responds correctly to all kinds of inputs, performs its functions within an acceptable time, is sufficiently usable, can be installed and run in its intended environments, and achieves the general result its stakeholders desire. As the number of possible tests for even simple software components is practically infinite, all software testing uses some strategy to select tests that are feasible for the available time and resources.

Mobile-device testing

Mobile-device testing assures the quality of mobile devices, like mobile phones, PDAs, etc. The testing will be conducted on both hardware and software. And from the view of different procedures, the testing comprises R&D testing, factory testing and certificate testing. Mobile-device testing involves a set of activities from monitoring and trouble shooting mobile application, content and services on real handsets. Testing includes verification and validation of hardware devices and software applications.

Notes

↑ "ISTQB Standard glossary of terms used in Software Testing". https://glossary.istqb.org/en/search/.
↑ 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)" (in en). Cyber Physical Systems. Model-Based Design. Lecture Notes in Computer Science (Cham: Springer International Publishing) 11615: 71–90. doi:10.1007/978-3-030-23703-5_4. ISBN 978-3-030-23703-5. https://figshare.com/articles/preprint/Model-Implemented_Hybrid_Fault_Injection_for_Simulink_Tool_Demonstrations_/12479930.
↑ (in EN) Optimizing fault injection in FMI co-simulation through sensitivity partitioning | Proceedings of the 2019 Summer Simulation Conference. 22 July 2019. pp. 1–12. https://dl.acm.org/doi/abs/10.5555/3374138.3374170. Retrieved 2020-06-15.
↑ 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).
↑ Kaner, Cem (November 17, 2006). "Exploratory Testing". Quality Assurance Institute Worldwide Annual Software Testing Conference. Orlando, FL. http://www.kaner.com/pdfs/ETatQAI.pdf. Retrieved November 22, 2014.

References

Black, Rex (2002). Managing the Testing Process (2nd ed.). Wiley Publishing. ISBN 0-471-22398-0. https://archive.org/details/managingtestingp00rexb.

de:Softwaretest#Systemtest

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/System testing. Read more

[1] "ISTQB Standard glossary of terms used in Software Testing". https://glossary.istqb.org/en/search/.

[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)" (in en). Cyber Physical Systems. Model-Based Design. Lecture Notes in Computer Science (Cham: Springer International Publishing) 11615: 71–90. doi:10.1007/978-3-030-23703-5_4. ISBN 978-3-030-23703-5. https://figshare.com/articles/preprint/Model-Implemented_Hybrid_Fault_Injection_for_Simulink_Tool_Demonstrations_/12479930.

[3] (in EN) Optimizing fault injection in FMI co-simulation through sensitivity partitioning | Proceedings of the 2019 Summer Simulation Conference. 22 July 2019. pp. 1–12. https://dl.acm.org/doi/abs/10.5555/3374138.3374170. 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).

[Kaner_1-5] Kaner, Cem (November 17, 2006). "Exploratory Testing". Quality Assurance Institute Worldwide Annual Software Testing Conference. Orlando, FL. http://www.kaner.com/pdfs/ETatQAI.pdf. Retrieved November 22, 2014.

[1]

[2]

[3]

[4]

[5]