Shulou(Shulou.com)06/03 Report--

Introduction

For the mobile phone project (application software) of the product, the main purpose is to test the system. For the system testing of mobile application software APP, we usually carry out the following aspects: functional module testing, compatibility testing, installation and uninstallation testing, software update testing, performance testing, user experience testing, cross event testing, user interface testing and so on.

Key points and common defects of functional testing

Common functional defects

APP crashes

This is a common problem in testing, and this kind of problem is also very serious, which will directly affect users' first impressions of the product. For example, if we are using an APP, we will stop responding when we are using a sudden application, a "forced close error" window pops up on the interface, the application needs to be forcibly closed, or the phenomenon of flickering occurs when we are in use. These conditions affect the user's experience and cause the user to uninstall the APP. A general test scenario that triggers a mobile APP crash is as follows:

Verify APP behavior on multiple devices with different screen resolutions, operating systems and operators; verify APP behavior with newly released operating system versions; verify APP behavior in environments with sudden network quality changes such as tunnels, elevators, etc.; verify APP behavior through manual network changes from cellular to Wi-Fi, or vice versa; verify APP behavior in an environment without a network Verify APP behavior when incoming calls / text messages and device-specific alerts (such as alerts and notifications); verify APP behavior in different view modes by changing the direction of the device; verify APP behavior when the device is out of memory; verify APP behavior by loading with test tools; verify APP behavior with different supporting languages.

The function is not implemented or only partially implemented

This kind of problem often occurs in the process of testing. Some of the versions sent for testing only achieve partial functions, but do not achieve all the functions in the product requirements statement, such as bill details query. It is required to show the details of each transaction bill and whether it has been recorded, and the development has realized the details of each transaction bill, but it has not been realized to show whether the bill has been recorded.

Function implementation error

The functions in the product requirements specification are not implemented, for example, according to the product requirements specification, users in the whitelist are not subject to single sign-on restrictions when logging in, that is to say, the same account can log in on both A mobile phone and B mobile phone at the same time, but the development and implementation is wrong. After logging in on A mobile phone, the whitelist users log in on B mobile phone, and then click the APP function on A mobile phone. A prompt will pop up: the account has been logged in on phone B, and phone An is forced to log out.

Key points of functional testing

Write test cases according to product requirements documents

Software design documentation use case

Test requirements: to ensure that the input data is correct, and carried out the correct operation, clear the correct output results and intermediate data value and format.

Key points of compatibility testing and common compatibility defects

The common versions of IOS system are 7.0,8.1,8.4,9.1, the hardware is common iPhone 4S, iPhone 5, iPhone 5S, iPhone 5C, iPhone 6, iPhone 6S, iPhone Plus, iPad series; the common Android versions are 4.3,4.4,5.1,6.0, and the hardware is innumerable, different brands, such as Samsung series, Huawei series, Xiaomi series, OPPO series, VIVO series and so on.

Testing APP has a variety of problems due to different software and hardware on different models. These are all places where defects gather. A page may display normally on Android phones, but may show misplacement on iPhone phones, so try to cover mainstream phone models and versions in the test, such as iPhone series, Samsung series, Huawei series, Xiaomi series, oppo series, vivo series and so on. Find out the defects in using app on these mainstream phones and fix them.

Key points of installation and uninstallation testing and common defects

Common installation and uninstall defects

There is a flashback in the installation process; after the installation is complete, click APP does not respond; after the installation is complete, click APP,APP to flash; the old version already exists, but do not uninstall the old version, when you overwrite and install the new version, the version number is the version number of the new version, but the content of APP is still the old version.

Key points of installation and uninstallation test

Installation testing is very important. The first action for a user to use APP is to install APP. If there is a problem with installing APP, it will cause the user to abandon the APP directly. In the test, the test is mainly conducted from the following aspects:

Whether the application can be installed on different system versions of IOS or Android (some system versions are too low to adapt); whether the software can run normally after installation, whether the folders and files after installation can be written to the specified directory; whether it can be cancelled during installation, and whether there are corresponding prompts when the installation space is insufficient; check whether the installation package is complete, especially DLL, check the installation manual If the application needs to be installed through network verification, you need to test whether there is a prompt in the case of network disconnection, and whether the application can be deleted (either on the desktop or through software uninstall). It has been found that there is an application on the IOS phone that is not fully installed. After the installation is terminated, the uninstalled application icon will always be displayed on the phone and cannot be deleted successfully); test whether all the installation folders have been deleted after uninstallation; during the uninstall process, unexpected situations such as crashing, power outage, restart and so on can be correctly uninstalled after the environment is restored. Whether the uninstall supports the cancel function, and whether the software uninstall is normal after clicking cancel. Key points of software update testing: when the client has a new version, there is an update prompt; the software update must be tested to ensure that the Android software update can update the new version correctly and is installed and run correctly; ensure that the IOS software update is limited, and the official version can be tested only when the official version is in store and there is a version update; when the user cancels the version update, the old version can be used normally, but the update prompt still appears the next time you start the application. When there is a new version, if the client is not deleted, the direct update checks whether the client can be updated normally, and whether the function of the client is up-to-date after the update (normally, the local client can be updated without mandatory deletion; when a cross-version update occurs, the update can be successful. Key points of performance testing and common defects

Common performance defects

The loading time is too long; the application starts slowly for the first time; the speed of entering a certain interface is slow; when you start an animated interface, the animation execution process is not smooth, or the animation execution stutter takes a long time; there is no response for a long time in response to a user event; after the application runs for a long time, the random stutter occurs; the server fails to respond and reports a HTTP500 error; APP appears black and white screen; APP crashes.

Key points of performance testing

Performance is also an indicator of the quality of APP. If the loading time is too long, the response time is too long, and users are impatient to wait, they are likely to unload APP directly.

Whether the startup time of APP is too long; the consumption of CPU and memory when APP is used; whether the probability of Crash when APP is more can be analyzed and tested; the use of power flow when APP is used; the use of this resource in the case of repeated long-term operation; response ability test to verify whether the operation can meet the response request of users under various circumstances. User experiential testing and common defects

From the perspective of subjective ordinary consumers to perceive the comfort, usefulness, ease of use and friendliness of products or services. Through different individuals, independent space and non-empirical statistical reuse to effectively evaluate the experience characteristics of the product, and put forward suggestions to improve the potential customer satisfaction of the product. It is mainly tested in terms of ease of use and friendliness.

Common defects

Whether the interface display is beautiful, whether the color and font size of the interface are appropriate, whether the layout is beautiful, and whether the prompts are friendly.

Whether buttons, dialogs, lists and windows conform to the user's habits

Whether it is easy to navigate, whether the navigation is intuitive, whether the navigation is consistent with the page structure, menu, and the style of connecting pages.

Defects of user experience class

The display of the interface is not beautiful, the user is uncomfortable with the interface color, the interface color and buttons, other editing boxes, etc., the display layout of the picture and font is not beautiful (the text surrounds the picture), the font of the interface does not satisfy the user with poor eyesight, the menu is too deep, the related options are too far away, the button is not clickable (if the button is not available, be sure to gray out, or remove the button. Otherwise, it will mislead the user) Because of the long page loading time and the high requirements of the mobile end, it is generally required that there is no waiting interval to load, and the page loading time is too long, which will cause users to wait impatiently and abandon the APP; page typesetting for too long. Generally, few viewers are interested in looking at the bottom content of the page. 90% of users open a page and browse only the content of the first screen, thinking that they have seen it all and will not scroll down. A long page is easy to cause visual fatigue of visitors; unfriendly navigation, unfriendly navigation is the most impact on user operation, can not let users easily find their own content. The user comes to a page and does not know how to return to the previous page and does not know which column the current page is under. In this way, it is very likely that users will not come again once, which is why there is more emphasis on information architecture design, which is part of the information architecture. If users have to reopen APP every time to find content, it is difficult for users to retain; out-of-date information, information that has not been updated for a long time, it is easy to disgust visitors, and will greatly reduce the brand image of your product in mind. Out-of-date news, out-of-date promotional information, event information are fatal; dead links or link errors; lack of interactive content, lack of user participation, can not let users express feelings and ideas, this product is doomed to be a self-contained product. Now the most basic thing is to provide an entry for "feedback" so that loyal users of the product can express their views and collect this feedback to improve the product. In addition, there are interactive openings, which will also make users feel that the product is more open; malicious plug-ins, malicious pop-up windows; and rude and unfriendly prompts. Testing points and common defects of cross events

A testing method is proposed for the service level division and real-time characteristics of intelligent terminal applications. Cross-testing, also known as event or conflict testing, refers to a test in which a function is being executed while another event or operation interferes with the process. For example, testing the interaction between App and key applications such as incoming calls, file downloads, music listening and so on when running in the foreground / background. Cross-event testing is very important to discover potential performance problems in many applications.

Cross defect

The basic function of a mobile phone is to be used as a communication tool, so when we use APP, we will definitely have phone calls, text messages, Bluetooth, alarm clocks, etc., and these functions have a higher priority than APP. Once they appear at the same time, APP needs to be run in the background or processed to give priority to basic functions. In the course of testing, there will be phenomena such as phone crashing or jamming when entering APP, alarm clock ringing, APP hanging, phone entry while APP is running, phone can not be answered, and so on. The problem in this area is so serious that if APP causes the basic functions of the phone to be unavailable, users will not accept it anyway.

Main testing points of cross events

Whether simultaneous operation of multiple APP affects normal function; whether front / background switching of APP runtime affects normal function; APP runtime makes / receives phone calls; APP runtime sends / receives messages; APP runtime sends / receives mail; APP runtime switches networks (2G, 3G, Wi-Fi); APP runtime browses the network; APP runtime uses Bluetooth to send / receive data APP uses cameras, calculators and other mobile devices when running. Key points and common defects of user interface testing

Test the layout of the user interface (such as menus, dialogs, windows and other controllable controls), whether the style meets customer requirements, whether the text is correct, whether the page is beautiful, whether the combination of text and pictures is perfect, whether the operation is friendly, etc.

The goal of UI testing is to ensure that the user interface provides users with appropriate access or browsing functions by testing the functionality of the object. Ensure that the user interface meets company or industry standards. It includes user-friendly, humanized and easy-to-operate testing.

Defects of user interface classes

Does not conform to UI design or is inconsistent with the interface prototype

For example, the interface style of a function of APP is not consistent with the overall interface style, or is not coordinated with pictures, text, buttons, etc., although there is no problem in use, but the user feels very bad, and it also gives the user the impression that the R & D team is unprofessional or the product is shoddy, and the user will not use it for too long or uninstall it directly.

The interface display is incomplete.

Because the function of APP is relatively simple, but it has to give people an intuitive impression, pictures are used as the first choice, especially for product display on the home page or important information transmission media. However, in the actual testing process, there will be imperfect page loading, such as incomplete picture display and disordered button display. After the content of the new page is successfully returned, the content of the new page overlaps with the original interface content, the input content in the edit box is too long, and the request returns data and other content overlap with the server.

Page loading error occurs during pull-up refresh and drop-down refresh

In the mobile client, when the content is more than one page, the pull-up will load more content and load errors (prone to duplicate data, mismatch between picture and article, repeated loading of picture, inconsistency between article title and content, etc.)

APP testing essentials and common Bug classification and summary, science and technology change life, public testing uses the testing capabilities and resources of the public to complete a large number of product testing tasks in a short time. And always from the user's point of view, put forward suggestions to improve the function, ease of use and compatibility of the product. Public testing is bound to play an inestimable role in the next mobile application development and testing.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.