Phone software testing software testing tutorial

First: Compatibility Test (Reprinted Source: Thousand Feng)

  For App will normally consider these aspects:

  1) operating system version

  Including Andoird version, iOS version

  2) Screen Resolution

  android 800*480, 960*640,1280*720(720p),1920*1080(1080p),2560*1440(2k).

  For iOS, consider the recent generations of models corresponding to the resolution.

  3) different manufacturers ROM

  Different manufacturers ROM, most of the manufacturers are on the android system has been customized, practical experience and underlying services such as calling cameras appear incompatibilities and different phone a shake encounter different problems for sensitivity setting direction and gravity sensor .

  4) the type of network

  Network types are generally considered wifi, functional case 2g, 3g4g under. Also consider a different type of browser and screen resolution for m site.

6801ee9b01b743e8b663844ac70bcdf5.jpg

  Second: flow test

  Moving the product in the test, it is necessary to use to measure the flow rate App, broadly speaking, it can be divided into traffic from the correlation of the angle of the user: one is led directly to a user's operation flow consumption; Another is a background that does not flow directly consumed in user usage.

  Test Method traffic:

  1. Based on the system comes with features.

  eg android proc/uid_stat/{uid} /tcp_send

  android proc/uid_stat/{uid} /tcp_rcv

  2. Data acquired by API or Buried system.

  3. The general flow test methods: capture phone or wifi agent (Fiddler, Charles).

  Common Flow-saving method:

  1 data compression.

  Compression compression interface contains text data, and image compression js file.

  2. The use of different data formats

  E.g. JSON format as the interface returns the data format is usually smaller than the XML format.

  3. The frequency of access control

  This report mainly for background information, PUSH messages and inspection of the timing mechanism.

  4. Only necessary data

  Sometimes an APP content is very large, and the user may only see part got me too much data from the background is a waste, so the split-screen mode to load or lazy loading can be used to reduce traffic consumption.

  5. Cache

  Images, js and other data can be stored temporarily, but due to limited phone memory, also need to control the entire cache size, and to provide users with the option to clean the cache.

  6. for different types of network access policies different design

  Some of the contents of different network types APP return is not the same.

8b84c13e471241a9970d1424a8609f56.png

  Third: power test

  Under the premise of not made a huge breakthrough in the electrical battery technology, this area will always exist some bottlenecks, if some App architecture design is not good, or even the code defect, it could lead to power consumption is relatively high, so the battery test is also very important.

  Tools GSam Battery Monitor Pro.

  Fourth: Weak network test

  Compared to PC Internet Mobile Internet products, there is a feature of the former use of the network is more varied, in addition Wif, is often used in a mobile network, the mobile network has encountered more complex, such as subways, tunnels, Stadium. So the network is more prone to instability, a number of issues App in many cases are only exposed to a complex network conditions, rather than let users find these problems and complaints, as we try to simulate this network conditions during the testing phase , early detection and fix these problems.

  tool:

  Network Delay Simulator at 1. Windows

  Network Link Conditioner under 2. Mac

  Fifth: Stability Test

  The basic function of ensuring the proper foundation, stability App it is very important, if an App often flash back or stuck, the user experience will be greatly hurt, is likely to result in the case of other competing products the loss of customers.

  Sixth: Safety Testing

  Including safety testing of the installation package (can decompile the code package is a signature, integrity checking, checking permissions, etc.).

  Test sensitive information (databases, logs, configuration files).

  Soft keyboard hijacking (user name and password input box financial APP login page),

  Account security (password is plaintext password transmission is encrypted, enter the account number of errors too many locks, while reminding the session, cancellation mechanism)

  Data communication security (or hash key data is encrypted, using a secure communication connection is critical, whether the digital certificate to verify the legitimacy, whether legitimacy check data.

  Component safety testing.

  Interface test server (SQL injection testing, XSS XSS, CSRF cross-site request forgery, unauthorized access, etc.).

b2997ba6f9c3470a9a97f0827cb415f4.jpg

  Seventh: environment-related test

  In a real project, there are some flaws I found and operating environment in which the App-related, so the design of test time, to take account of these scenarios, such as:

  1) interference testing

  Receive calls, receive SMS, receive a notification bar message, no electricity prompt box pops up, third-party security alert pop-up.

  2) The Rights Test

  Some users when in actual use App conscious return to block certain functions. For example, some users feel let an App to access the phone book or album may leak privacy, you set permissions on the App banned access to the album in your phone.

  3) Limit Testing

  Phone environment itself also has its limits if necessary to cover the test. Common scenarios are:

  Available storage space is too small, no SD card / dual SD card, flight mode, the system time is wrong (and later than the earlier standard time), rely on a third party (such as our App App rely on third parties, but now there is no third-party App install or test case version too low).

  4) Android placement test

  Simulation with whitebox

Guess you like

Origin blog.csdn.net/IT_studied/article/details/89156241