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

As a developer, I missed the footpath children's shoes countless times after leaving a company in Langfang. Their testing professionalism and dedication made me once complain that you are so annoying. But what can be boasted is that at least the software is wet and stable, at least there has been no large and serious Bug.

Without testing children's shoes, how can we ensure that our Bug rate is not so proudly standing up?

In this paper, some auxiliary testing tools are sorted out and do their best.

Those testing tools.

With the development of the Internet, there are a wide range of testing tools. Here are the following three ways for reference.

I. Human flesh test

Human flesh testing is the most common situation in the industry.

Generally speaking, the developer needs to pass the self-test at least once before the software is released, and then give it to the tester.

The process of testing children's shoes that I have come into contact with is as follows:

Whether the submitted software business is complete and closed-loop

Details and whether the user-friendly handling is appropriate

What's the compatibility?

Of course, the actual situation is often more complicated than the above, and in some bad cases, submitting a bug will often get more bug after repair, challenging the tester's mental limit again and again. Silently love A Fan Children's shoes.

As one of the current general situations for small companies, the disadvantages are also full:

Compatibility cannot be tested completely

The complete closed loop of the business process and the trend of business exceptions cannot be tested in place.

It is difficult to develop children's shoes with Bug feedback. Once encountered an example, online feedback clicks are not in line with the actual situation, the specific click location is unknown, and the Bug description given is not consistent with the actual situation, which directly led me to test based on a customer's same equipment purchased for no reason in a certain Dongqi day. However, nothing was tested. In the end, Lao Han gave back a doubt and settled it in minutes.

The benchmark is different, the effect is different, the user experience is poor.

Okay. Human flesh test, ordinary and universal, thank you.

2. Monkey-stress testing

As a mobile developer, personal testing is essential, and stress testing is particularly important.

Recommend an artifact: Monkey, here intercepts the official description, and the official link is attached at the end of the article.

Monkey is a program that runs on an emulator or device that generates a stream of pseudorandom user events (such as clicks, touches, or gestures) as well as many system-level events.

In practice, we can stress test the current App through Monkey, and the test scope is as follows:

Basic configuration options, such as setting the number of events to try

Operation restrictions, such as limiting the test object to a single package

Event type and frequency

Debugging options.

Monkey generates events at run time and sends them to the system. It also monitors the system under test and looks for three special situations:

If you have restricted Monkey to running in one or more specific packages, it monitors attempts to move to any other package and blocks them

If the application crashes or receives any unhandled exceptions, Monkey stops and reports an error

If the application generates an "application unresponsive" error, Monkey stops and reports the error.

Let's do it in practice.

First of all, make sure that the current computer has an adb environment:

Partners who are not available can go directly to the local SDK storage address to find it, as shown in the following figure:

The basic syntax of Monkey is as follows:

$adb shell monkey [options] 1

Of course, you can also view it directly through the help command in use:

The most commonly used commands at work are as follows:

Adb shell monkey-p your.package.name-v 5001

Its function is to send 500 simulated events to the App with the specified package name.

Third, PerfDog performance Dog

When I first paid attention to Gouzi, the official website was still a page with some descriptions of Gouzi. The web page was very rough, but I was very interested in the content.

Before playing with dogs, you need to be based on the following two points:

Installed PC-end dog App

Has registered an official account to receive the newlyweds' gift bag.

Then we logged in and found that the current devices had been automatically detected for us, wired and wireless were on the list, very nice.

Then select the wired device. At this time, the Gouzi Android service will be installed on the phone, and you can choose to agree to install it:

After the installation is complete, basic information about the current device is displayed:

Then select the application to debug:

Open the application to be tested, select the upper right corner of PerfDog to record, and then start the operation of App. At this time, PerfDog starts to record all the data under the current operation:

After the execution of a process, click the upper right corner to pause recording and submit the data to the PerfDog platform:

Click the plus sign in the lower right corner to select more parameters:

The functions provided are relatively perfect.

Screenshot FPSCPU memory network power.

Let's do it on demand.

Click the small cloud ☁️ icon in the upper right corner of the PerfDog client to go to the PerfDog web page to view our test report.

FPS:

CPU:

Memory:

Network:

This is a personal knowledge blind area, this data will not be analyzed for the time being.

Briefly evaluate the feeling of personal use:

The existing functions are more comprehensive, and the cost of testing is low; although the test results are more comprehensive, the cost for novice analysis results is high, so I hope that more actual explanations or programs for the results can be more approachable; just provide some professional expositions involved, and the knowledge blind areas involved can be explained in the station without the need for user Google search.

IV. Automated compatibility testing on WeTest platform

This piece is also stumbled upon by checking PerfDog. Test a version that is already online to see how compatible it is.

Then select the model, here you can use the default recommendation, and then click on the security scan.

The newlyweds' gift package gives some experience qualifications:

Successful submission, waiting for good news ~

About twenty minutes, the test is complete, and you will be notified by email.

Let's look at the report together.

1. Equipment pass rate: 80.0%

The problem model is mainly below 6.0. this project is wild with minimum compatibility of Android 6.0.

two。 Question list

The reason for installation failure mentioned above is minimum compatibility with Android 6.0. Here, let's take a look at the process exit.

Screenshots will not be released because of the project nature, and interested partners can download the experience in the major application markets and launch bug at any time.

The consumption of traffic is a little distressing. It still needs continuous optimization.

This section is rich in content, with relevant screenshots, Log, abnormal device models and so on, which is worth experiencing.

3. Installation package check

Click on the corresponding item, in which the suggestion is quite detailed.

The rest needs to be discovered by the buddies themselves.

Reference UI/Application Exerciser MonkeyPerfDog performance Dog WeTest from: https://blog.csdn.net/u012400885/article/details/104654592

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.