App test essentials and common bug categories

Introduction

For the product of the mobile phone project (application software), mainly for the system testing. For system testing of mobile application software, 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, etc.

Key points of functional testing and common defects

Common functional-class defects

App crashes

This is a common problem in the test, which is very serious, it will directly affect the user's first impression of the product, for example, we are using an app, is using a sudden application to stop responding, the interface pops up a "Forced close error" window, the need to force the application to close, or is in use when the phenomenon of flash. These conditions affect the user's experience and cause users to uninstall the app. The common test scenario for triggering a mobile app crash is as follows:

1. Verify app behavior on multiple devices with different screen resolutions, operating systems and operators;
2. Verify the app's behavior with the newly released operating system version;
3. Verify app behavior in environments such as tunnels, elevators, and so on, where network quality suddenly changes;
4. Change from cellular to Wi-Fi via manual network, or in turn, verify app behavior;
5. Verify app behavior in a network-free environment;
6. App behavior when verifying incoming/SMS and device-specific alerts (such as alerts and notifications);
7. Verify app behavior by changing the direction of the device and using different view modes;
8. Verify app behavior when device memory is low;
9. Verifying app behavior by applying loads with test tools;
10. Verify app behavior in different supported languages.

Feature is not implemented or only partially implemented

This kind of problem in the testing process also often appear, the release of the test has only partially realized the function, did not realize the full functionality of the product requirements specification, such as billing details, request to display the details of each transaction bill and show whether it has been accounted for, developed to achieve the details of each transaction bill, However, it is not implemented to show whether the bill has been recorded.

Feature implementation Error

Not according to the function of the product requirements specification, such as in accordance with the requirements of the product specification, the white list of users do not subject to single-point landing restrictions, that is, the same account can be at the same time in a mobile phone and B mobile login, but the development of implementation errors, white list of users in a mobile login, b mobile Login, Then click on a mobile phone app features, will pop up prompt: The account in the B phone is logged in, a mobile phone forced to log out.

Functional Testing Essentials

Write test cases according to the product requirement document;
Software design document writing use case;
Test requirements: To ensure that the input data is correct, and the correct operation, clear the correct output and intermediate data values and format.

Compatibility test essentials and common compatibility flaws

Common IOS versions are 7.0, 8.1, 8.4, 9.1, etc., hardware common iphone 4S, iphone 5, iphone 5S, iphone 5 C, iphone 6, iphone 6S, iphone Plus, IPad series, Android common version has 4 .3, 4.4, 5.1, 6.0, the hardware is a number of countless, different brands, common such as Samsung series, Huawei series, Millet series, OPPO series, Vivo series, etc.

Test app on different models due to software, hardware and other different problems, these are the place of the defect aggregation, a page may appear on the Android phone normal, but may appear on the iphone misplaced, so the test as far as possible to cover the mainstream phone models and versions, such as the iphone series, Samsung series, Huawei series, Xiaomi series, Oppo series, Vivo series, and so on, find out the defects and repair of using the app on these mainstream phones.

installation, unloading test points and common defects

Common installation, unloading class defects

1. During installation, the Flash-back occurs;
2. When the installation is complete, click the app to not respond;
3. After the installation is complete, click App,app to Flash back;
4. An older version is already present, but the old version is not uninstalled, and when you overwrite the new version, the version number is the version number of the new version, but the content of the app is still the old version.

Install and Uninstall Test Essentials

Installation testing is important, the first action users use the app is to install the app, if there is a problem installing the app, will let users directly discard the app. Tests are mainly tested in the following areas:

2. Whether the app can be installed on different system versions of iOS or on different versions of Android (some systems are too low to fit);
4. Whether the software can be run properly after installation, whether the folder and files after installation can be written to the specified directory;
6. Whether the installation process can be canceled, the installation of insufficient space when there is a corresponding prompt;
8. Check the installation package is complete, especially the DLL, check the installation manual;
10. If the application needs to pass the network authentication and so on installs, needs to test the disconnection situation to have the corresponding prompt;
12. Whether you can delete the app (either from the desktop or from the software to uninstall the installation.) Have found an app installed on an iOS phone is not fully installed, after terminating the installation, the app icon for the unfinished installation is always displayed on the phone and cannot be deleted successfully;
14. Tests whether the file deletes all installation folders after uninstallation;
16. During the unloading process, the crash, power outage, restart and other unexpected situations, if the environment after the restoration can be properly unloaded;
18. Uninstall whether to support the cancellation feature, click Cancel after the software uninstall condition is normal. Software Update Testing Essentials
20. When the client has a new version, there is an update prompt;
22. Software updates must be tested to ensure that the Android software update can update the new version correctly, and that the installation is running correctly;
24. Make sure that iOS software updates are limited, and that the official version is only tested when it is on the store and has a version update;
26. When the user cancels the version update, the old version can be used normally, but the next time the app is launched, the update prompt still appears;
28. When there is a new version, do not delete the client, the direct update check whether the update is normal, and after the update of the client's functionality is the latest version (normally do not have to force the deletion of local clients can be updated normally;
30. When a cross-version update occurs, you can update the success. Performance test essentials and common defects

    Common performance-related flaws

32. Loading time is too long;
34. The application starts slowly for the first time;
36. The speed of entering an interface is slow;
38. Start an animated interface, the animation execution process is not smooth, or the animation execution lag time long;
40. Response to a user event for a long time without response;
42. After long-time operation, the phenomenon of Kaka appears randomly.
44. The server could not respond, reported HTTP500 error;
46. App appears black and white screen;
48. App crashes.
    Performance Test Essentials

Performance is also a measure of the quality of the app, if the load time is too long, the response time is too long, the user is not patient waiting, it is likely to uninstall the app directly

1. Is the app's startup time too long;
2. The consumption of CPU and memory when the app is used;
3. If the crash is more likely to be used in the app, it can be tested by buried point analysis;
4. Use of the power flow when the app is in use;
5. In the case of repeated long-term operation, the system uses the resource;
6. The response capability test verifies that the operation can meet the user's response request in various situations. User experience testing and common pitfalls

   To perceive the comfort, usefulness, ease of use and friendliness of a product or service in the perspective of a subjective, ordinary consumer. Through different individuals, independent space and non-empirical statistical multiplexing methods to effectively evaluate the product experience characteristics, proposed to improve product potential customer satisfaction. It is mainly tested in terms of ease of use and friendliness.
   

Common defects

Whether the interface display is beautiful, the color of the interface, whether the font size is suitable, the layout is beautiful, the prompt is friendly;
Whether buttons, dialogs, lists, and windows are in accordance with the user's usage habits;
Whether it is easy to navigate, whether navigation is intuitive, navigation is consistent with the style of the page structure, menu, and Connection page.
Defects in user experience classes

1. interface display is not beautiful, the interface color user use uncomfortable, interface color and buttons, other editing boxes, such as non-adjustment, the picture and font display layout (text surrounding the picture), the interface font does not meet the poor eyesight of the user, the menu is too deep, the relevant options are too far away, button is not clickable (if the button is not available, be sure to gray out, or take off the button, otherwise it will mislead the user);
2. long page load times, high demand on the mobile side, generally require no waiting interval loading, page load time is too long, will cause the user impatient wait and discard the app ;
3. page layout is too long, generally very few visitors are interested to see the bottom of the page, 90% of the users, open a page, only browse the content of the first screen, thought to see all, and not scroll down. A long page can easily cause the visual fatigue of the visitors;
4. unfriendly navigation, unfriendly navigation is the most impact on user operations, it is not easy for users to find what they think. Users come to a page do not know how to return to the previous page, do not know the current page is under which column. It is likely that users will not come again once, which is the reason for the emphasis on information architecture design, and navigation design is part of the information architecture. Users always have to reopen the app to find content, it is difficult to have users will be retained;
5. outdated information, long time not updated information, it is easy for visitors to feel disgusted, but also in the heart of your product brand image greatly discounted. Expired news, outdated promotional information, activity information are fatal;
6. dead link or link error;
7. lack of interactive content, lack of user participation, can not allow users to express feelings and ideas, destined for this product is just a product of its laurels. Now the most basic, all to provide a "feedback" of the entrance, so that the product of loyal users to express their views, and thus collect this part of feedback to improve the product. There are also interactive openings that will make the user feel that the product is relatively open,
8. malicious plug-ins, malicious pop-up windows,
9. prompt rude unfriendly. The test points and common defects of cross-events

   The method of service classification and real-time characteristics of intelligent terminal application. Cross-testing, also known as an event or conflict test, is a test in which a feature is executing while another event or operation interferes with the process. Such as: The app in front/background running state with the call, file download, music listening and other key applications such as interactive testing. Cross-event testing is important to identify potential performance issues in many applications.

Cross-cutting aspects of defects

The basic function of mobile phone is to use as a communication tool, so we will definitely have phone, SMS, Bluetooth, Alarm clock and other access in the app, and these features than the priority of the app, once at the same time, the app to run in the background or processing to make the basic function priority. In the test process will appear when the phone into the app crashes or stuck, the alarm clock sounded app hangs and so on, the app runs while the phone enters, the phone can not answer and so on. The problem is very serious, if the app caused the basic function of mobile phones can not be used, the user can not accept anyway.

Key points for cross-event testing

1. Whether multiple apps run at the same time affect normal function;
2. Does the app run in front/back switch affect normal function;
3. make/Receive phone calls while the app is running;
4. Send/Receive messages while the app is running;
5. Send/Receive mail while the app is running;
6. App Runtime Switch Network (2G, 3G, Wi-Fi);
7. Browse the network while the app is running;
8. Use Bluetooth to transmit/receive data while the app is running;
9. The app runs with your device using your camera, calculator, and more. User interface Test essentials and common defects

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

The goal of the UI test is to ensure that the user interface provides the user with the appropriate access or browsing capabilities by testing the functionality of the object. Ensure that the user interface complies with company or industry standards. Including user-friendly, humanized, easy to operate test.

Defects in user interface classes

• Not conforming to UI design or inconsistent with interface prototypes
  such as the application of a function of the interface style and the overall interface style inconsistent, or with pictures, text, buttons and other uncoordinated, such problems, although there is no use of problems, but users feel very bad, but also to users leave the research and development team is not professional or product rough impression, users will not use too long or directly uninstall.

• The interface is not fully displayed
  App because of the relatively simple function, but also give people an intuitive impression, so the image as the preferred use, especially in the home page for product display or important information transmission medium will often be used, but in the actual testing process will appear in the pages of incomplete loading situation, such as: Image display is not complete, button display disorder, Request the content of the new page successfully returned and the original interface content overlap, in the edit box input content too long, submit requests to the server to return data and other content overlap and so on.

• A page load error occurs when the pull-up refresh and the drop-down refresh
  Mobile client, content more than one page, pull load more content, loading errors (prone to duplication of data, pictures and articles do not match, picture repeated loading, article title and content inconsistencies, etc.)

  App test essentials and common bug subtotals, technology to change the life, the public to use the testing capacity of the masses and test resources, in a short period of time to complete a lot of work product testing tasks. And always from the user's point of view, the function of the product, ease of use, compatibility of the proposed improvement features. The survey is bound to play an invaluable role in the next mobile application development and testing.

App test essentials and common bug categories