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

one

In fact, at the beginning of this article, the title was "how to clean up a dusty station with a rag at a time." I felt a little twisted over and over again, but in the end, I also found that, wow, this rag is so miserable. I changed the title to "tragedy caused by a rag" and felt that it was suspected of the title party, so I finally decided on the current title.

To get back to the point, I don't know if there is any leverage in the students who read here, and if they do the test, I'm sure there is. anyway, let me explain first. This is mainly about the topic of testing strategy, such as how to find the Bug with high severity as soon as possible. Some people will say, what does this have to do with rags? Don't worry, keep looking.

two

I have always felt that testing is not just a technical output type of work, sometimes giving full play to soft skills will get twice the result with half the effort.

With regard to the question of "how to clean up a dusty workstation with a rag at a time", we can imagine that dusty workstations must be dirty. in addition to desktops, there are also computer monitors, mainframes, cabinets and so on that need to be cleaned.

If we use a dishcloth, we will find that the dishcloth has to be washed before the table is finished, so if we want to clean it at once, we need this dishcloth to wipe it a few more times. so how can we wipe a rag as many times as possible?

The (male) students who often do housework are more experienced at this time. I can wipe the front and the back again.

Right, so the premise is that you can't start wiping with a rag, but you have to spread it flat and use one side of the rules first, so you can use it at least twice, but twice is not necessarily enough. What should we do? How to make a rag with only two sides come out with multiple regular faces?

It may have occurred to someone to fold the rag in half.

You see, after one fold, there are four faces, two folds is eight faces, a rag is wiped eight times and once, this contrast effect is still quite big.

Ahem, another lever essence came: "in theory, it can be eight times, but in fact it is already very dirty, and the effect is getting worse and worse." "

Well, of course, so in addition to folding, we also need to plan the priority of wiping. For example, monitors, which are difficult to wipe and valuable items, can be scrubbed first, and the desktop will be left until the end, so that although the later effect will be poor, but it is also acceptable.

All right, a rag. After all we've said, do you feel miserable? In fact, what I mainly want to say is that a reasonable adjustment of the testing strategy can make the test execution get twice the result with half the effort.

three

Look, the rag finally has something to do with the test, but let's give an example of the test and explain it in detail.

For example, there is a project that has written 100 use cases, and now you need to help with the test execution of the first round of coverage. generally speaking, you only need to execute the use cases from top to bottom and from front to back. however, it is possible that when you run to the 80th use case, you suddenly find a P1 Bug, and then you make trouble and location, and it is found that it is a problem with the technical architecture. If you modify it, all the previous work will be wasted.

Based on the previous rag tragedy, we can imagine that if the executive has some knowledge of the testing strategy, his first reaction to the use case is not to execute it immediately, but to look at the key modification points involved in the requirements first, then look at the correspondence between the use cases and requirements, and reorder all P1 + P0 use cases in the order of the key requirements. And prioritize the priority use cases of P1 + P0 in this order, so that you may be able to identify this potential P1-level Bug in the first place.

Of course, the requirement for the executive is relatively high, so let's imagine again that if the project leader in charge of the project, when assigning tasks, told which part of the function was more important, and marked all the use cases in order of priority, and specifically required that the high-priority use cases should be executed first, as long as the executive could understand. The Bug of P1 can also be found as early as possible.

Then some students said that we must give priority to the use cases at P1 level. This example is not appropriate. Well, P2 cases can also be done this way. Of course, P2 use cases are generally more, so the strategy can continue to be optimized. For example, if two people execute, one executes from top to bottom and the other executes from bottom to top. If there are more than one person, each person can divide the scope of his own priority execution. You are responsible for the execution of the part and then cover the other parts.

The general principle is that use cases of high importance should be covered first and complete the first full coverage as early as possible.

four

Well, this is what suddenly occurred to me when I was cleaning the station in the morning. Haha, isn't it a little big? Do you think it makes sense? Welcome to leave a message for discussion.

This article is originally published on the official account "sylan215", ten years to test the original practical information of veterans, follow me, rise posture!

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.