Warmly celebrate the first software test ended, from no concept to complete the test, plus a walk-stop, two months. The summary meeting that day lost the adult, did not prepare to go up on the nonsense. Haha, but on the stage feel very good ah.
In fact, there is no summary, that is, a summary, because the cloud platform to do a lot of problems in the process of testing personnel, such as limited levels of problems, resulting in testing and did not follow the plan of the person in charge. This is a little pity, otherwise, the final report must be very beautiful ... Nothing,,, the plan to catch up with the changes, this time the mistake is the next step to progress the stepping stone ...
This test is mainly black box test, not white box test.
Black box testing As the name implies is the software as a black box, not the internal structure of the test, the tester does not need to understand the implementation details, according to the test case, input instructions, see the output and the results of the prediction is consistent. It is important that it from the user's point of view, the user experience can also be proposed to modify the views. This comparison pays attention to the software to the result, does not pay attention to the process. Black-Box testing does not have clear and concise specifications, and test cases are difficult to design.
White-Box testing compared to the black box test manpower and material investment, forcing testers to understand the system implementation. Through dynamic and static analysis, the problem of the system is detected more thoroughly. It is also possible to find hidden errors.
Each of the two approaches has its own advantages and disadvantages. The combination of the two is a multiplier.
During the testing process, there is an understanding of the life cycle.
Development software has a life cycle, from understanding requirements, design, development, testing, operation and maintenance is a simple development software lifecycle.
The test also has a life cycle:
(Image from Network)
Even a bug has a life cycle:
, it might be possible to describe the bug from being discovered, to resolving to shutting down, and reopening if the problem is still not resolved when the regression is tested.
Finally, we get a beautiful picture.
This process requires a lot of experience and knowledge of testing, as well as a sense of global control and good communication with the development department. Let us test department can find more problems and find hidden defects, so that the software to reach customer satisfaction at an early stage, can withstand the pressure of the software.
in this process, we also want to thank our thin sister who led us, as well as the hard work of the small partners. (from the last picture can be seen, hehe) at the same time I wish you a prosperous year of the goat, sheep and sheep proud, the best luck ...
Rigrand the song--Software testing