| System Testing |
Article Index for System |
Website Links For System |
Information AboutSystem Testing |
| CATEGORIES ABOUT SYSTEM TESTING | |
| software testing | |
|
Alpha Testing and Beta Testing are sub-categories of System testing. As a rule, System testing takes, as its input, all of the "integrated" software components that have successfully 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 hardware. System testing is more of a limiting type of testing, where it seeks to detect both defects within the "inter-assemblages" and also the system as a whole. TESTING THE WHOLE SYSTEM Generally speaking, System testing is the first time that the entire system can be tested against the Functional Requirement Specification(s) (FRS) and/or the System Requirement Specification (SRS), these are the ''rules'' that describe the functionality that the Vendor (the entity developing the software) and a Customer have agreed upon. System testing tends to be more of an ''investigatory'' testing phase, where the focus is to have almost a destructive attitude and test not only the design, but also the behavior and even the believed expectations of the customer. System testing is intended to test up to and beyond the bounds defined in the software/hardware requirements specification(s). One could view System testing as the final ''destructive'' testing phase before Acceptance Testing . TYPES OF SYSTEM TESTS The following examples are different types of testing, that should be considered during System testing:
Although different testing organizations may prescribe different tests, within System testing, this list serves as a general framework, or foundation to begin with. SEE ALSO
REFERENCES
|
|
|