Focus on mobile app development and testing

Recently, the company wants to set up a mobile phone testing department to summarize its three-year experience in mobile phone development. It is a sporadic Trojan Horse with regulations and hopes to help. If you have other good ideas, you can leave a message and communicate with each other.

As a restricted device, mobile phones have limited screen size, limited computing power, and limited power supply. Mobile phoneProgramCompared with conventional PC programs, you need to consider the appeal from three limited perspectives during testing.

I. Limited screen size

1. The screen size is different, and the resolution is also different. It should be ensured that the screen can be completely displayed on various mobile phones, buttons are not allowed, and the list is exposed to the screen, which may affect user usage.
2. The option cannot exceed 1 screen, and a maximum of 1.5 screens can be selected. If there are too many options, you should consider the steps to make them look like a wizard. Too many options will cause users to stop using them and cause errors easily. This disadvantage is even greater for mobile phones that are inconvenient to input.
3. There are not more than 10 drop-down lists on the mobile phone interface, because too many drop-down lists are difficult to select, and the performance requirements are too high. In the past, I used to create a WAP website. The drop-down list contains more than 100 million items, and the normal Nokia mobile phone crashes. The iPhone can be pulled down, but it is inconvenient to choose from.
4. On the input box page, consider whether the pop-up keyboard will cover the following input box, and whether it will affect user input and next operations.
5. Whether the button position on the interface is reasonable or not. The operator does not meet the user's habits. In particular, some small button users cannot touch or are not easy to touch.
6. We recommend that you use the filtering method for the list of more than 20 items in the project. You can search for and select the best user experience.

Ii. Limited computing capability

1. During the test, pay attention to whether the system will crash when loading large images. When many programs re-write, they do not consider the phone memory ceiling. The 4 m high-resolution images are directly loaded to the memory without being scaled to the file, and the system will crash. Large XML files cannot be loaded using Dom.
2. For a test that queries the list, you need to test whether the system chooses to load by page or directly load all the results to the interface when more than 20 results are returned. If it is directly loaded to the interface, when the return entry exceeds a certain limit, the mobile phone program must also crash.
3. When developing a mobile phone program, you must consider exception handling when the memory is full. You can enable the multi-point program on your mobile phone first, then open our program, and perform some memory-consuming operations (such as opening the camera and scaling images) let's see how the program handles memory exceptions, and whether the program will crash or become inexplicable.
4. If the content displayed on the phone details page exceeds one screen, and the memory does not have any special operations, you can splice the memory into HTML and load it with webview. These two advantages: one is that you can customize the style very beautiful, and the other is that webview will help us deal with page turning, scrolling, image processing and other operations, the memory used by this program is also a saving.
5. For poll operations, writeCodeWhen using while (0), but the loop body must sleep to release the CPU chip, or the CPU of the mobile phone will be very high, the phone will be very hot.
6. The mobile phone network is not a stable network. We recommend that you use offline and mobile networks to run one side during the test. Do not use WiFi for testing. In this way, network exception handling cannot be detected. For all network-related operations, retry at least two sides on the phone to ensure its availability.

Iii. Limited Power Supply

1. The basic cache data of Mobile Phone development is loaded into the memory, which reduces the disk I/O operations and saves the power required for the drive SD card. For power-consuming devices such as GPS and WiFi, you need to use a program to disable them.
2. If the network communication is cyclical, the less recommended content, the better, the better. The interval should not be less than one minute. If the real-time requirement is not high, we recommend that you use it once every 15 minutes.
3. The special requirements of mobile phone program fees generally do not significantly increase system power consumption. During the test, you can try to change the program for an hour to see how much power is reduced. It cannot exceed 10%. Another effective method is to test the program for 1-2 hours and find that the cell phone battery is very hot (multiple mobile phones are hot), which indicates that the system design is faulty. If you use too many resources, you need to make a more general analysis.

The most fundamental principle for mobile phone testing is availability. For example, random operations cannot crash and are easy to use. Users cannot input anything they can choose. Treat users as dummies and do not let users think too much. Currently, no user is willing to see the operation manual. In addition, companies have more programs than specialized APN programs. Therefore, you need to switch through specialized APN to access the Intranet. I recently read several programs and found that many Access Point switches are incorrect and cannot be accessed normally. the most unreliable thing is to switch to the dedicated APN when the program enters, but do not switch back when exiting. The user can no longer access the Internet after exiting our program. The consequence is that our program destroys the availability of the system, which is a very serious bug.