I originally wanted to add a new topic to my article, but thinking about it, it seems that there is no more appropriate word than "win in the test". It has been more than three years since I worked today, from development, BA to testing, and now to test management, I have experienced a lot, and have a lot of thoughts on testing.
Someone once asked me how to learn testing techniques? Specialized or broad?
To use an inappropriate analogy, testing is like digging a well in a dry land to find water. So is it better to keep digging in one place and never give up, or to try it in many places? I think there should be an intermediate state between the specialty and the wide, that is, try to dig a few meters in many places, and dig deeply in some places where there is hope that there will be water. Going back to testing, the technology should be more extensive. Functional testing, white-box testing, automated testing, performance testing, security testing, etc. should all be covered, including database technology and UI technology. , java , python , and framework algorithms should be learned as much as possible, but choose the areas that you are interested in or are best at and delve into. A wide range of knowledge and professional skills are more in line with the development of the test.
Reading the trial chapter, I really like a passage from senior Zheng Wenqiang: "I have been working in the testing industry for more than 11 years, and I feel that I am gaining a deeper understanding of the connotation of testing, and I am more willing to regard the current state as one that surpasses myself. Starting point. Persist in doing the work you like, keep accumulating, summarizing and sharing, I believe everyone can become an expert in the field.”
For the test work, especially for the fresh professionals who are new to the industry, it is always more confusing than longing. Of course, this is also due to the current overall atmosphere of domestic IT , and testing has not received enough attention in small and medium-sized enterprises. I also believe that with the continuous development of the IT industry, this atmosphere will gradually change.
Just a digression, then back to our testing discussion. I've summed up the "five taboos" of testing in the past like this:
Avoid "slightly tasted and stop", avoid "know the truth, but don't know why", avoid "so lofty goals", avoid "anxious to eat hot tofu" and avoid "hidden secrets".
The so-called "slightly tasted and stopped" refers to the attitude of encountering difficulties. In the process of learning, it is inevitable to encounter some difficulties or even difficult problems to solve. What should I do? First, think more, think independently to solve problems, and then ask diligently, if you can’t figure it out, you will ask the experienced people around you. Much of the experience, thought, and gain comes from the lessons of failure.
"Know it, don't know why" was a big taboo in my evaluation of security testing. Because the current security awareness of developers is not strong enough, when you propose that your code has SQL injection vulnerabilities, XSS vulnerabilities, etc., the development may not be able to deal with it correctly. At this time, you need to know the principle of the vulnerability and some simple prevention methods. to give some guidance. In fact, this idea can also be extended to the whole test learning. "Knowing why" will undoubtedly improve your own ability at the greatest speed.
"To be too ambitious", this is a common problem of most people, and I have had it too. When I have a little achievement, I feel a little carried away, I feel that I have learned to be a teacher, and I can stand at the top of the industry. Of course, this statement is a bit extreme, but many people have similar ideas. For example, "don't tell me such basic things, I understand", do you really understand? Confucius said : I should examine myself for three days.
"I want to eat hot tofu in a hurry" is a bit funny to say, but it exists in many cases. For example, someone wants to learn automated testing, so the master will start to teach him some framework ideas, programming basics, and so on. The person will occasionally complain and say, "I just want to learn automation, why do I say so much useless" and so on. Well, down-to-earth learning, not much to say.
The last is "secret". Many people don't like to share, and feel as if they are at a loss by sharing their own things. Let’s use a sentence from the trial reading chapter: “Sharing will not lead to teaching the apprentice and starving the master to death, because learning is a process. On the other hand, colleagues will also thank and respect you for your sharing.”
I have written a lot of this, but it is nothing more than my own thoughts and insights about the test. Of course, the qualifications are still shallow, if there is anything inappropriate, please correct me.