Summary of mobile application testing technology


Summary of mobile application testing technology

After graduation, I have been engaged in mobile terminal application testing. With more than ten years’ experience, I feel a little sad. This time, I write down my mobile application test experience in recent years and share it with you.

In fact, testing is relatively simple, more complex than nothing. Basically, it is to develop the test process according to the requirements and implement it step by step. Of course, it also contains some necessary testing tools. Whether it is mobile game testing or app testing, whose basic idea remains unchanged, even if it is automated testing.

For example, relatively speaking, many small companies do not have a mature system in testing, there are no specific requirements for testing, and the time is relatively tight. So how to design use cases for projects when the process is not rigorous? In my opinion, when the project is completed, I don’t want to start testing immediately. Instead, I should familiarize myself with the whole process of the project, go through the general framework, record the places you don’t understand, ask for development, master the process, write the test plan and test scheme, write the use case script according to the requirements, list each function module, and roughly function points The method to test is marked, and then the test is executed according to the test requirements.

At present, the mainstream testing methods of mobile terminal include:
Compatibility test, function test, regression test, interruption test, weak network test and stress test;

Compatibility test: test the mainstream device installation applications in the market to ensure that the applications can install and uninstall the basic functions and run correctly, and even test UI and program exceptions;

Function test: test the specific function points one by one to ensure that each point can realize the corresponding function correctly;

Regression testing: after the iterative development of the version, all the new and old functions need to be traversed to ensure the normal operation of all functions and UI

Interrupt test: for the running application, if you enter the SMS, phone and other software response, it will not affect the tested application, and will ensure that the application can run correctly;

Stress testing: the application with large number of users and high interaction needs to perform stress test on the interface to ensure that the application will not run normally under the condition of large number of users.

Most of the above can achieve automated testing. For example, automated compatibility testing can fully meet the requirements of mobile game testing and app testing. However, it is difficult to implement app function testing. The relatively simple one is automated regression testing.

Next, there are many factors that affect the performance of the app, which is also the reason for testing. The longest response time that users can tolerate is 5 seconds. If the response time exceeds 5 seconds, 50% of mobile app users will give up, and a third of disappointed users will turn to competitors

According to the statistics of testbird test platform before, connection timeout, flashback, stuck, crash, black-and-white screen, network hijacking, poor interactivity, CPU utilization, memory leakage and bad interface are the main reasons for the performance impact of mobile applications.

Therefore, improving product performance in this case is more important than the development of new features. To a large extent, product performance determines user experience, and user experience is the decisive factor to ensure the retention.