Mobile Application Specific Testing

The special test has the resources class performance, the interaction class performance, the stability, the compatibility and the security and so on. But think about it, for a small team, a start-up or start-up team need to tube so much? No, as long as the mind has a concept, and the corresponding guarantee measures can be. For small teams, the more important thing is to hit the pain point, because the pain point is the biggest obstacle to product development, with a very high cost-effective. But what is the pain point? Many products on the surface know their own pain points, in fact, it is not so. In the case of not understanding user feedback, say that they understand the user's pain points, and create product requirements abound. So for the special test, the first step is undoubtedly to find the pain point.

The first step is to build a feedback system to find the pain point. This feedback includes a variety of user feedback collection and analysis, a variety of special data on the front and back end of the escalation analysis. There are some such as listening to the cloud, oneapm,bugly actually have some of the ability to monitor the escalation, but unfortunately in the user feedback collection and analysis, the corresponding system has not been seen. Therefore, the application of existing systems may also need to be self-built. So, if you have these systems, to help us know how many users encounter the card dead, the actual crash rate is how much, how many users said the consumption of traffic, the actual terminal consumed by the flow report results. At this point, the pain points naturally at a glance, the future can achieve the goal is clearly visible, the boss may be more clearly understand the seriousness of the problem, and thus determined to improve.

The second step is to find the bottom line and target. We have a feedback system, we know the user's actual situation, then we need to base on the data to let the team clear the bottom line and the target, so as to improve the efficiency of the follow-up team cooperation. The goal can be, crash rate is how much does not let release, crash rate is how much can not fix, switch interface bottom line is how much, percent of user's smoothness is how much, user feedback of the lag problem from TOP10 problem culling and so on.

The third step is to solve the problem. There are pain points to solve the pain point of the goal, we will act, in order to achieve the goal, solve the problem. We and our platforms need to have the following three capabilities:

The fourth step is to return to the feedback system and show the effect. Development, testing busy for a long time, reached the effect, but did not show that is missing the development and testing to form a trust relationship closed loop of the best opportunity. Of course, there is also a lack of further improvement, the opportunity to do fine. As we upload pictures, the first goal is only to improve the success rate, and then is to let the bandwidth good transmission speed, and then is to let the network poor can also be on the basis of success to ensure that faster, and then find ways to save more in the concert when the message and pictures of users, along the way are constantly looking at data reporting, analysis, Solve problems, show effect, analyze again, solve again, show effect, form closed loop.

Tool article

In general, the most painful specific issues for users are usually the most superficial and intuitive issues, including:
Flash back: Including crash, System strong kill, ANR, directly affect the user's use.
Lag: Including dropped frames, low animation frame rate, the corresponding user operation speed is slow, even the card is dead, but did not trigger the ANR or watchdog timeout. These feelings to the user is used very uncomfortable, especially when there is a contrast.

High traffic/slow speed: Mobile applications are bound to face traffic problems, so far we will see the end of the flow effect, we know the importance of this. Moreover, for small companies, the more painful may be the bandwidth, the cost of CDN.

Weak network compatibility Poor: the user-oriented network situation is actually good and bad, but users expect the business to execute successfully, even more time-consuming.

Short standby time/mobile phone hot: From the beginning of the iphone, each phone needs to "hang brine" (using mobile power). If he found you in the power consumption ranking TOP1, but has been in the background of no achievements, I believe users will not hesitate to delete.

Business specific issues: different products have different business specific issues, said alone because the front 4 is universal, please do not limit their own thinking. According to the business characteristics there are some specific indicators will be generated, such as the accuracy of map application positioning, advertising ability to push the accuracy of the music software to play the sound quality, image application of the image.

For these questions, let's look at what tools we have to help us. There is no resource input like bat, but the problem has to be solved. Below the small V to recommend some of our internal construction ideas similar to the external open source tools to help you solve the problem. (PS: I only recommend that I think landing cost low output the highest tool for everyone, so some tools I do not know, but the problem of input. And below I no longer say specific indicators, I would say is the pain point, because the special indicators certainly not only these. The following content I try to be objective, but do not rule out some subjective judgments, after all, I do not use each in depth. ）

Android

Ios

General

Mobile Application Specific Testing