Web app testing focus:
1.
Functional test
: Whether the implementation of the function meets the requirements.
2.
Performance test
:
2.1
Link Speed Test
: Test the speed of page links
2.2
Load testing
: How many users can the web application system allow online at the same time? What happens when this number is exceeded?
2.3
Stress test
: Test whether the web application will crash under certain pressure and where the performance bottleneck is.
3.
User interface test
: whether the interface is harmonious and beautiful, whether the style is consistent, and whether the page can be scaled proportionally
4.
Compatibility test
:
browser
(different versions from different manufacturers), resolution
5.
Safety test
:
5.1 Is there a limit on the number of logins and whether there is a timeout limit (whether the user will automatically log out if he does not do any operations within a certain period of time after login)
5.2 Log files and cookies (do these two explicitly display the user password account?)
Mobile app testing focus:
1.
Install and uninstall
1.1 Whether the application can be installed on different system versions of IOS or Android (some system versions are too low, the application cannot be adapted)
1.2 Whether the software can run normally after installation
1.3 Is it possible to cancel during the installation process?
1.4 Is there a corresponding prompt when the installation space is insufficient
1.5 Whether there is a corresponding prompt when the network is disconnected during network installation
1.6 Can the software be uninstalled normally?
1.7 If there are accidents such as crash, power failure, and restart during uninstallation, whether it can be uninstalled correctly after the environment is restored
1.8 Can it be canceled during the uninstall process, and whether it can be used normally after clicking cancel to uninstall
1.9 Whether there is prompt information directly written in the program
1.9 Whether to delete all installation folders after uninstallation
2.
Login
2.1 Is there a prompt on the interface when the account number and password are wrong?
2.2 After the user actively logs out, the login interface should be entered at the next restart
2.3 Can you log in correctly and automatically when you remember your password?
2.4 After the password is modified, whether the next login will be synchronized in time (login with the original password prompts that the password is incorrect)
2.5 Whether some pages are controlled when operating in the unlogged state (please log in first to add the product to the shopping cart when not logged in)
2.6 Whether the user information is updated in time when switching accounts (QQ switches associated accounts, and user information changes in time)
2.7 When operating on multiple terminals, ensure that the data is accurate and that each terminal can see the updated data in time (QQ: computer,
mobile phone
)
2.8 Log in to the same account on different IOS and android devices to modify the data to ensure that the data is correct and the updated data can be seen in time
3.
Run
3.1 Can it be opened and used normally after installation?
3.2 Whether there is a loading prompt at runtime
3.3 Whether the running speed and the switching speed between modules are smooth
4.
Offline
4.1 Can I browse local data after disconnecting from the Internet?
4.2 Whether there is a friendly prompt when the network is disconnected when acquiring data
4.3 Can the network be used normally after reconnecting after disconnection
5.
Message push switch
5.1 Whether the message push switch is enabled by default (it is enabled by default)
5.2 Whether the push switch can be turned on and off freely
5.3 Whether the push switch is turned on to receive message push normally
5.4 When the app hangs up in the background, the mobile phone message bar can receive message reminders, you can click to view, and disappear from the message bar after clicking
5.5 The message prompt will not enter the message bar when the app is running
5.6 Turn off the push switch and cannot receive push messages
6.
Software Updates
6.1 Show that when the client has a new version, there is an update prompt
6.2 Make sure that both IOS and android can update the latest version, can be installed and run normally
6.3 When the version is a non-mandatory upgrade version, the user can cancel the update, and the old version can be used normally. The user can still get an update prompt the next time they start the app
6.4 When the version is a mandatory upgrade version, when the user does not update after the mandatory update is given, exit the client. The next time you start the app, the forced upgrade prompt still appears.
6.5 When the client has a new version, without deleting the client locally, directly update to check whether it can be updated normally.
6.6 When there is a new version of the client, without deleting the client locally, check whether the updated client function is a new version.
6.7 When there is a new version of the client, without deleting the client locally, check whether the resource file with the same name, such as a picture, can be updated to the latest version normally. If the above cannot be updated successfully, it is also a defect
7.
Exception testing
7.1 Is the correct prompt for insufficient memory when the app is running?
7.2 When the app is running, whether the power is suddenly cut off, the network is disconnected, the point is constantly updated, the background is switched, whether it flashes back or crashes (abnormal test)
7.3 What are the tips for making or receiving
calls
, sending messages, receiving emails, and starting the camera when the app is running?
7.4 App response speed under 2G, 3G, 4G, WIFI network
7.5 When the network is not good, whether the submitted data has been processed and submitted, whether there is a delay, and whether there is a reminder when the submission fails
7.6 When there is a network to no network and then to a network, whether the data is submitted and the operation is loaded normally
8.
Switching between the front and back of the application
8.1 Switch the app to the background, then go back to the app to check whether it stays on the last operation interface
8.2 Switch the APP to the background, and then return to the app to check whether the function and application status are normal. The processing mechanism of IOS4 and IOS5 is different.
8.3 When the app switches to the background and then returns to the foreground, pay attention to whether the program crashes and whether the functional status is normal, especially when the data is automatically updated when switching from the background to the foreground.
8.4 After entering the app after the phone locks and unlocks the screen, pay attention to whether it will crash and whether the functional status is normal, especially when the data is automatically updated when switching from the background to the foreground.
8.5 When a phone call is interrupted during the use of the app, and then switch to the app, is the functional status normal?
8.6 When the app process is killed and the app is restarted, can the app start normally?
8.7 After the prompt box that must be processed appears, switch to the background, then switch back to check whether the prompt box still exists. Sometimes there is a defect that the application automatically skips the prompt box.
8.8 For pages with data exchange, each page must be tested for switching between front and back, and lock screen. This kind of page is most likely to crash.
Reprint: http://www.51testing.com/html/63/n-3719663.html