"Industry Exchange" TID quality competitiveness Conference--the road of mobile Internet testing to quality change

TID quality Conference held in Beijing, had the honor to participate in two games, are very well received, the following to share the content of the Conference, as well as some of their own simple ideas to write down, hoping to help some people more or less.

The first to participate in is Monkey "mobile Internet testing to the quality of the road of Change", into this line should know Monkey bar, I will not more wordy, below to see the real person:

Monkey on his self-introduction:

Here are some of the issues that I believe will be faced by both large and small companies:

And one of the most critical of these is:

　　　　How do you guarantee the quality of your business in such a short test time in an Internet product that iterates so fast?

This question is not in a hurry to answer, first of all, we look at the following a more intuitive expectation:

The first mentioned is the person, the tester, and we look at what the testers expect:

The first is testing technology:

See this picture very agree, we can see pyramid spire is so-called "tall on" test development technology, now the whole industry is too impetuous, are too much fancy testers of technology, this will make us out of our nature, we are test engineers, But the concept of testing theory and understanding of the increasingly weak, if the entire industry has been the case, then we test the industry will be very dangerous, and really one day may be called Test development (developer) or operational testing (operator) to replace, So here we must pay attention to the test itself some theoretical knowledge.

Then is the skill, here write more intuitive, say a mouth is the location of the problem, take an example, when we in the test process if you find an interface list sliding special, this time to submit a bug, development is very easy to call you back, because this is a subjective thing, This problem is very likely to develop will say here is not the card ah, and then the bug to you kicked back, so kick to kick no meaning, we need to do is, it is best to directly locate the problem, and then reported to the development, so I believe that development will not be easy for you to kick back.

Business quality accounted for 60% of the KPI, you can see the quality of the business is we have to ensure that, I want to talk about technology upgrading, here is not to say that you learned what technology, but you learned which technology after landing to your project, and achieved a certain effect, do not purely to enhance their own self-hi , and this is not the hope of the Test team.

The last one is the recruitment of personnel, this I did not recruit, no voice, with monkey words is you will what is not important, the most low interviewer is to use their own good things to examine others, no meaning, recruiters should pay attention to the candidate learning ability, the way to learn, and look at the height of the problem.

Monkey said he had previously communicated with a company's Test manager, and the test manager told him that our automation, the special project has done well, and also put a lot of manpower, why do we still feel a little bit of quality in the whole test? In fact, these so-called automation, special in the entire product process is a relatively downstream things, and grasp the upstream, we need to stand in the height of the quality to look at the problem, this picture some do not see clearly, and so on, I will replace a clear picture, here is we need to focus on some of the quality of the details of the part.

The next thing to say is something downstream:

Here is a description of the three points it mentions:

1. Client UI Automation is only available for smoke and regression

2, the backend API, interface needs to overwrite

3, when the need to do similar scanning to pay such power consumption, often with automation together to complete

This is really not like some blowing said that our automation coverage of more than 90%, a listen is bragging. One of the things that comes up here is that the drop of a product, involving the driver and the passenger side, may require an automated tool for the communication between the frame and the frame.

Special test, here he suggested that the special test to recruit some experienced people, because the students do business test most of the time is to know the expected results and then compared with the actual results, and the special test in a power consumption indicators, he did not know whether this indicator is good or bad, this time need to use empirical values to judge, In addition is weak network simulation 2G time, exactly up and down line and jitter, delay this setting how much, these need to have experienced people to do.

Here's a list of things to consider when testing the network:

Next is the quality market:

This is more interesting,

First of all, what is this? This is a scoring assessment of the quality of each module.

Why should these modules be evaluated? Because some scenarios (such as page start-up time), the data measured by testers in the test environment are often inconsistent with data from real users on the line and cannot be judged to have an impact on the online user.

In what way? Through the burial point, in the gray time evaluation.

How to bury it? What's the difference between a normal burial point? First they divided the business code into three layers, the underlying framework layer, buried the ordinary events, followed by the component layer, buried such as network-related, see the network delay, the top layer of the business level buried start time and so on. After the big data is obtained, a cleaning is performed on the data, and then a graded value is obtained by a complex formula.

Project Flow comparison cleaning, nothing to say.

The evolution of the platform is more interesting:

Before is the tool group to make the business group the tool, the business group always complains that the tool group's thing does not connect the atmosphere, and is difficult to use, the tool group classmate under the KPI pressure, unceasingly develops the new demand, but does not revise some bugs, thus causes each other to complain. After the revision, the tool group only provides the underlying services, and the students of the business use the capabilities provided by the tool group to develop what is appropriate for their business. It reminds me of the little squirrel and the GT.

Finally back to the original question, and the answer? It is:

The world of Chu Gate.

　　

"Industry Exchange" TID quality competitiveness Conference--the road of mobile Internet testing to quality change