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

When I saw a blog post on 51testing in the morning, I thought it was well written and could be used as a self-evaluation and a reference for the company's evaluation testers. Source: http://www.51testing.com/html/31/n-863431.html here I also talk about some of their own ideas, but also by the way to complain for the testers.

As a matter of fact, testing is a thankless role. At present, individuals still feel that it is a bit of a "pit". Very often, we are "trapped" for no reason. We can be trapped, but we cannot be buried. We have to have the ability to climb out. How did this ability come from? Let's give it a try in view of the following situations:

The missed detection rate is very high.

In such a situation, we need to reflect on ourselves, and your ability has something to do with it. At this time, we need you to think about why it was missed and that the analysis was not done. Case is not well written? Did you ignore it when performing case? Or some other reason, find the crux of the problem, then you should always remind yourself

The demand is not clear, but the customer insists that it is a product issue

In fact, in such a situation, the responsibility should not be yours, and you don't have to care too much about it. If you often encounter such things, you can take the initiative. I think you more or less know where the needs are unknown. You are also aware of some potential problems, but you are too lazy to ask. You can confirm positively. I just hope there is no fault if you do not pursue outstanding contributions, unless it is very unreasonable. Otherwise, I think they will see your enthusiasm. Normal people will not reject enthusiastic and responsible people thousands of miles away.

Developers hate issue, or care about quantity.

In such a situation, you can be more round. You have to learn to observe words and expressions. Don't try so hard. Even if what you find is indeed a problem, try to avoid arguing. You can explain issue to him by asking for advice. For example: I have a problem. Do you think my test method is wrong? Or, I need your support, please correct what is wrong. In this way, you not only express your problem, but also let him understand what the problem is, and you will not be rejected in general when you communicate in a consulting manner. For those who are very concerned about the number of issue, you should be careful. If that person is not capable, you don't have to carry it for him all the time. You can say privately that if the character is very stubborn, you bear it, and the result of private communication is still the same, you'd better report it truthfully, and there will be times when you can't bear it.

The test is not sure.

Yes, it proves that he writes well and of high quality. Why didn't you test it when he was wrong? Anyway, the credit is his, the responsibility is yours, what you need to do is to affirm your own contribution, of course, also affirm his ability, look down on the gains and losses, people are doing, heaven is watching, not only one mouth can speak.

It's almost "Sen."

Almost, as a test, you must not specify that right is right, wrong is wrong, vague, or confirm first, it is best to reach an agreement, and then turn it into right or wrong. Or make it clear and list the Assumption clearly.

Life is a kind of toss, don't live so hard!

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.