1. Functional testing
- Write test cases based on product requirements documents and conduct testing
- Functionality includes a single functional module of the client and functional business logic (functional interactions such as: equivalence classes, boundary values, exceptions or illegality, etc. need to be considered where input is involved)
For details, please refer to this article
2. Special tests
2.1 Compatibility [Key Points]
-
Mobile phone model: different brands, different models (Huawei P30)
-
Operating system version:
- Android: Obtained based on data from online statistics platform
- ios
-
resolution
-
Screen
- Size: 5.1. 5.54.7
- Type: Notch screen, water drop screen, curved screen, folding screen
-
Network: Mobile Data and WiFi
-
Application compatibility
- Mobile phone hardware: physical buttons on the mobile phone (volume button, home button, power button)
- External hardware: Bluetooth device Wired device
- Operating system settings: wlan time positioning
- Other APPs: APPs with background playback functions, such as music
2.2 APP project installation, uninstallation and upgrade testing [Key points]
1.2.1-Installation, uninstallation and upgrade testing (installation testing focus)
Installation, uninstallation, and upgrade: APP is a client program, and the client program needs to be installed in advance before it can be used. Therefore, it is necessary to test the installation, uninstallation, and upgrade operations.
1.2.2-Installation, uninstallation and upgrade testing (uninstallation and upgrade testing focus)
installation
- normal scene
- Install from different sources
- Installation of different operating systems
- Installation in different paths (mobile phone\SD card)
- Abnormal scene
- Interrupt the installation (shut down and disconnect the network), can the installation be resumed after the interruption?
- Insufficient storage space to install
- Can the installation be normal after manually canceling or pausing and resuming during installation?
- Can the installation be overwritten while it is running (running in the background\running in the foreground: you need to consider whether it will interrupt user operations)
- Lower version covers higher version
- Uninstall and then install (will data be cleared after uninstalling)
uninstall
- Normal uninstall (uninstall on mobile phone) Use third-party software to uninstall)
- Uninstall while running (running in the background)
- Cancel uninstallation (third-party software\cancel when confirming the second pop-up window)
- Interrupt uninstallation (shutdown)
- Data remains after uninstallation (the user is prompted for confirmation. If the user agrees to remain, the data can be retained; if the user refuses to remain, the data cannot be retained. If no confirmation prompt is made, the residual data needs to be cleared by default)
upgrade
- Upgrading from an adjacent version (.last released version)
- Cross-version upgrade (historically released versions)--------The current version is n: n-2 upgrade n;
- Upgrade from different channels
- Upgrade successful reminder (red dot prompt\message prompt)
- Whether to remind before upgrading (message push prompts for upgrade\forced upgrade without reminder)
- Develop and upgrade the system by yourself (both daily upgrades and forced upgrades are required)
- Use third party (daily upgrade\forced upgrade)
- Whether the current version has the ability to upgrade (n upgrade n+1, upgrade rules)
2.3 APP project cross-event testing [Key points]
Cross-testing: Also called conflict testing or interference testing, it refers to a test in which a function is being executed and another event or operation interferes with the process. For example: running the App in the foreground/background while answering calls or downloading files, etc.
Cross event testing focus:
➢ Make calls while the APP is running:
➢ Send and receive messages while the APP is running:
➢ View application push notifications while the APP is running
➢ Connect the Bluetooth device
while the APP is running ➢ Receive file pop-up reminders
while the APP is running ➢ Rotate the screen while the APP is running
➢ Switch networks while the APP is running (4G, Wi-Fi):
➢ Use the camera, calculator and other mobile phone built-in applications when the App is running:
➢ Battery alarm, plug and unplug the charger when the App is running.
Precautions
- Simulate user usage scenarios. All scenarios that may affect the normal operation of the AP are cross-event considerations.
2.4 PUSH message test (understanding)
1.4.1-Basic knowledge of push messages (what is a push message)
What is a Push message?
●Push messages: These are various messages pushed to you by the APP.
●Usually "Settings" - "Notifications" on the mobile phone are used to set push messages, so push messages need to be tested.
When will Push messages be used?
Message push scenarios:
●Product perspective: functional needs, such as: news push for information products, announcement push for tool products, express delivery notifications, etc. ●Operation perspective
: activity operation needs, such as: Promotional activities for e-commerce products: recalling users/increasing activity, etc.
1.4.2-Push message push basics (message push principle)
precautions
●In the APP project, based on the consideration of mobile phone power and traffic, the push method is used to push messages, so it is also called Push message.
1.4.3 Basic knowledge of Push message (Push message push method)
- Push server (whether to push according to rules)
- push content
- Push time
- Push frequency
- Pushed object
- Mobile terminal
- If you do not receive messages, you will not receive any push
- receive messages
- How to display messages when APP is running in the foreground
- How to display messages when APP is running in the background
- How to display messages when the APP is offline?
- Can the message be opened?
- Set when receiving
- Receive messages but not remind: mobile phone reminder will not be triggered
- Receive messages and remind: Trigger reminders while receiving messages (combined with mobile phone mode: silent mode\vibration mode; ringtone)
- Receive messages but do not display the message content (for example: a message is sent from WeChat)
2.5 User experience [Key points]
- UI interface testing (whether the prototype design is reasonable)
- Horizontal and vertical screen testing (whether content display is abnormal)
- Usability test (empty data prompt\whether the menu level is too deep, whether there are too many business operation steps, whether the button position is appropriate)
- Accessibility functions on mobile phones (color blind mode\blind mode)
Live experience
- You can find people who meet the conditions for target users
- You can find a novice user experience (people from other teams within the company who have not been exposed to this project)