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

Baidu search: Xiaoqiang Test Brand

Kick talk shows, entertain technology and systematize fragments, all in Litchi FM (http://www.lizhi.fm/200893)

1. Introduction

During this period of time, the hot topic is whether the company needs software test engineers, N how many cattle and company leaders have come forward to do their own defense, it can be seen that the position of test engineer has gradually become more familiar to more people.

At first, I was sure and did not deny that I hated those who said the test was bad and worthless, and I also participated in the debate on the Internet, but later, after reading an article on the main responsibility of Software testing written by Master Liu, I calmly thought about many issues, so today I want to analyze this argument again from a different point of view. I also hope to give more ideological guidance to IT leaders and colleagues.

2. My opinion

As I said before, there are basically pros and cons on the Internet. I will take a neutral view against the risk of being beaten this time, that is, it is neither positive nor negative. Why do I have such a view? I think it can be explained from the following two points:

Whether it is manual testing or automated testing, developers only need to spend some time and energy to conduct such tests. Before, a friend of mine worked in a company that did not have testers, and the developers were responsible for their own programs. If something goes wrong, you have to bear your own responsibility, so you can see that testing is not a necessary position.

As Master Liu cited the example of the physical examination to describe the test, it is very vivid. To put it simply, testing is like a doctor who has a physical examination, and the patient (product) is a problem. The doctor helps to check it out and inform it (test). But maybe you are a salesman, even if you know you have fatty liver, but in order to socialize, you have to continue to drink, who are you to blame?

On the whole, the quality of the product is the responsibility of everyone in the product team and does not belong to a certain group or role. The responsibility of testing is to be responsible for the testing work itself and to assume the quality responsibility of its own work, rather than the quality responsibility of the whole product.

So I remain neutral, and the value of the test is not determined by who, much less by the mouth, but requires our testers to take practical actions to bring real value to the upstream, downstream and the entire product line. this is the most powerful proof, but also the most meaningful.

3. How to make yourself more valuable

To get others to recognize you, you have to do something that can help others, especially for testing. What we often face in testing is product and development, so how can we show our value to both? I think we can start with the following points:

We often get caught up in the fun of finding bug in our tests. I can't say bad, but we must be moderate. It is our job to find bug, so we must do it conscientiously, not only describe it clearly, but also analyze it properly. For development, when looking for bug, we must locate bug as much as possible, and give analysis, so that we can not only make ourselves more in-depth understanding of the program, but also help developers save a lot of time.

At the same time, we only look for bug blindly, but forget the very important bug summary, that is, just like the case base, we should classify and summarize bug, give solutions and specifications to avoid repetition, which is the most meaningful part of bug knowledge base. For example, it is very effective to deduce according to the type of bug that appears, output development specification to constrain, and so on.

In the face of products, we can actually produce something more meaningful. We have been involved in the design, development, testing and launch of the product, and we have a greater say in the quality and characteristics of the product. We can collect the feedback and ideas of each member of the product, summarize and review to form a document and hand it over to the product staff, which can help the product staff to design and optimize the product, which is more meaningful to them.

4. Big ideas

We are often taught by our predecessors that testing is a meticulous job, but today I want to say that testing is also a rough job. Why? Very simply, testing is a link between the upstream and downstream of the whole R & D process, so we should not only understand the upstream and downstream of the product, but also have enough understanding of the whole business system and promote the research and development of the whole project and product at a certain height. I think this is the great value that a real test engineer can bring!

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.