Android Application Testing: solution Summary (1)

Android Application Testing: solution Summary (1)

BKJIA: Checking apps on Android or iOS platforms is not as special as you may think. The goal of our work is the same, the expected results are the same, and the operation process is the same. Compared with the desktop platform, the main difference in mobile app testing is that we need to pay more attention to the details, which is the focus of this article.

1. Basic Principles

Before in-depth discussion, let's first talk about some basic principles of testing. Unless you have a thorough understanding of and are familiar with the entire testing system, it helps you quickly identify the solutions you have.

Challenges on Android

What really favored Android is its countless possibilities. In the iOS camp, we can only think of iPhone, iPad, and iPod Touch. They have different styles, but have the pixel density, screen resolution, processor speed, and memory size common to iOS devices.

However, on the Android side, the same appearance size, screen resolution and size, processor speed, and memory capacity can be used to build countless combinations-and what "icing on the cake" is, the fragmentation of operating system versions makes all this more complicated.

Speaking of the operating system version, it is not uncommon for operators and mobile phone manufacturers to stop providing version updates for their products soon after the launch. Isn't that a problem? Of course. If you are interested, click here to view the official Android Market Share statistics provided by Google to learn how serious this problem is.

Among the projects with reduced market share, we see jelly bean 4.1 to 4.3), ginger pie 2.3) and ice cream sandwich 4.0.

In contrast, Apple iOS 7 has a much better acceptance ratio. As of the end of, of iOS devices have been running iOS 7. We need to remind you that iOS 7 was officially released in last September. The performance of the two products is similar to that of Alibaba Cloud.

Learning, comparison and reference

I wonder if you have really experienced poor Android applications? Compared with applications that are useless from beginning to end, what's worse is the garbage that is filled with countless vulnerabilities that make people unable to figure out the results.

Based on my personal experience, to make the test process smoother and more effective, everyone's focus is very important-including what we use, what we like, and what we hate. Although it seems a little too strong to hate this word, I am sure you have experienced this experience during use.

Please answer the following questions objectively:

• What are your favorite applications? Why do they get your affirmation?
• What bad applications have you ever experienced?
• What makes an application outstanding? Have they noticed the details during the development process?
• Do bad applications often get stuck during running? Will it crash? Or is there a problem with the design idea?

Know which Android devices you want to deal

Let's go back to the Android operating system market share reference chart. It can be seen that testing every device and every Android version is simply a dream and not necessary.

In my opinion, we need to consider the specific release requirements. What are our applications and target markets? Is this a game or a utility application?

If this is a game, the focus may be on updating and higher-end device knowledge. However, for utility applications, You need to attract a wider audience and support a larger number of device types.