Also said that automated testing

I went through the project in the order of the following automated test exploration: 1, C + + function automation testing, 2, GUI program Interface Automation test, 3, Openresty interface Automation test, 4, web interface Automation test, 5, PHP interface Automation test.
C + + function automation Test equals white box test, by the important functions of export, from the outside reference these functions for parametric testing and results validation, the test logic goes to each function inside, such as testing each loop each judgment statement, and its shortcomings are more obvious, because the basic every line of code to handwriting, Modifying the test case is also a bit of a hassle, so you can only focus on core functions, such as the driver and driver of the Ring 3 interface layer of the function test, these functions at the beginning of the product is rarely changed, can not cover the entire product. This was not used in the modern test framework, can be understood as a written test framework, pure C + + implementation.
GUI Program Interface Automation testing, I went through some of the project is to use C # interface Automation, because the object is running in Windows, some use Python, the core is also called C + + function to do interface Click Test, it is the benefit of simulating the user's actual operation of the software when the action, The effect looks cool after running. One of the disadvantages is that the impact of the environment is greater, the machine speed to test results, often to debug a long time, the same code for a machine does not necessarily run through; the disadvantage of the second is the product interface, if the interface changes, the need to adjust the test code is also many.
Openresty interface Automation test, using Python unitest to test each location, simulation of various parameters after verifying the results of the interface execution, it seems to be more smooth.
Web interface Automation testing, the use of selenium-based, specifically I did not participate, but its shortcomings are more obvious, the control depends on a lot, if the interface changes, there are many places to modify.
PHP interface Automated testing, using Python's unitest to test each PHP interface, it seems to be quite smooth.
Automated testing can certainly save a lot of human resources, but its actual implementation of the domestic Internet company is not very common, a few days ago in a communication site to see a colleague asked the actual work of the proportion of automated testing, we answer mostly accounted for about 30%, From the actual experience, the reason that the automatic test can't be carried out on a large scale is that the project iteration is fast and the interface demand becomes faster.
I think that in the case of limited resources to do automated testing to have a choice, it is recommended to focus on the interface Automation testing and function automation testing, interface Automation testing can be stabilized after the project for those who are expected to rarely change the implementation of the object, which also involves an automated test intervention project timing issues, For interface automation testing is not required at the beginning of the interface definition, because the development of the joint or after the implementation of the interface may be a large adjustment, it is recommended that the development and validation of the joint pass after the implementation of the interface test code to write. Interface Automation testing time is much more, after the control can be determined after a number of control library definition, and so on when the product is released, the test case of the specified object can be written, mainly for the post-product stability testing and regression testing. From what I've seen, the project practice has shown that the costs of getting involved too early tend to be greater than the benefits, and if you finally find out that most of the use cases are not available then it will hit the testers more actively.

Also said that automated testing