Shulou(Shulou.com)06/02 Report--

Editor to share with you the example analysis of automated testing in mobile development, I believe most people do not know much about it, so share this article for your reference, I hope you will learn a lot after reading this article. Let's take a look at it!

I. the concept of automated testing

Automated testing is a process of transforming human-driven testing behavior into machine execution.

II. Project characteristics suitable for automated testing

III. Classification of software testing

By project flow: unit testing, integration testing, system testing, regression testing, acceptance testing

By technology: black box testing, white box testing, gray box testing

By function: logic function test, interface test, ease of use test, installation test, compatibility test

By performance: time performance test, space performance test

By Automation: functional Automation, performance Automation

Project flow + automated → layered testing: unit testing (unit testing), service testing (interface testing), UI testing

IV. The present situation of automated testing

1. Unit testing (extreme programming-test-driven development), accounting for 70%

(1) check and verify the minimum testable unit in the software

(2) written by the developer to verify whether the semantics of the test unit is correct.

(3) generally execute automated test scripts during the construction phase

(4) Representative tools: XUnit, etc.

2. Interface testing, accounting for 20%

(1) Test of the interface between the components of the test system

(2) mainly to ensure the correctness and stability of the interface

(3) Representative tools: Jmeter, Postman, etc.

3. UI test, accounting for 10%

(1) verify whether the layout is reasonable, the style is consistent, etc.

(2) ensure that the objects inside the UI function are as expected

(3) Representative tools: selenium, robot framework, etc.

4. Summary

(1) with the help of the test framework of the corresponding language, the unit test can execute the test script at build time, and it is less difficult.

(2) Interface testing can also be automated by defining the input and output of each use case and with the help of interface testing tools, which is not difficult.

(3) UI testing is more related to interface rendering, including whether the location and size of elements are correct, whether the contents of elements are correct, and so on, mainly testing the results of interface rendering.

5. Automated testing of UI on different ends

In order to judge whether the rendering interface meets the expectations, it is necessary to have the ability to manipulate the terminal interface and compare the information of the elements with the expected results through positioning elements.

Note: this only falls within the scope of functional testing, and other means of comparison are needed if multimedia content is included.

The ability to control the interface of the terminal varies with the terminal, which is mainly the difference between the PC end and the mobile terminal.

1. PC side:

Each browser vendor will provide the corresponding driver, they all implement the WebDriver's wire protocol defined by Selenium, through this protocol you can manipulate the browser to do anything!

This driver starts the web service based on this protocol, which is actually listening for http requests on a port and performing different operations according to different requests.

Representative framework:

Take Selinium as an example, the implementation principle is as follows:

2. Mobile:

Similar to the principle of PC, but with the difference between Android and IOS

Android: mainly based on UIAutomator and UIAutomator2, earlier can be traced back to the instrumentation framework.

(1) instrumentation can load the test package and the target test app into the same process to control the app.

Then encapsulated to form a Selendroid architecture

(2) UIAutomator is a UI testing framework based on Java that Google launched when the Android4.1 version was released, which is used in conjunction with Bootstrap.

Its characteristic is that it can operate across processes, and any control property of any app on the screen can be obtained and manipulated.

But the disadvantage is that it can only be written in Java, and the test script must be uploaded to the device to run.

(3) UIAutomator2 fixes the original version of bug and adds many new features.

Equipment and development machines can be separated from the data line and interconnected through WiFi (based on atx-agent)

Integrate openstf/minicap to achieve real-time screen frequency casting and real-time screenshot

Integrate openstf/minitouch to achieve accurate real-time control equipment

Fixed a problem with frequent xiaocong/uiautomator exits

The code has been refactored and streamlined to facilitate maintenance

Implemented a device management platform (also supporting iOS) atxserver2

IOS: mainly based on the introduction of UITesting after UIAutomation,Xcode 7

(1) when operating app through UIAutomation, UIAutomation will send WM_GETOBJECT message to app.

If app processes WM_GETOBJECT messages, implements UIAutomation Provider, and calls the following functions, the app supports UiaReturnRawElementProvider (HWND hwnd, WPARAM wparam, LPARAM lparam, IRawElementProviderSimple * el)

IRawElementProviderSimple is UIAutomation Provider, which contains all kinds of information about the control, such as Name,ClassName, coordinates and so on.

Therefore, if app wants to support automation, it must implement UIAutomation Provider. For more information, see "UIAutomation Client Programmer's Guide".

(2) UITesting is a UI automated testing framework introduced by Apple and introduced in Xcode 7. Its principle makes use of IOS's Accessibility.

Xcode comes with it and does not need to build an environment.

Support OC and Swift with low learning cost

Support for WebView testing

Good stability

VI. Commonly used automated testing framework for mobile terminals

The following figure lists the performance of some of the testing frameworks on some indicators, in addition to these, Robot framework, Ali's macaca framework and so on can also be considered.

Seventh, the concrete realization of mobile terminal automatic test.

A thousand mouth handles are not as good as lai hands!

The following automated test script code implements the screenshot in app based on Appium:

Of course, in addition to writing test scripts, there is a lot of work to be prepared.

For usb to connect to the device, the device needs to open developer mode

Install the debug package of the target test app

Check whether the driver version of chromeDriver matches the device

Other unknown problems may be encountered.

Here is a snippet of an automated test script based on Robot framework

8. Exploration of mobile automated testing 1. Data-driven automated testing → keyword-driven automated testing.

As can be seen from the above specific implementation, to write a corresponding test script for a test case, it requires a large amount of code, and needs to be very familiar with the definition and input and output of each method.

Therefore, to achieve automated testing at the UI level, the cost is very high, and even exceeds the benefits.

Therefore, if you can make it easy to write test scripts, it will greatly improve the status quo.

2. Exploration

Looking carefully at the above specific implementation, we can find that a test script can be composed of multiple test cases, and each test case can be composed of multiple instructions with clear semantics.

So you can consider abstracting it, which is also a specific application of the policy pattern, which mainly includes three aspects:

The separation of the interface element name from the test internal object name.

All the elements on the interface are mapped to a corresponding logical object, and the test is carried out for these logical objects. the change of the interface element will only affect the mapping table, not the test.

The separation of the test description from the specific implementation details separates the test description from the specific implementation details of the test.

The test description only describes what the software test is going to do and what results to expect, regardless of how the test is performed or how the result is verified.

This is done because the implementation details of the test are often closely related to the specific platform and the specific test execution tools.

This separation makes the test description insensitive to the application implementation details and facilitates the migration of tests between tools and platforms.

The separation of scripts from data.

The test data needed during the test execution is extracted from the script, and the test script reads the pre-customized data from the data store at run time, so that the script and data can be maintained independently.

The following is a keyword-driven instruction model mapping table

IX. The Prospect of Mobile UI Automation Test

A complete mobile UI automation process should include both functional and visual parts.

In terms of functionality, although automation can be achieved using some mainstream frameworks, scripting is still costly and complex.

In terms of vision, we need to rely on image recognition, image similarity matching, audio matching and other technical means.

Therefore, at present, the automated testing for mobile UI is still full of difficulties, and there is not a mature solution.

Traditional testing Technology → testing Technology based on AI

Since AI successively defeated Lee Shishi and Ke Jie in the go world, AI technology has gradually affected all aspects of human society.

And automated testing is also slowly developing in the direction of AI, based on deep learning, through iterative training, let the machine make its own decisions, and finally complete the operation.

The representative AI automated testing practices are Aion testing framework of iqiyi team and AI automated testing system of Tencent Games QA team.

I believe that in the near future, with the power of AI, automated testing will become more and more simple!

The above is all the contents of the article "sample Analysis of Automated testing in Mobile Development". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.