Understanding of several test types in project development

Understanding of several test types in project development-Linux general technology-Linux programming and kernel information. The following is a detailed description. Many people think that testing is generally performed after the system is completed, but today, we often hear senior developers persuade new people: how can we understand the phrase "testing is the first step of development? If you understand from the buck quality management method invented by the Japanese, it means that testing should be carried out when each link is handed over to the next level. Some tests do not have much impact on subsequent operations, such as poor films, unreasonable menus, and ugly la S. Others directly make the next level unable to start work, such as unclear use cases; self-contradictory use cases, internal component errors, unreasonable framework, and so on.

Although level-1 checks can increase the quality to at least one level, it is still in the final stage of development. Therefore, it seems that my level is still not home, "testing is the first step of development" is hard to understand, the only thing that can be understood is standardization first, document first, document standardization should always be prior to coding, which is also the main content of QA; this can be explained in general. In this way, the test and the specification overlap. From a strict point of view, the test is a test. If the specification is classified into the specification, we should start to understand the test after the module (project; therefore, all content about programming, documentation, and design specifications is not included in the test scope. In other words, we focus on QC rather than standardized QA, although that is also very important.

Unit test: A Unit test is a test of module components or methods. In my own operations, it is generally a test within the scope of the developer's work; in the case of a standard component interface, it is generally necessary to do a test tool to simulate the call environment, write a test instance, check whether the actual work of the breakpoint monitoring module is normal. The quality of a single functional module developed in this way is very high. However, if there is no unified module specification, the development and testing workload is close to one-to-one. However, if the module is developed according to the unified standard, the same test suite can be used on various modules, this saves test time. I think this is a test within the scope of work of the Development Department and has nothing to do with the QA/QC department. In fact, the use cases at this level are not what QC can do and understand.

White-box testing: design a test instance for a logical process with an understanding of the internal process to identify the limit edge and internal logical errors. The proportion of white box tests in unit tests is very high (the reason is not difficult to understand. Who else understands the module construction process better than the author himself ?).

Black box testing: This is the main work of the QC department. The black box test mainly involves compiling test instances. However, in practice, members with the least technical knowledge are allocated for testing. The highest technical level is VSS, so do not expect to compile any test instances. The so-called black box test is usually aimed at the menu button. Click it. Oh, something is coming out, right, and a check -- actually, at this time, the instance is one by one and then there is no output, and only the interface is limited, the inner part and the edge are probably not expected. However, as far as the author knows, black box testing is the most important way to evaluate software among foreign software companies with more than four CMM. through suitable testing examples, apart from the most common usability testing, it also includes stress testing and Monkey test ).

Stress Testing: Evaluate the maximum amount of pressure that a system can withstand, and respond to overload situations. At the same time, under extreme conditions, some bugs that do not usually show up. Therefore, the author believes that this test should not be conducted by the QC department alone, but by the Development Department and the QC department. Even if the system fails to respond to the limit test, it will not be able to become a machine and resume normal operation within a period of time after the load returns to normal. At this time, one of the reasons for the negative comments on windows was: Once the website exceeded-concurrent, windows not only went on strike, but also died. The system had to be restarted (of course, any windows hard reboot could lead to a crash, in most cases, it is also a very valuable advantage). However, when linux exceeds the load, the downloading curve is generally not too obvious-but this is not absolute, the authors found that, when linux enters the memory jitter in the extreme state, the dead phase is not much inferior to windows; therefore, the memory consumption is not an important factor for linux's reliability to surpass windows.

Regression testing. After you modify one of the modules, check the other modules. The author believes that this test is the product of the concept of procedural programs. In modular software, the degree of coupling is low, and it is subject to the unified transfer protocol. Is it true that it is a self-owned thing, and other people (modules) there is no semi-coherence.

Overall Test: link different modules to see how the cooperation works. This is actually a test of the interface protocol. The author believes that it can be part of the design of interface interaction, and there is no need to put it out as one of the processes. In the same way, there is also a system test. What is the final state of the entire system running. It seems big, but if the previous steps are done well, it would be strange if there is a problem here!

Alpha testing: Allows internal members to participate in testing;

Beta testing: This is a testing that keeps the bad guys all over the world confused.

After that, should it be okay ?? Software companies in Europe, the United States, and Japan are probably allowed. But in China, I don't know. In many cases, business demand personnel will say, "This is not the case !" He went there early! Or "What other functions are added ?", He probably went to bed early in the morning. The first thing the Big Guy did was to waste the two sentences. All the things had to come back from a link in the middle. This was a nightmare. At this time, instead of following their old brother's nonsense, it is better to find out the contract and issue it carefully.