1, first interface test is skipped front end interface of the service side of the test, the test is a test of the UI of the front-end interface, from the viewpoint of delamination testing perspective, the two should not be substituted relationship to each other.
2, from the perspective of the company to carry out automated consideration, you can focus on the projects carried out automation and interfaces are required UI Automation of time consuming, automated testing personnel costs, the feasibility of the project to carry out automated testing, automated UI automation and interfaces into production the ratio is determined to carry out the final UI automation interfaces and automation of proportion.
3, the coverage and ease of automated test considered, in general, feature points in the system can be tested than the number of front-end interface of the interface to be less, and the frequency of the low frequency change than the front end interface of the interface changes, as interface to automate the study costs are relatively low point, also can directly use the many tools available.
4, but the automated testing is just a way to solve some of the duplication of smoke, regression, acceptance, or to see how deep the specific degree of automation you want, and then think of ways to achieve this objective.
UI and interfaces combined, usually based interfaces, supplemented UI.
the reason:
- Interface implementation of high efficiency, high code coverage can be tested, low maintenance costs, are low-cost, high-yield.
- UI Automation low efficiency, and vulnerable for other reasons (computer Caton, Caton browser, speed, etc.) affect the result in the script fails, it is difficult to improve the coverage, the higher the cost of maintenance, are put into higher and lower income Types of. But its advantage is that you can fully simulate user behavior, closer to real