Understanding and practice of several test types in project development

Project
Original:

Tests are typically done after the system is completed, but today, senior developers are often heard to persuade new people that "testing is the first step in development" how to understand it? If the Japanese invented Buck Quality management approach to understand, probably means that each link to the next level should be tested. Some tests do not have much impact on the following operations, such as the picture is not beautiful, the menu is not reasonable, the layout is difficult to see and so on, while others, but directly to the next level can not start work, such as use case is not clear, use-case contradictions; Of course, the level of control, you can improve the quality to at least a grade above; but for every link, it's still in the final stages of development. Therefore, it seems that my level is still not home, "testing is the first step in development" difficult to understand, the only thing that can be understood is that the canonical, document first, the standardization of documents should always be in the code before, this is also the main content of QA; Presumably it's still a lot of explanation In this way, the test and the specification of two things overlap, from a strict point of view, testing is testing, specification into the specification, or from the module (project) after the test began to understand it; so all the content about programming and documentation, design specifications, I'm not included in the test discussion scope. Or, we focus on QC rather than normative QA, although that's also important.

Unit test: A test for a module component or method. In my operation, the developer is generally the scope of the test, in the case of component interface specifications, generally need to do a test tool to simulate the call environment, write test instances, through the breakpoint situation monitoring the actual work of the module is normal. The quality of a single functional module developed in this way is very high. But without a unified modular specification, the workload for development and testing is close to 1:1, but if the modules are developed on a uniform basis, the same suite of tests can be used on each module, thus saving the test time. I think this is within the scope of the development Department of the Test, and the QA/QC department has no big relationship, in fact, the use cases at this level is not QC can do and understand.

White Box testing: Design test instances for logical processes in the context of understanding internal processes, with the aim of identifying limits and intrinsic logic errors. The proportion of white box testing in unit tests is very high, (why is it not difficult to understand, who has more understanding of the structure of the module than the author itself?) ）。

Black-Box test: This is the main work of QC department. Black-Box testing is mainly about writing test cases. In practice, however, the least skilled members are assigned to the test, the highest level of technology is the use of VSS, so do not expect to compile what test examples. The so-called black-box test, often to the menu button, this press, oh, something out, right, tick-in fact, then the example is to press down and see if there is no output, and only limited to the interface, the inner part and edge of the situation is probably not expected. But as far as the authors know, in foreign software companies with more than four CMM, black-box testing is the most important way to evaluate software, including stress tests and oddball tests (Monkey test), in addition to the most common usability tests, through appropriate test cases.

Stress testing: Evaluating the amount of pressure a system can withstand and the response to overload, and at the extreme, some bugs that don't usually appear. Therefore, the test authors think that should not be carried out by the QC department alone, but should be jointly conducted by the development department and the QC Department. Ideally, the system will not be able to respond to the test under extreme conditions, and can resume normal operation for some time after the load has returned to normal. At this time one of the reasons for the Windows bad rating: Like Web site once more than 100-200 Concurrent,windows not only strike also died, have to restart the system (of course, Windows arbitrary hard restart can kill fish, most of the case, is also a valuable advantage), and Linux in the general case after the load drop curve is not too obvious-but this is not absolute, the author found that once Linux in the extreme state into the memory jitter, die dead and Windows is not much difference; Linux reliability can outweigh the important elements of Windows.

Regression test, after modifying one of the modules to see what is wrong with other modules. The author believes that this test is a process of the concept of the product, the modular software in a low degree of coupling, and obedience to a unified mobility protocol, is not modified really from the home, and others (modules) have no slightest relevance.

Overall test: Connect the different modules and see how the joint works. This is actually a test of the interface protocol. The author believes that it is possible to work as part of the design of an interactive part of the interface, and that there is no need to pose as one process. The same is also the system test, anyway, finally the whole system to run the situation. Looks big, but if the front has done well, if there is a problem, it is called Strange!

Alpha test: Allow internal members to misbehave test;

Beta test: A test that makes all the world's villains misbehave.

After this pass, probably should be OK?? In Europe US Japan's normative software company is probably OK. But in China it is not necessarily, many times the business needs of people will jump out and say: "Not like this!" "Early in the morning he did not know where to go!" Or "Add another function?" "He probably went to bed early." Folks in front of things to do, the two words on the full waste, all things have to from the middle of a link again, this is called nightmare. At this time, rather than follow their old brother to run nonsense, rather than find a contract to go down carefully.