Basic method for system testing
(This article is reproduced from Software Engineering Expert Network
Www.21cmm.com)
Computer software is based on an important part of a computer system. After the software development is completed, it should be integrated with other ingredients in the system, and a series of system integration and confirmation tests are required. The detailed discussion of these tests has exceeded software engineering, and these tests cannot be completed only by software developers. Prior to system testing, software engineers should complete the following work: (1) Design error handling pathway for the input information of the test software system; (2) Design test case, analog error data, and software interface may occur, record the test results, System test provides experience and help; (3) Participate in the planning and design of system testing to ensure the rationality of software testing. System testing should be composed of several different tests, the purpose is to fully run the system, verify that the system can work and complete the task given. Several types of system tests are simply discussed below. 1. Recovery Test Recovery Test Mainly Check the system's fault tolerance. When the system is wrong, the error can be corrected in the specified time interval and restart the system. Recovery tests first use various ways to force the system failure, and then verify that the system can recover as soon as possible. For automatic recovery, the correctness of the reinitialization, checkpointing mechanism, data recovery, and restarts, etc.; Determine whether it is within an acceptable range. 2. Safety test safety test inspection system to prevent the ability of illegal intrusion. During the safety test, the test personnel pretend to be illegally invaded, and various ways to try to break through the defense line. For example, 1 want to intercept or decompose the password; 2 specialize in the protection mechanism of the software destruction system; 3 deliberately lead to the failure of the system, attempted to recover illegally enter; 4 Attempt to browse non-confidential data, derive the required information, and so on. In theory, as long as there is enough time and resources, there is no system that cannot be entered. Therefore, the system security design is the value of illegal intrusion exceeding the value of the protected information. At this time, illegal invasants have been unprofitable. 3, intensity test intensity test inspection procedure against abnormal conditions. Strength testing always force the system to run under an abnormal resource configuration. For example, 1 When the normal frequency of the interrupt is one to two times per second, run the test case for 10 interrupts per second; 2 Quantitatively grow the data input rate, check the reflection capabilities of the input sub-function; 3 Run require maximum storage space ( Or other resource) test case; 4 Run may result in test cases of the virtual operating system crash or disk data violently jitter, and so on. 4. Performance Test For those real-time and embedded systems, the software part does not meet the performance requirements even if the functional requirements are met, although from the unit test, each test step contains performance test, but only when the system is really integrated, In the real environment, you can fully and reliably test the performance system performance test to complete this task. Performance tests are sometimes combined with intensity testing and often require supporting support for other hardware and software.
