About software Testing (1): The basic method of system testing

For software programmers, the good Ruan test method can avoid a lot of duplication and software defects, and can be found and corrected in time. It's just that I've been on the software testing course, so let's start with the basic method of testing the system for software testing.

Roughly divided into the following four methods.

1. Recovery test

Recovery testing primarily checks the system for fault tolerance. Can you fix the error within a specified time interval and restart the system when the system is faulted. Recovery testing the first thing to do is to force the system to fail, and then verify that the system recovers as quickly as possible. The correctness of mechanisms such as re-initialization (reinitialization), Checkpoint (checkpointing mechanisms), data recovery, and restart (restart) are required for automatic recovery For human-assisted recovery systems, the average repair time needs to be estimated to determine whether it is within acceptable range.

2. Safety Test

The safety test checks the system's ability to prevent intrusion. During the security test, the testers disguised as illegal intruders and tried to break through the line of defense by various means. For example, ① tries to intercept or decipher the password, ② specially custom-made software to destroy the system protection mechanism, ③ deliberately cause system failure, attempt to take advantage of the recovery of the machine illegally enter, ④ try to browse non-confidential data, deduce the required information, and so on. Theoretically, as long as there is enough time and resources, there is no system to enter. Therefore, the criterion of system security design is to make the cost of illegal intrusion exceed the value of protected information. At this time the illegal intruders are unprofitable.

3. Strength test

The strength test examines the ability of the program to withstand abnormal conditions. Strength testing always forces the system to run under an abnormal resource configuration. For example, ① a test case that runs 10 interrupts per second when the normal frequency of interrupts is one to two per second, and ② quantitatively increases the data input rate to check the reflection capability of the input sub function; ③ Run test cases that require maximum storage space (or other resources) ④ run a test case that could cause a virtual-memory operating system crash or severe disk data jitter, and so on.

4. Performance test

For those real-time and embedded systems, the software component may not meet the performance requirements even if it satisfies the functional requirements, although each test step includes performance testing from the unit test, but only when the system is truly integrated, the performance test of the performance system can be fully and reliably tested in real-world environments in order to accomplish this task. Performance testing, sometimes combined with strength testing, often requires support from other hardware and software.

Many people misunderstand that software testing is the lowest technical content of the software engineering work, in fact, if you want to really understand these, and can be used to help companies or companies, there is much to learn.

About software Testing (1): The basic method of system testing