Shulou(Shulou.com)05/31 Report--

What are the eight rules of APP testing? for this question, this article introduces the corresponding analysis and solutions in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible way.

When it comes to software testing, testers must check files, functionality, API, performance and determine whether the software is secure, as well as other things about specific parts of the software. But for mobile testing, testers have to consider mobile-related functions based on the user's mobile usage patterns.

The following is mainly about mobile testing, for the product of mobile phone projects (applications), mainly for system testing. For the system testing of mobile application software APP, we usually carry out the following aspects: functional module testing, compatibility testing, installation and uninstallation testing, software update testing, performance testing, user experience testing, cross event testing, user interface testing and so on.

As a software quality assurance manager, I devote myself to iPhone,Android,WindowsPhone7 's mobile apps and mobile webapps. In the process of daily work and communication with other mobile testing experts, I have a deep understanding of the difficulties of mobile testing. Therefore, this article is summarized based on my work experience, hoping to help you solve some practical problems. With regard to the key points of the APP test, sort it out and post it for everyone to see.

First, take a look at the following picture:

This diagram should clearly show the flow of APP testing. Then what needs to be explained is the part where the test was executed. Because of the xmind, the picture looks too small if there are too many words, so let's talk about the corresponding things for each stage here.

Flow of APP testing

1. UI test

Check whether the UI elements such as UI picture, icon, text, layout and so on are consistent with the effect picture. In general, there is no particularly serious problem with UI, so just give it to the product as a suggestion.

2. Functional test

Check whether the function meets the requirements, involving UI layer, interface, data, server, code logic and so on. Functional defects are generally defined as serious defects that must be fixed.

3. Robustness test

Check the handling mechanism of the product in the event of an exception. At the same time, you need to check whether crash or anr will occur when these exception scenarios or limit situations occur. You need to pay attention to some limit and exception scenarios, as well as the testing of interrupts and weak networks.

4. Adaptation

Check product compatibility, different hardware devices, resolution, operating system, screen size, mobile phone model, etc. Android is not easy to do, there are too many customized systems in China, and the general method is to test mainstream models.

5. Stability test

Monkey is usually used for testing here. I was also dismissive of monkey before, but later, after the guidance of my predecessors, I also found its strength. At present, it also belongs to the stage of learning. The main means is to carry out a large number of clicks, slides and other operations through the pseudo-random event stream, which is mainly used to detect the defects of crash and anr hidden in the product.

6. Performance testing

Client performance: the main monitoring, client runtime device CPU,GPU, traffic, power consumption, response time and other data. Carry on the data analysis, optimize the product for the client, so as to enhance the competitiveness of the product. Further exploration can analyze the performance bottleneck of the client, and even locate the code that affects the performance of the client.

Server performance: main monitoring, Imax O, throughput, concurrency, stress, load and other data. Analyze the test results, find the performance bottleneck and optimize the performance. The main purpose is to check the stability of the server, whether to achieve the desired goals and complete the expected tasks.

7. Regression test

Regression testing is mainly aimed at testing defects repaired by development. Assess the scope of impact of the changes and conduct targeted testing. In fact, we also need to return to the functions, data and so on of the old version.

8. Online test

After the release, the final round of system testing will be carried out in the production environment. I usually do all the things I've done before.

The difference between ios and Android in App testing

1. Android long press the home key to call out the application list and switch applications, and then swipe right to terminate the application.

2. Multi-resolution test, there are more than 20 kinds of Android and less ios.

3. Mobile operating systems have more Android, less ios and cannot be downgraded, so they can only be upgraded one-way; the resource library in the new ios system is not fully compatible with the application in the lower version of the ios system, and the application in the lower version of the ios system calls the new resource library, which will directly lead to Crash.

4. Operation habits: whether the Android and back keys are rewritten, test whether the feedback after clicking the back keys is correct, and whether the application data can run normally after moving from memory to SD card, etc.

5. Push test: Android: click the home button, when the program is running in the background, receive the push, wake up the application after clicking, and whether you can jump correctly at this time; ios, click the home button to close the program and the screen lock screen (red dot display)

6. Installation and uninstall testing: there are many platforms, tools and channels for downloading and installing Android. Ios mainly has appstore,iTunes and testflight downloads.

7. Upgrade testing: necessary conditions that can be upgraded: new and old versions have the same signature; new and old versions have the same package name; there is an identifier to distinguish between new and old versions (such as version number). For Android, if there is a built-in application, check whether the built-in files match after upgrade (such as built-in input method).

In addition: there are a few points to pay attention to for testing:

1. Concurrent (interrupt) testing: alarm pop-up box prompts, startup of another application, video and audio playback, incoming calls, user input, etc., voice, recording, etc. Playback forces other players to be paused.

2. Testing of data sources: input, selection, replication, voice input, installation of different input methods, etc.

3. Push (push) test: when push is performed on / off and standby, the message dies first and the push jump is correct; whether the push display and jump are correct when the application is developed, unopened, started and running in the background; whether the change of the number before and after the push message is correct; whether the display and jump of the collection of multiple push is correct

4. Sharing jump: whether the copy after sharing is correct, whether the jump after sharing is correct, and whether the source of the message displayed is correct.

5. Touch screen test: touch different locations or perform different operations at the same time to check the processing of the client, whether it will crash, etc.

This is the answer to the eight rules for doing a good APP test. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel to learn more about it.

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.