Summary of the work of the software test engineer

"Summary" Software quality is getting more and more people's attention. Software testing has many imperfections as an emerging industry. Many of the peers engaged in software testing work are confused, how to improve, how to solve practical problems in the test work, and puzzle everyone. This article summarizes your personal experience and hopes to help everyone.

"Keywords" software test software test learning software test engineer

When I first took part in the testing work, I didn't know what software testing was. The concepts of integration testing and system testing were often confused. What CMM is even more unknown. At that time, the simplest switch machine was also completed by directly plugging in the power supply. The installation system is the highest skill of mankind in history. For those who install the machine with a screwdriver, it is considered to be the super master of U-none, killing people. Invisible secret skills. Napoleon said that the soldiers who did not want to be generals were not good soldiers. My first dream was to become a master of software testing and to be proud of the world. Therefore, I have been stealing the teacher and summing up the experience. I believe that I have mastered several secret skills that have become masters. In recent years, the "river and lake" has not been compromised. I don't dare to enjoy it alone. I hope to learn from our testers, and sum up the success of the secret technology as soon as possible, and help the new recruits get started as soon as possible.

The first move to learn to use the Internet

Just joined the work to face the vast online world, at that time, such as Liu Yujin Grand View Garden, everything is novel, everything wants, download a lot of source code from the Internet, software technical documents and the like, can not wait to collect all the good things In the hands, in fact, some people seem to be a bunch of garbage. At that time, I felt that I had these "martial arts cheats" and became a high-handed person. I initially participated in the work because I was fortunate enough to turn to development. After joining the project team, my habits have not changed. Instead, I have become more aggressive, with more resources in my hands and more frequent online time.

Once the project manager assigned the task, I felt that relying on the cheats in my hands and my own "intelligence" would soon be completed. Unexpectedly, in a short period of time, everything became the Maginot line. The problem is very slow and the idea is not clear. The project manager taught me a memorable one in the process of putting pressure on me. I learned to use the Internet to find the answer to the problem. From then on, Google became my favorite. The tricks of my change. In the software testing work, he solved many difficult problems for me and answered many places that confuse me. It is also one of the means for me to help test peers to solve problems. Many software test novices and even veterans don't realize that they have "invincible cheats" on their hands, so as long as you are patient, the answer is around.

Here is a summary of the techniques for using web search engines:

Combined search

Every time you search for a file, if you only give one word for searching, there will often be thousands of matching pages. However, if you add a word, the search results will be more relevant.

Select the phrase for the expression

In general, when I search for the webpage, I choose some keyword groups that can express the content I want to find, which is used to narrow down the search range, so that finding the search results is the best way. To use phrase search, you can simply enter a question as a phrase search first. If you still can't find a suitable one, then use multiple keywords that can express the content you want to query.

Targeting information source

Sometimes the phrase cannot be searched or cannot accurately represent the required information. You can use another method to go directly to the information source, either directly to the site that provides some kind of information. You can use the formula "" to guess the characteristics of an organization. Thereby obtaining the main phrase of the information to be searched

In fact, there are a lot of articles on search skills on the Internet, you can learn on your own. Always remember that search engines are a powerful weapon to help you succeed.

The second move to learn hands

After participating in the software testing work, I feel better and better as my work experience grows. In the company, I was gradually paid attention to by my colleagues. When I tested the company's new software functions, I tested several bugs as usual, and then filled out the Bug list carefully. At this time, the test manager came over and re-examined the bug. He simplifies my input changes during the process of recreating my bug, and the bug magically appears. The same phenomenon, he closes the software and changes the input again. After expanding 10 changes, the software does not move, and the memory continues to rise. Finally, he found the cause of the software bug, and then said to me, "Looking for bugs to be accurately positioned, our development team is a whole, time is equal, time is not wasted on you, it is wasted on him. If testers The bug descriptions found each time are unclear, and the potential cause of multiple problems is one, although the operation may change slightly. This way, the developer has to debug the trace when recreating the bug, which is time consuming and inefficient. If the tester finds a bug, more hands-on can more accurately locate the bug steps and reasons, give the developer the most accurate steps and accurate description, so that the entire team can be efficient, so you need to collaborate!!

In the days to come, I will remember to test more times and try more each time I solve the problem. When many friends and colleagues on the Internet ask me questions, they are actually just one step away from the Long March. As long as they do more experiments, they can achieve their goals. So do more hands and try more.

The third move is to think about what you have done.

When I first started, I always thought about how to do software testing. I think that the company's testing process is always very confusing. I think that I can't learn anything. How can I test a good product? I often say that my heart is not as good as action. I used to see the scenes that often appear in Gu Long's novels. The unknown boy constantly challenges the master and sums up the accumulation. I have concluded that some of the experience is obtained in actual combat, so I constantly try to introduce a new test process and then evaluate it. Although this process is very painful, I have accumulated a lot of experience. During this time, I learned a lot of things, and I was exposed to ISO, CMM, test management tools, and automation tools. Because the report is often written in the work, it has become a habit of summing up the lessons, because the things on paper will never be forgotten. In the process of writing, it can be continuously supplemented and expanded. The whole process is the process of sublimation of thought. The nine years of Dharma face is a typical example of integration. If he does not have a process of thinking, he cannot become a generation. If someone later records his stunts from time to time, there will be no later Shaolin Temple 72 stunts.

Therefore, being good at thinking and summing up experience is also the only way to become a master.

The fourth move to learn to use forum resources

In fact, the difference between testing new recruits and testers is often not using existing resources. In the forum, we will see a lot of newcomers constantly asking questions, but there are many problems that have already been mentioned by others, or there are already solutions. Therefore, I often see the "testing master" figure, and do not mention the problem, but also "stubbornly help the weak", is a life-saving straw to test the new Ding. It seems that the masters are omnipotent. In fact, they have taken off this dazzling aura. They didn't think so much, but just found the answers through their own search and then helped others. Of course, there are also many people who have learned a lot through self-study and then exchanged ideas in the forum. The master is also good at thinking about problems and solving problems personally. So they are constantly improving as they work and use the resources of the forum.

Many times I saw some questions in the forum, the problem description was unclear, and many people looked confused. Posting questions can't move, please help the master, life-saving and the like, it seems like the world is chaos, the end of the world. Although this topic is very attractive, it is impossible for those who want to help you to help you, because the title is not clear, and the master word has deterred many people. In fact, asking questions is also a process of sorting out ideas. The description is clear and people understand clearly. Only then can you know the environment in which you are currently in trouble, and let those who want to help you solve the problem, otherwise it will give people the feeling that they can’t get started. It is not efficient to solve problems.

The fifth trick is to learn about the software products you are testing.

To be a good tester, you need to know the software you are testing. To understand what the architecture of a software product is like. To understand the market demand of software, you should be able to look at the user's feedback at the beginning of the contact with the software. These are the users' most concerned, and you need to pay attention to the test, to meet the customer's greatest needs. But after understanding the software requirements, you should learn to read more about the technical documentation of the software system, software design documents, which can help you understand how the product works. There are a lot more questions in the company's bug library. These problems can help you understand the flaws in the software products, and the software system will be wrong. The software is running in a big environment. If you are not familiar with the system, then some problems you can't consider from a broader perspective, learning the knowledge of the operating system can help you find defects and locate the problem more accurately. For example, if the software runs on Windows or Linux, if you don't understand the operating system, you can't set up the test environment. Sometimes the software components have problems, which is caused by your system configuration. If you are not familiar with the system, you will attribute the external reasons. For the software itself. So learn about software systems, such as programming, networking, databases, and more. Not necessarily how good you have to learn, just through these extended knowledge areas, you can not be limited to narrow circles when you find problems and solve problems.

Communicate with all relevant personnel, different communication channels, and get different information and different angles. Communicate with customers, you will find problems from the customer's point of view in the test; communicate with the developers, you will understand how the developers implement the software functions; communicate with the project management staff, you will know the development progress and difficulties encountered