[Software testing] software testing is about finding bugs, not looking for bugs.

Two days ago, I chatted with a new friend.

"Are you a codenon ?"

I'm so angry. Is my image like this? Like? I really want to beat him.

"No, I did a software test, and I didn't use that much code, so I couldn't name it"

"Oh! Then you are trying to pick up the problem. What are you looking ?"

At that time, I decided that this friend had gone over to you.

"I did a test, but I was looking for a defect, not a fault. Thank you for your patience. Please be busy first. Goodbye"

After I go home, I want to share with you:

First:

The test is to find a bug, not a fault. In the past, we used to conduct tests in outsourcing mode. We were faced with PM, and the so-called customer was the developer of software development. In addition, because we were far away from the developer, communication was basically done by email, so there were not many feelings at the time, but they just did their jobs well, found more problems as much as possible, and made the problems they found more valuable as much as possible, try to make the problems you have discovered so that development can be completely reproduced! Now I joined a company that made my own products, and all the people I faced were changed. I used to think that I was facing development and now I understand that I am working in a company that made products, we must not only face development, but also products, designs, and real-use customers! In the past, I always heard that testing and development are the opposite thing, and it is difficult to communicate. I also read a lot of questions about communication between development and testing. In fact, there is nothing wrong with it, the ultimate goal is the same for everyone. It is to make the project better, test the project better, and develop the project better! Just like an article I read two days ago, I said that development is actually the same as testing, because they are the people who actually implement the product, who doesn't want to do anything as perfect as possible? Why is there a gap between development and testing? The reason is that developers want the test to be able to identify critical and critical bugs in the first time. What about testing itself? Every problem you see will be reported in a timely manner, but it is only divided into priority levels, but development does not look at these so-called priority levels, so you will think that it is not good to find a major bug, in fact, every role has to understand each other and solve the problem. Since the goal is the same, why do we have to struggle with this order? Developers should not think that testers are deliberately looking for faults. The problems they have raised should be all defects, but you can determine the priority of the handling, do not think that developers have opinions on themselves. When submitting bugs, it is best to pick out major bugs and develop them by vibrating them, and then report the less important issues together, this not only demonstrates the value of testing, but also gives developers a different view and greatly improves the testing status! Always remember that we are looking for bugs, not bugs!

Second:

Testing only improves product quality, rather than ensuring product quality. I remember my first contact with the test. In class, my mentor told me, "We test to improve quality, not to ensure quality ." Many people who do not quite understand the test will have a misunderstanding. What do they think is the purpose of the test? Since we spent money on you, we should ensure that our products are not defective! For such a person, I can only say that it is irrational. It is not that I shirk responsibility as a tester, but that there is nothing in the world, what we can do is to do our best to improve, find the most problems, and solve them accordingly. testing is not omnipotent. If someone says that my testing can ensure the quality of your products, I can only say that you have been fooled. We only improve the product quality, not to ensure the product quality!

Third:

Testing requires participation by all people, not just for test engineers. Some people think that there are testers, so they are not very concerned about the product. In fact, testing is a matter for everyone, including customers, because a person is meticulous and has no comprehensive eyes. I forgot which company's boss has always advocated the testing consciousness of the whole people. I think it is awesome because every employee is a member, each product is not only the company's image, but also the embodiment of each of us, but our division of labor is different, but it represents us, in addition, I think such a management concept can also have the power to unite people, so that everyone can do things better together! Instead of relying solely on testing, we finally become more and more lazy. I found that the current company has such a phenomenon. Developers sometimes have a dependency mentality that there is a test anyway? I am not so serious about the programs I have written, and I am not very serious about checking the programs I have done. It is a bug to take the programs away. In the end, the development and testing are both headaches. Therefore, the company should encourage this kind of consciousness from the root. testing is not only a task of testing engineers, but also an important task that requires participation by all people!

These are my thoughts, which may be a bit broken or biased. They are for your reference only, but I still hope to change some people's ideas.

I have some software testing materials here. For entry-level information, please leave a comment. I will send the online storage address in the comment.

If you feel familiar with the content, please comment on it.

[Software testing] software testing is about finding bugs, not looking for bugs.