Little feeling
I suddenly started the role of this role: To introduce you to the role positioning of a tester, as well as questions and mentality issues that need to be understood. To be honest, it feels very difficult. Sometimes some things feel that it is not very difficult, but it is really difficult to transform it into the form of text. But I am still very willing to use a pen to slowly describe an understanding of my testers' positioning: When a person walks on a long and bumpy road, I believe he will have something you will settle down. . When I got the East China Test Exchange Conference, I heard how to be very deep when I heard how to locate my role. I feel that I still have a lot of people worthy of drilling. In the field of test, my awareness is still very beautiful. . As the company has gradually expanded, testers have also developed from the previous few people to dozens of people. The growth of the team is obvious. However, many colleagues who have just entered the door have begun to slow down to test the confused eyes, asking the reason, very simple, doing testing, doing things, doing the mouse point, keyboard knocking, it is difficult to learn real thing. After listening to it, I couldn't help but smile, I thought I was coming from such a situation. When you just entered the company, let tests, experienced the same mouse point, keyboard knocking on the experience. However, some of these growth experiences let me understand a lot of truth in their plain, and slowly do testing from work and continue to do test work because of interested hobbies. Doing testing is not only the continuation of this knocking point-knockpoint phenomenon, but also a deeper connotation, but many of us have not reached this realm, so it looks very boring. (I didn't reach this realm, but I know that my work is not very boring, huh, huh). Many friends who have just started testing are doing black box testing, and black box testing often requires the ability to write capacity to code, so that people who have just entered the door have caused a tester to misunderstand the misunderstanding of too many knowledge. However, doing testing often requires a wide range of knowledge. Not only is it just a professional, and I have to understand what many developers don't understand. Developers in a system can only understand customer needs, and our testers need to understand the entire overall situation. Oh, it feels a bit of a sense of accomplishment. However, sometimes it is true that it is true relative to developers. Developers don't have to understand the needs of users, but we need to accurately capture users, pay attention to a lot of details. Many people are often passionate about testing tools and use when they first enter the test industry, in fact, this is not a very systematic cognition. The learning of knowledge is also a phased. Testing these two words are very simple, just give the program to pick the mistake, find BUG, but how we should effectively perform the test and development in the entire software development process requires practice to prove. And these are not the tools you can do. We need a lot of things on the entire test process, and tools just need some of them and is a small part of knowledge. What you know is not only the surface of the test, you need to understand the process of testing, you need to know how to use a good test plan to plan our test time, test scope (some companies put the test range design inside the test demand However, many companies are in the test plan), you need to know how to use a good test case to overwrite test implementation within the entire test range. Learn how to ensure that the bug tested is the problem of developers rather than because you know the problem. How to summarize the problem within the BUG analysis report is the knowledge we need to notice. Detailed planning is also required for your test time, as much as possible. This can minimize relevant risks as much as possible. 2. How to perform software testing? Knowledge learning inside can be divided into the following three stages (this stage is just a personal opinion):
In the first stage, we must let the people who do tests understand the importance of the entire software engineering, understand the basic knowledge of the test, and gradually explore his interest in testing in the process of understanding these knowledge. Interest is a very good important condition for working. Let a person who doesn't understand the test and is not interested, do you think is it in the youth of others? In the second phase, we must have a very clear understanding of the management of the process of testing. Because many times work is carried out in the case of teams coordinated, they need to be familiar with the test flow in the entire software development process and the development process, so that you can work better. When we are very familiar and is very smooth in work, we can learn more about test tools. It is true that many companies always ask for the automation test tool when recruiting testers, in fact, many companies do not really use automation tests. So don't go to the door, I want to learn the automated test tool, and many knowledge can be better after you understand other knowledge. While understanding the test-related procedures, we must expand our other related knowledge, including the needs of our customers' needs to understand more comprehensive and deeper than developers. In this way, we can guarantee our processes, our tests are advanced in accordance with the objective correct direction, not to be pulled by the developer's thoughts. Ha ha. I like to do things active instead of being executed. To the third stage we can take your favorite ways like yourself: On the one hand, we can continue to improve our testing professional skills and can truly engage in automation tests, becoming experts inside the technical field. On the other hand, we can slowly tend to test management. At the last meeting, Haisong's big brother had made a very image of the development path plan for the development phase of the testers. I painted a rough process. You can look at the development map below: (from bottom to Development trend) (of course, everyone is not within this curve)
Figure 1-1 Test staff development map: The length of the line can be roughly outlined for different times. From this graph, we can also see roughly, for primary test engineers, this is two different development directions, but In the end, it is also developed into a end point (PM). From a primary test engineer to a senior test engineer faster, it is relatively long from an initial test engineer to a Team Leader. From a senior test engineer to a senior test engineer spending a longer time, it can be easily tested after arriving at the senior test engineer, and it can be developed to PM. Of course, from primary testers to advanced and senior testers are not expressly expressing "curve development process", many times, the accumulation of industry knowledge is important. This will only find its importance. Many years of increasing experience, some precipitation is not manifested on literal, others can understand and comprehension. Therefore, we must have a confidence, we must have patience, Rome is not built in a day. I believe that tomorrow will be tightly grasp today. 3. I think the basic quality of the test personnel should have a few people feel uncomfortable when testing, which may be not interested in testing. (Recommended to contact the friend who is not interested in finding his own reasons, I can't find another well-developed industry.). Because the knowledge hierarchy is not enough, this often feels that the bug you find is not very good at developers, and I feel that my labor results have not been respectful. A tester often produces such a phenomenon when he is dealing with the developer. As the development is carried out, the bug submitted by the tester is increasingly not being attached to the developers. In addition to developers, it is more busy. Another reason why we can't ignore is that our test person's own knowledge is not level, many times because we don't understand demand, do not understand the relevant expertise and mistakenly think that the right thing is bug. Anyone inside any area should have such an idea and oppose this idea: That is the incorrect point of the outside line, which is equivalent to a non-responsible negation of the labor results of others. So we must strengthen our own expertise. At this time, everyone may ask, what kind of knowledge should a real tester? I want to have some more common knowledge in addition to the relevant expertise, professional knowledge is very different because of the differences in the industry, this is not detailed, I will explain the following from the aspect of popularization. As you need, this is also the basic quality as a tester should have: a. We need to have good communication skills: communication is an important sign of human progress, useful in our industry. Our communication is often not only communicating with developers, sometimes communicating with our customers. This is two different types of people, and their focus on the problem is different. So we need to master certain skills when we communicate, so you can get more accurate needs from our customers. Sometimes our work will be considered by developers to be "destroyed" sex, which will cause our conflict with developers, so when we find a bug, how to communicate with developers is also an art. Many times we are not only writing bugs, but also known to developers. This achieves a result of we want to do with each other. B. We need a good self-confidence: Many times developers will often believe that the development of testers is not as good as they, so there will be a despise attitude. At this time, in addition to supplementing our expertise, we need a strong Self-confidence. Ha ha. If he is allowed to say this to us, then I think our work has not been in a very unfavorable point, we will be taken with your nose. This phenomenon is normal. And I belong to the person who is very annoying by others.
So I know that we must be very professional to let others respect their own labor results and listen to their opinions. Of course, this self-confidence is also built in cardiac, and is not completely opposite. C. We need to maintain a skeptic spirit: (I am very good at this point, I often doubt the PLMM who should be rubbed with me to discharge. So always ..., huh, the result is the nearest medical office Dafu said that I have neurotic. The loss is big), we will often encounter such a situation, and we often discover the BUG to make the developers, they always do their best to explain each of them think that it is not bug. We have listened to their explanation while we must doubt their view until we have confirmed it. D. We need patience and good memory: Sometimes we often take us very patiently spending time, energy is going to put on it, and when we find some similar bugs, we must find these from the mind. Bug, this requires us to have good memory. In fact, if there is no such condition, the relevant document is our best inquiry information. I am a type, and I always read the previous document a lot. But there is a benefit, that is, we have revised the document in the continuous query, so that the document is perfect, of course, this improvement is also relative. E. We need a quiet heart: because the impetuous people can't find bugs hidden in the depths, (so our developers always like to let me test their things, because I reported very little, This way, their performance is very good. So I always be approved. But now I am learning, huh, huh.) So when we test, we should maintain the calm, so that we will maintain a good insight. Forces found the deep bugs hidden. And it also caught relevant focus. This is very important. Otherwise, your test is nothing to do, according to the business process, according to the user's needs, according to the development of the developer, I found some fur's bug. This is not a good testers should do. We can keep your own point of view in peace is not around others. F. We also need to be able to withstand pressure and do not have to question, our work has a certain pressure, of course, this is a little one, but it should be like this. Therefore, we often have a certain pressure, the customer is urging, the developer is in Delay, the mouse inside the box is charged. So we must be able to withstand pressure, including external, working pressure. And don't take bad emotions caused by pressure to work. Learn to do these pressures, keep a relaxed, calm heart, and then put our work into our work. The above is only based on some of the actual experience and some of the friends who have seen some friends who have seen, but there are still many other knowledge, but I have no time, huh, huh, I am sorry. It is sometimes necessary to continue to add. Just want to emphasize a little: Testing the prospects in China is very good, and this can be seen from the recent changes in the test personnel and the test environment or the customer's requirements for product quality. Still the old saying that I said: I believe that I will grasp today! --------------------------------------[About the Author]
Name: Yang Zhang
Working hours: 2 years (test related)
Professional expertise: test process management, ERP test knowledge
Hobbies: Network, Tour (this year's goal - Tibet), Sport Mail: Leveret@citiz.net
