The difference between mobile app, interface, and web automated testing

Let’s talk about WEB UI automation testing first:

when many people talk about automated testing, they basically refer to WEB UI automation testing, but this is actually wrong. Automated testing includes a lot of development technologies, not just on the interface. of automated tests. WEB UI automation testing is just one of them, but it does have the most tools, such as WINRUNNER\QTP(UFT)\TESTCOMPLETE\SILKTEST\ROBOT\SELENIUM\RF\WAITER and so on. For testers who have no development foundation, they can consider QTP, an automated tool, which can be mastered quickly, but it is necessary to master development technology to learn it well. But in general, choose the tools and development languages ​​that suit your company's needs according to your own needs.

Next, I will talk about the advantages and disadvantages of WEB UI automation testing:

Disadvantages: low development efficiency, high maintenance cost, slow execution speed, etc.   
Advantages: strong user operation authenticity.

Interface automation testing:

Interface automation testing appeared later, but now most Internet companies like to use it as a test work aid. The reason is very simple, it can make up for the shortcomings of UI automation, but at the same time it also has a biggest problem: the authenticity of user operations is not strong. In fact, I personally feel that interface automation testing and UI automation testing can produce complementary tests. Because when we do interface testing, we mostly test HTTP\SOCKET and so on according to the developed technology (interface testing basically does not need any tools, if necessary, it is recommended to use SOAPUI), rather than real testing. The system is operated to verify whether there is a problem with the system.

APP automated testing:

The automated testing of APP should also be divided into UI and interface automated testing. The interface testing is the same as the above, and it is not a matter of technical level. Then I still pay attention to the UI automation testing of APP. There are many automated testing tools for APP, but they are not mature. I chose APPIUM, mainly considering that it can perform cross-platform testing, but the biggest problem is still unstable. Therefore, it does not dare to arrange its automated test cases in a large area. APP just said that it is mainly divided into NATIVE and WEBVIEW. NATIVE objects are easy to obtain. For example, android can directly use uiautomatorviewer to obtain them. WEBVIEW is more troublesome. If you can't get it directly, you can either let the development provide it to you, or you can directly download the code and find it yourself, and you can get it through a method of google....

I talked about these three technologies. Some content, in fact, I want to say that no matter what type of automated testing, our testing process needs to be closely integrated with development, but testing is better than the testing idea of ​​development. In addition, these three technologies should be mixed and tested in practical applications:

UI (WEB) automated testing is the main process test, interface automated testing is comprehensive testing: the automated testing of the interface is first arranged for testing and Regression testing, especially in agile testing, should be dominated by interface automation testing. Post-layout UI automation tests for regression testing of live processes.

The combination of UI (WEB) automated testing and APP automated testing : requires the coordination of an automated testing framework, which can perform automated testing of long-process scenarios from UI automated testing to the APP interface layer, and can also perform automated testing of long-process scenarios from UI automated testing to the APPUI layer. test.

The combination of interface automation testing and APP automation testing: In fact, the same principle as the long-term exchange of UI and APP automation testing requires the support of an automated testing framework. Execute the interface test case first, and then execute the APP UI and interface test case execution.