Our daily shopping, travel, payment and other activities are all inseparable from mobile phones, and many APPs have been derived from this.
For example, WeChat, Alipay, Weibo, Douyin, King of Glory, etc. are used very frequently every day.
APP testing mainly includes functional testing, performance testing, automated testing, security testing, compatibility testing, and special testing.
01 APP testing process
The APP testing process is similar to the web testing process and is divided into the following seven stages:
1. Write a test plan based on the requirements specification;
2. Develop a test plan, mainly the allocation of test tasks, testers and test time;
3. Test preparation, including setting up a test environment, preparing test data, and determining test methods;
4. Design and write test cases, review and supplement test cases;
5. When executing the test, first conduct a smoke test, and then test the main functional process, including a single functional module of the client, functional business logic function interaction, and regression testing;
6. Submit test results, including test cases and test plans;
7. Daily maintenance testing;
02 APP testing ideas
1. First, we get an app’s apk package or the app installation package downloaded from testflight, which needs to be installed and tested.
1. Before software installation: Is there any corresponding prompt for insufficient space?
2. The software is being installed: whether it can be canceled or paused during the installation process; whether the installation can proceed normally; whether there is a prompt if the installation space is insufficient.
3. After the software is installed: whether the application can be uninstalled through the desktop or through software settings; whether the uninstallation supports the cancellation function, and whether cancellation will affect the normal uninstallation of the software; whether the installation package will be automatically deleted after the installation is completed; repeated installation will prompt that the version already exists , or directly overwrite the installation, but it can be used normally.
2. The installed app needs to be upgraded and tested as iterative versions are updated.
1. Before upgrading: When the client has a new version, is there an update prompt?
2. After the upgrade: Update the current version immediately and upgrade normally. After the upgrade, the new version can be used normally.
3. Non-mandatory version upgrade: users can cancel the update, the old version can be used normally, and the update prompt will still appear when the user starts the app next time
4. Forced version upgrade: If the user does not update the app, he cannot use the app; if the user logs in to the app again next time, the forced upgrade will still be performed. After the forced upgrade, the new version can be used normally. – Mainly used for gaming apps
5. Online cross-version upgrade: Analyze the version most used by users through operational data. If not, you can choose the latest 5-6 versions; after the upgrade, the new version can be used normally.
6. What is the scope of version upgrade testing coverage - old functions + new requirements; 1) new requirements, detailed testing; 2) ensuring the normal use of old functions
3. App functional testing, that is, the functional business logic that needs to be implemented in app product design
1. After designing and reviewing use cases according to the product's requirements document, execute test cases to verify the correctness of the business logic.
2. Verify the correctness of data based on business logic, such as order data, payment data, withdrawal data, etc.
4. App security testing
1. Security testing – permission testing, login authentication, interface sensitive data encryption
2. Deduction risks: including sending text messages, making phone calls, connecting to the Internet, and can you be reminded when there is no Internet === Friendly reminder
3. Privacy leakage risk: including access to mobile phone information, access to contact information, etc.
4. Whether to allow access to the photo album, open permission for taking pictures + no permission, whether to allow recording, whether to allow positioning, whether to allow receiving push notifications
5. App compatibility testing
2. Whether the application can adapt to various screen sizes and resolutions. The resolution affects the size of icons and text. Ensure that the page is displayed completely under mainstream resolutions and the text is not blocked.
3. Summary: Select the mainstream models on the market for compatibility testing.
6. App weak network test
1. Test the switching of 2G/3G/4G/5G/WIFI network, switch from wifi environment to 4G environment, prompt whether to enable 4G network, and whether there will be a reminder for deduction.
2. Test network/no network switching: from network to network to network, whether the data can be automatically restored and loaded normally; when there is no network, whether the various prompt messages are friendly
3. Weak network test (delay + packet loss): Pay attention to whether there is a reasonable prompt for timeout in a weak network scenario, and whether there is a resend mechanism; whether the submitted data is always being processed and submitted, whether there will be a delay, and whether there will be a failure in data exchange. There is a reminder; if the data is submitted multiple times (payment app), can it only be executed once?
7. App performance testing
1. The response time of various functional operations of the app (performance of the background server)
2. Pressure stability test (for example: monkey)
3.cpu usage
4.Memory usage
8. App push message test
1. Switch setting: the default state is all on/pop-up reminder selection after installation, the client can receive push information; the setting switch can be turned on or off; when the app setting switch is turned off, the client cannot receive push messages
2. When the mobile client does not lock the screen: the app is running in the background, and push messages can be accepted normally and can be clicked to view; on the main interface or when using another app, click on the message to jump to the app; when the app is used in the foreground, messages can be received Go to the message reminder, click to view
3. When the mobile client locks the screen: whether the message push is accepted normally, prompt sound, bright screen, middle list display; click on the message push, unlock first, jump to the app after unlocking, etc.
4. Login status: After logging out, whether to accept message push (depending on the needs to see whether the message is pushed.
To sum up, in our daily app testing, the most important things are actually the functional testing of the app and the compatibility testing of the app (because there are so many models in the world, we need to cover mainstream models and operating systems). The other point is the key point. Pay attention to app performance.
Finally, I would like to thank everyone who reads my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, if you can use it, you can take it directly:
This information should be the most comprehensive and complete preparation warehouse for [software testing] friends. This warehouse has also accompanied tens of thousands of test engineers through the most difficult journey. I hope it can also help you!