Jump to content

System testing

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Anon lynx (talk | contribs) at 19:49, 20 October 2018 (→Methods: more of same). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

System testing is testing conducted on a complete integrated system to evaluate the system's compliance with its specified requirements.

As a rule, system testing takes, as its input, all of the integrated components that have passed integration testing and also the software system itself integrated with any applicable hardware system(s). The purpose of integration testing is to detect any inconsistencies between the software units that are integrated together (called assemblages) or between any of the assemblages and the hardware. System testing is a more limited type of testing; it seeks to detect defects both within the "inter-assemblages" and also within the system as a whole.

System testing is performed on the entire system in the context of a Functional Requirement Specification(s) (FRS) and/or a System Requirement Specification (SRS). 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/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.

Software testing

Software testing is an investigation conducted to provide stakeholders with information about the quality of the software product or service under test.[1] 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.

See also

Notes

  1. ^ Kaner, Cem (November 17, 2006). Exploratory Testing (PDF). Quality Assurance Institute Worldwide Annual Software Testing Conference. Orlando, FL. Retrieved November 22, 2014.

References

  • Black, Rex (2002). Managing the Testing Process (2nd ed.). Wiley Publishing. ISBN 0-471-22398-0.
Retrieved from "https://en.wikipedia.org/w/index.php?title=System_testing&oldid=864966050"