A mobile phone in front of APP test preparation:
phone APP test, aimed primarily at android and ios two major operating systems, the main consideration is the functionality, compatibility, stability, ease of use (that is, human-computer interaction), performance .
Preparation before test: 1. Use the same type of products, not just the use of the test should be the same type of product. 2. familiar with our product spec documentation, and active exchanges pm. 3, writing test cases, no time must be at least a checklist.
Mobile APP two test points Test:
functional tests (test process, the test function point), compatibility testing, cross-testing, installation test unloading (including application upgrades), the stress test (interface test pressure);
functional test: to specific functional point eleven tests to ensure that each point can correctly implement the corresponding function; function is currently not reach the level of automation on the market, mainly by hand to measure. The problem with that is most special symbols, boundary value, buttons and the like. Basic functions, mainly refers to whether or not the app all the features of the design. Distinguish module, write a checklist, to avoid leakage test. Consider switch the screen anyway, but now many app only supports vertical screen.
Compatibility test: install the application on the mainstream perform the test equipment on the market, can ensure normal operation; compatibility considerations phone version, model, resolution. Different versions are differences, the general low version prone to problems.
Stability Test: main flash back, system crashes, and the like did not respond.
Usability testing: to consider the interface is attractive, easy to understand, the interface is clean, simple, no typos. Click OK range and so on. This part of the test, if the test is generally considered unreasonable demands will submit bug.
Performance Testing: tools to achieve mainly by CPU usage, memory usage, battery temperature.
Cross Test: For applications running into the case if other software SMS, telephone and other response will not affect the test application, and will ensure that the application will run correctly; the main consideration include phone text messages interference, low battery reminder, push reminders, usb plug reminder data line, charging reminders.
Install uninstall test: ensure that the application can correctly install, uninstall, and can correct operation (note test application upgrades: upgrade status before and after);
stress test: Users volume, high interactivity application interfaces required to perform a stress test to ensure It does not apply in the case of large amount of users to run correctly.
Field: network handover, signal strength and network operation app under weak conditions.
Three considerations:
flash back (out of memory, etc.), on the phone, the chance of such problems is large, should focus on testing, for example, access to a return module (data acquisition module from time to time), switch applications, resubmit , caller interaction are all great chance to flash back the cause.
The following is a note of when the function test point:
1. Log
● login user name and password error, the interface has prompts
● After the user is actively log out, the next time you start the APP, should enter login interface
● Support for automatic login of APP, data exchange, whether it can automatically log successful and correct operation of the database
● after the password change, or not to be valid data validation when logging
● for some pages of the operation is not logged in, whether made control
● switch account login, login test whether to do to update information
● for multiple end all operate to ensure correct operation of the database, and each side can see the data timely updates
● for some software, support a login account allows only one machine, then, need to check the account to log multiple cell phones, if the user removed the original, and can give tips
● when aPP switch to the background, switch back to the front of the test, such as login time, a call comes in
2, off-line
off-line application is in the local client caches part of the data to the next call work program
● for a These procedures, if necessary, after logging in, then under no circumstances can browse the local network data
● For when there is no network, get refreshed when new data can not obtain the data and can give prompt and friendly
● switch to the background, switch to the front again , you can see the normal
● offline and then connect to the Internet, this time when there are updates, you need to get new data from the server to the client data to update the data, and to update the local cache information
● For some interface does not provide offline data, need to give prompt and appropriate interface without any data after update
3, the database
android and IOS clients are using a database,
when the APP need to save data on the client, they will create the appropriate database table, the most common is the preservation of the account, then test points are mainly:
● Like a general database, you need to check the data add, delete, change,
● clients use namely construction, when the table does not exist when, will automatically create
● after the data table is deleted, the new data in the table can automatically retrieved from the server to come back and save
● when the data is modified, deleted, client and server can have a corresponding update
● access to data, the client is to compare and from the acquisition or server-side data directly from the client
data ● for the client from the server-side update, whether the client has stored locally.