The difference between Android and IOS testing in App testing

What are the differences between ios and Android in app testing?

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

2. For multi-resolution testing, there are more than 20 kinds of Android terminals, but less ios;

3. Mobile operating systems, more Android, and more ios There are few and cannot be downgraded, only one-way upgrade; 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 flash Crash;

4. Operating habits: Android, whether the Back key is rewritten, test whether the feedback after clicking the Back key is correct; 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 push at this time, click to wake up the application, whether it 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 uninstallation test: There are many platforms, tools and channels for Android to download and install, ios mainly include app store, iTunes and testflight download;

7. Upgrade test: the necessary conditions for being upgraded: the old and new versions have the same signature; the old and new versions have the same signature; The version has the same package name; there is an identifier to distinguish the old and new version (such as version number), for Android, if there is a built-in application, you need to check whether the built-in file matches after the upgrade (such as the built-in input method)

. A few points:

1. Concurrency (interruption) test: the alarm pop-up box prompts, another application starts, video and audio playback, incoming calls, user input, etc., when the voice, recording, etc. are played, other players are forced to pause;

2. Data source test: input, select, copy, voice input, install different input methods, etc.;

3. Push (push) test: When the push is executed in the power-on and standby state, the message will die first and the correctness of the push jump; the push display is displayed when the application is under development, not opened, and the application is started and running in the background. Whether the number and jump are correct; whether the change of numbers before and after reading the push message is correct; whether the display and jump of the collection of multiple pushes are correct;

4. Share jump: whether the copy after sharing is correct; whether the jump after sharing is correct, display 5. Touch screen test: touch different locations at the

same time or perform different operations at the same time, check the processing status of the client, whether it will crash, etc.