READ: A girl from a software test engineer to a supervisor's growth story thoughts

Today, I read an article from the internet, a girl who shared her success: from a software Test engineer to a supervisor. After reading a lot of sentiment, share and hope to share with you, but also hope to bring you some hope and encouragement. She used to study economic and trade, because of the strong interest in the test industry, after graduation in Beijing school to learn software testing engineering major. In less than a year, she has been promoted from a tester to a Test director. She has accumulated a lot of experience in learning and working, so she writes down the experience of the year to share with you.

Original article:

Go into the testing industry: interests, knowledge
To tell the truth, I do the test work time is not very long, after learning software Test Engineer's course, to now is more than a year of time, but, I am willing to learn and work in the accumulation of these bits to share with you.
I walked into the testing industry because of interest, interest, enthusiasm for learning and work, really is not fake. From my choice to walk into this industry, study, work, from the tester to the test director, I am happy, but also very fulfilling, very fulfilling sense.
I think, in the decision to enter the testing industry, it is necessary to do more preparation and accumulation in this area, first of all to have a solid test theory basis, these knowledge is not only learning time to learn solid, in the future work will continue to improve. Second, there must be a certain degree of industry knowledge. After graduation to find a job, have to do mobile phone testing, but also to do outsourced testing. What I do is ERP products. As we all know, ERP (Enterprise Resourceplanning) is a corporate resource planning system, which is based on information technology, with systematic management ideas, for the decision-making and staff of enterprises to provide decisions to run the means of management platform. I was in the study of the test before the professional contact with ERP, so, in the graduation of the search for work on this aspect of development.
When it comes to looking for a job, I think it's a one-off and flexible interview technique. Sometimes you have to apply what you've learned in life to an interview. I remember the first time I went to the interview, it happened that the night before the interview I just saw a TV interview on the show, and the next day I went to the interview on my own when I used it. It was when the salary treatment was asked. I think this is a lot of people, including my own in the interview will feel a more headache, because, said more, no, said less, also not. At this point, you will have to use some tricks.
At this point you can first tentatively ask the other company in the recruitment of the position when it is stipulated? When you get to know this, you will be able to measure your own technical ability to compare the corresponding salary, the other is to see the strength of the company, as well as the industry in the general treatment of the position. In this case, when you say your salary requirements, if, the company is small, but there is a certain development space and you want to try the situation, you need to pay low, the other side will consider that you may have a general understanding of the company's strength so that the conditions, not your own technology no If you see this company is still relatively good, is a certain strength of the company, at this time, you can properly raise their worth.
My application is still relatively smooth, the first day of the application, the next day to work. I remember the interview at the time about 2.5 hours of talk about a one-off interview clearance. In addition, I am also proud of myself is that I am the only one in our company in two months to positive.

New arrivals: Familiar with the environment, as soon as possible

When you start entering the company, you should be familiar with the company's environment first. In some large companies may be familiar with the environment of the time, but also arrange for some appropriate training or something. I then entered the company is relatively small, there is no relevant training, it was only our department manager to get some relevant information, documents, let the network management to configure the working environment. But small companies have the benefit of small companies, and he will soon get you involved in the job and assign you tasks.
Therefore, you must be familiar with all aspects of the company's environment, especially the personnel environment, within a week or so. I think that interpersonal relationships are also important in the company, and it's even more important to exaggerate than your job. Because, mastering technology is your IQ problem, and contact with people is not so simple, because our interests, hobbies may be very different, personality also has introverted and outgoing, so in entering the community into the work post with people really is very test a person. If you have a good relationship with the company, the work will be well coordinated and the progress of the work can be smooth.
There is to be as soon as possible familiar with the company's test environment, operating system, development language, platform, and then to understand the company's products, master product-related knowledge. Like our company is our own research and development of distribution group, financial such a system. When you want to understand the company's products, you can go to the product Development department, or the design department to some relevant documentation, as soon as possible to intervene in the industry, familiar with the test project to do. To tell the truth, I was studying economics and trade, not learning computer, so I was a bit dizzy at the time, I directly take the product of their own in there groping, write a product use instructions. To such a thing, there may be a special selection in a big company, and in small companies it is possible to learn the products by themselves. However, I think this is a very good exercise, but also to explore your potential on the other hand.

Test Plan

Writing a test plan is like what we learned in class, test plans, test cases, and start our testing process. This is the time for specific applications. Write the test plan with the development department to design the documentation, product specifications and requirements of the survey (product instructions) such as the relevant documents. If in a large company, his design department will write product instructions or some test protocol. There is a need for his development plan, because you do every step of the test is based on development progress, development planning is essential. Finally, based on the above documentation, a simple test plan has taken shape, from time, content, resources, tools, and manpower arrangements. Like a small company, he will be very concerned about which day the person finishes the work, like the relatively complete document we have learned in such a small company, because they do not have a lot of manpower and material time to see such documents. Writing test cases first depends on the characteristics of the product. The characteristics of your product before the product is not formed, you certainly do not know or particularly clear, but you can be based on its framework is probably given out, you can think of as far as possible to write to the document inside, and then in the testing process of continuous improvement.
If you suddenly find a good test case in the process of test execution, be sure to add it in time, you do not add to it is a big loss for you, because you may later work will need such a document, or later take over the person you work, he may see this document, This will also be a great help to his future work. In large companies there are specialized test designers to write these things, in small companies are test supervisors or testers.
I do things like our company from test cases, test plans, and test executions. Originally because the company is relatively small, I do, it was to give me a recruit an assistant, also used for about a month or two. My personal feeling is that unless you recruit particularly skilled, to the industry, testing technology in all aspects are more familiar with, one can get started work is OK. If not, recruit a fresh graduating students, he is not very familiar with the test industry, and small companies, the manpower itself is less, you do not have the time to give him training, and you have to work, there is not so much energy to hands-on teaching others.
Be considerate when designing test cases and don't repeat them. As far as my work is concerned, ERP product is to pay attention to the excuses of each module and data test. There are a lot of interfaces, such as the sales module is and the financial module in the test is a repetition of the part, this should be your own attention. The industry is stronger. Next, execute the test. To be executed according to the test case. You can't say you did the test case and don't look at it at work, so it's not helpful for your job. Because you follow the test case to carry out the basic is to follow your own ideas to do, so you go to any step in the mind is very clear. The biggest benefit is to reduce duplication of effort and increase productivity. I think this is important both in small companies and in large companies, as well as in the way we work.
Then, it is better to do a test day record, the purpose is to clear where you test to avoid duplication of work. As far as I am concerned, I do the test diary every day when I am doing the test, one is to record how many bugs I found today, to what step? What work has been done. I found this to be a very interesting test day record. How many bugs were detected every day, I recorded it on the bag management tool, but I still have to record it.
The first day I went to work, when I first came into contact with this test, I remember especially clearly that I found 65 bugs. I think this shows two problems, one is that I work very seriously, one is the research and development department has a problem is indeed a problem. So, you do not think that research and development are very powerful, very cow ah, you will be a little afraid.
At the beginning of our company is Lenovo, founder, Hewlett-Packard, the three main pillars, but I do not feel intimidated, although they are very conceited. Basically a small error can be raised, they think it is not a bug at all. But when you arrive at a seminar or technical meeting or evaluation session, you can come up with it, as this is the most basic work you need to be a tester and a conscientious and responsible attitude to your work. Communication with developers. This is very important for testers. This I mentioned earlier, everyone is not independent in doing things, the work needs to cooperate with each other, especially testing work, there are problems, you need to timely and research and development personnel communication. If you do not communicate well, then there is no way to test your work. In this, you have to adhere to their own principles, is the wrong thing, because, this product has a problem, it is the existence of a bug, then, someone will be responsible to modify. You can not say that the other side is the department leader you do not dare to insist on the question you ask. The second is to stick to other testing principles, which is what we know when we learn the theory. Because, we study the curriculum design is according to the project to set, many things basically and the actual work is consistent. As a Test manager, I have set a basic workflow for myself in the testing work, and now I'm going to take it as the department's rules and regulations. is to enter the bug, I will do in the following bug description, the developer whether to modify, why to modify, about the time is how much, so urging each other's words, will be conducive to the progress of the work. Otherwise, if the work is not completed, there will be a phenomenon of mutual excuses. When the bug is detected, the developer is urged to modify the bug. Also pay attention to the bug management tool. You need to use good bug management tools, but also to urge developers to use good bug management tools. Because, a lot of developers are still lazy, he will tell you, there are any bugs, you go to my machine to show me on the line?
It's a bad habit, and it's time-consuming. Therefore, you must urge them to use the Bug management tool. This is what I have learned deeply, but also in the two big companies meeting, the final is accepted by everyone. We all know that the general development of male colleagues more, do test girls more, you ask questions when the attitude is not too tough, in the daily work of the tactful remind him, we generally will not be too difficult for you. Not only the work solved, the relationship between colleagues is also very harmonious.
The test report is then written. These we have learned in the employment class, is the test background, content, test pass rate. and the advantages and disadvantages of the product, as well as your suggestions for the project. It's all done and it's a test-and-evaluation meeting.

About automated testing my personal opinion

I personally think that the automation is now rife. Now a lot of companies, whether big or small, whether the company has used this test tool, he will ask you will use several test tools, will be automated testing? When I went to the interview, I also encountered this problem, when I first asked him, our company has done in addition to manual performance, or functional other tests? They replied that no. A product that does not do manual testing is determined not to use tools instead of manual.
Automated testing is not a substitute for manual. Automated tests are good for saving time and improving efficiency. But if you use it badly, you will increase your workload. If your needs and interface continue to increase, then automation is also not used. I think the company is suitable for automated testing, one is the safety and performance requirements of the product strict; one can have a person to teach this document to maintain. Like those who do not pass the manual test, demand changes frequently, fewer people, the product of the GUI by the production of modified companies are not very suitable for automated testing.
Accidentally organized so many drops out, I really did not think I still can write it. It is estimated that this is related to my work in the company in addition to testing and doing other jobs. I said, because we are small companies, so, some product use instructions, product installation instructions, including customer service training, are written by me. In addition to testing, some work unrelated to the test I will do, such as the preparation of test system, OA product manager, pre-sales consultants such work. I think that's how I exercise.

READ: A girl from a software test engineer to a supervisor's growth story thoughts