Mobile app non-functional test point collection

Non-functional testing
Another important aspect of mobile app testing is the non-functional requirements of mobile apps. Mobile testers have many questions to test before they launch the market or make further development.
The first test to be performed in the early stages of development should be a usability test. This is usually done by an alpha user or colleague. Walk into a café or restaurant and ask the people inside about their app usage. Let them look at the first version of the current development and collect feedback to see if the user can use the new feature well in order to get a first impression.
Check the app's performance. Compare the released version to the current version to see if performance is the same. Better? Or is it worse? Install the app on your old device to see if the app still works on your old device, whether it's good or bad for your hardware device. The most advanced equipment will do the same.
Test phone, SMS, MMS, Twitter or other notifications come in when the app reacts. Check your battery when using the app. Make sure the test process test equipment is fully charged and check the battery usage every 10 minutes to see if the app consumes too much power. Install the app on the device at low power to see what happens. Check your app's memory usage. If the app stores data in a local file system, test the usage of different memory cards. Think about what happens when local storage is almost full.--app will crash or pop up an error alert box to notify the user?
Test the app's installation and removal process. More importantly, test the process of upgrading from an older version to a new version. Perhaps the local database has changed, which can cause some serious migration problems.
Is the app localized? Testers need to test the app in different languages. Remember to test with different network speeds on different web carriers. Make sure the app works in GPRS, EDGE, UMTS, LTE and WiFi environments.
Don't forget to check how the app reacts when the Internet connection is bad or completely dropped. Use the app in airplane mode to see what happens if a request fails. Connect the test device to your computer and check the development log file for exceptions, warnings, or other strange anomalies. These are just a few of the non-functional requirements that mobile testers and developers should consider when developing and testing an app. It is never possible to check in place on every aspect, so the overall team should support QA members to cover as many aspects as possible to prevent users from getting a bad experience.

Summarize:
?? Do a usability test.
?? Compare the performance of the app's released version and the new version.
?? Check your phone, SMS, MMS or Weibo or the app's response when you come in.
?? Check the power of the test equipment.
?? Test your app's memory usage.
?? Install and remove apps.
?? Test the process of upgrading from an older version to a new version.
?? Check the conversion of the language.
?? Use apps in different vectors and network connections, such as Gprs,wifi, or LTE, in the environment.
?? Check the log file for errors or exceptions.

Mobile app non-functional test point collection