Recently, I have sorted out the experience and experience of mobile terminal testing in the past three years to share with you. I hope you will actively leave a message to discuss! ! !
1. Mobile App is more complicated than program testing on PC
Various compatibility, multiple resolutions, multiple exceptions. Makes testing on mobile apps more complicated
2. How to design Test Case in mobile APP testing
The development pace of the mobile Internet is fast, and the version is iterated rapidly. It is recommended to abandon the traditional Tese Case completely, and there is no need to write detailed test cases. And use feature list. For example, use the method of mind mapping tool + function point. This saves a lot of time. Moreover, the mind map is more intuitive, and it is not easy to miss functions.
3. Make yourself a real user
Most mobile apps are for ordinary users, not business users. To make yourself a real user of the APP, so as to thoroughly understand the business logic
Fourth , pay attention to user experience testing
The key to the success of user experience APP, on such a small screen, the user experience is related to the user's satisfaction with the APP
Five, do less UI automation, do more automation of the background interface
Most of the time UI automation is meaningless, the investment is large, and the income is small. More attention should be paid to automated testing of background excuses
6. Important principles: Test the version of the app you will eventually release to users
The concept of daily construction and daily testing has been deeply rooted in the hearts of the people. Many times we test the development and debug versions of the App. Instead of the final Release version, when packaging the final Release version. We generally add digital signatures, or add code obfuscation. Then there must be some inconsistencies between the final release version and the Debug version. It is likely that the final version will have issues. For example, the Debug version is completely working properly, but it is found after going online that it will cause a crash
7. Both HTTP and HTTPS must be covered
Many apps and background services interact through HTTP. Under normal circumstances, everything is normal. Why do you need to test the HTTPS environment? In some free Internet environments, such as McDonald's and Wanda Mall, their network environment requires entering a user name and password to access the network through SSL authentication. If you use HTTP Client's Library to not capture this exception, your APP will definitely crash.
8. Carry out the test when the network is abnormal, the server is down or 404, 502 occurs.
The stability of background services is sometimes difficult for you to control, especially when DNS and space service providers are involved. If there is a DNS parsing failure, in this case, your request to the background API is likely to have a 404 error, and the data you interact with the API should be in a certain fixed format such as JSON and XML, so that your data parsing such as An error will occur, an exception will be thrown. If you don't handle exceptions properly, your program may not work properly.
Nine, 2G, 3G, 4G wifi must be covered
These four are not just differences in network speed, they represent different network environments. There are often some apps that can run under 3G network, but not under wifi. So you need to check in different network environments.
10. AppStore's lengthy review mechanism
Once your app has a serious system error, it is almost impossible for your repaired version to be available on the App Store in a short period of time. Then your users will leave.