1. Common concerns of App testing
1. App functional test
Functional testing is our first test. Only when the function is implemented can it meet the minimum standards for online release. We need to detect whether the product function has been realized, whether the product function meets the design requirements, whether the product function is repeated, and whether the product has repeated functions.
2. App installation and uninstallation test
installation:
1) Whether the software is installed properly under different operating systems.
2) Whether the software can run normally after installation, and whether the installed folders and files are written to the specified directory.
3) Whether the combination of software installation options meets the outline design specification
4) UI test of the software installation wizard
5) Whether the software installation process can be canceled, after clicking cancel, whether the written file is handled as the outline design description
6) Whether the handling of unexpected situations during the software installation meets the requirements (such as crash, restart, power failure)
7) Is there a corresponding prompt when the installation space is insufficient
8) No redundant directory structure and files are generated after installation
9) For installations that require network verification, try it when the network is disconnected
10) It is also necessary to test the installation manual, and whether it can be installed smoothly according to the installation manual
11) The description of the app during installation, such as version number, mobile phone system version requirements suitable for installation, etc.
12) Some permissions obtained during installation, such as camera, recording, etc.
13) Install again after installation, or update and install the app
14) App icon and name display after installation
15) The prompt message during the installation process is normal
process:
1) Whether it is running after installation and whether the process exists
2) After killing the process, is it normal to enter the app again?
3) Uninstall while the app is running
4) Uninstall when the app is not running
Uninstall:
1) Directly delete the installation folder and uninstall whether there is a prompt message.
2) Test whether the system directly uninstalls the program if there is a prompt message.
3) Test whether all files are deleted from all installation folders after uninstallation.
4) Test for unexpected situations (such as crash, power failure, restart) during the uninstall process.
5) Whether the uninstallation supports the cancel function, and the software uninstallation after clicking cancel.
6) The system directly uninstalls the UI to test whether there is a progress bar prompt for the uninstallation status.
7) Whether there are residual folders after uninstallation
3. App UI test
Test the layout of the user interface (such as menus, dialog boxes, windows and other controls), whether the style meets the requirements, whether the text is correct, whether the page is beautiful, whether the combination of text and pictures is perfect, whether the operation is friendly, etc.
(1) Navigation test: Whether the navigation is intuitive, whether the navigation help is accurate and intuitive; whether the navigation is consistent with the page structure, menu, and connection page style;
(2) Graphic test: the label style of the page, the operation of each control is convenient and unified; the pictures on the page should have practical meaning and require an orderly and beautiful overall;
(3) Content test: Whether the content of the description text in the input box is consistent with the system function; whether the length of the text is restricted, and whether the content is unclear;
4. App compatibility test
Check whether it is compatible with local and mainstream apps, and whether each device is compatible (compatibility of different mobile phone screen resolutions, compatibility of different mobile phone brands, compatibility of different mobile phone operating systems)
5. App cross event test (also belongs to the category of functional test)
Check whether the front/background switching during APP operation affects normal functions, whether the APP can respond normally when making/receiving calls when the APP is running, whether the APP can respond normally when sending/receiving information when the APP is running,
Whether the APP can respond normally when sending/receiving mail when the APP is running, whether the browsing network can respond normally when the APP is running, and whether the APP can respond normally when using Bluetooth to transmit/receive data when the APP is running.
6. App security test
detects whether the software has a formal digital signature, whether the software program is encrypted, whether sensitive data has desensitization display, whether there is encryption during data transmission, security vulnerabilities, system vulnerabilities, software permissions (such as restrictions/ Allows to read text messages, make calls, access contact information, etc.).
7. App's weak network test
You can use Fiddler or Charles to simulate a weak network environment to test the response time of an operation of the App in a weak network environment, the friendliness of the UI interface (whether it prompts no network, etc.), whether the request is automatically reissued after the network is disconnected, etc.
8. App performance test
Check whether the various performance indicators of the system under normal conditions and peak conditions are normal. The performance indicators mainly include: response time (the time it takes for the application to respond from the request to the client to receive the response), the maximum number of concurrent users, throughput, CPU memory usage, power consumption, and traffic.
9. App upgrade and update test
(1) When the client has a new version, the user can cancel the update, the old version can be used normally, the user will start the app next time. The update prompt still appears;
(2) When the version is a mandatory upgrade version, but the user did not update after the mandatory update is given, exit the client, and the next time the app is launched, the mandatory upgrade prompt will still appear;
(3) When the client When there is a new version, without deleting the client locally, directly update to check whether it can be updated normally, and check whether the updated client function is a new version;