Shulou(Shulou.com)06/03 Report--

When the developer turned to testing, there was both advice and support from friends, who advised me to say that it was not worth giving up one and a half years of development experience to do testing. Those who supported me said that girls were too tired to do development, and testing could be relaxed, and I was the one who decided. I will certainly do it, and since I feel that I have done the test, I will not regret it.

I was very hit at the beginning of the interview. after all, development and testing are two different industries. Maybe we all underestimate the testing work, because we have no work experience and no expertise in testing, so we can only start with functional testing when we get to the company. Originally thought that testing work will be easier than development, at least not so long overtime, but the fact is: overtime is now common, sometimes when I get home around 11:00, I understand that overtime is a habit in the IT industry.

When talking about functional testing, maybe you understand that functional testing is a little bit of a system to see if you can report errors, to see if you can add, delete, modify and check, and write a test case to OK. In fact, it is really not an easy thing to do. Many people will say that testing is a very boring thing. You do the same thing every day, there is nothing innovative, and there is endless bug with programmer. If the leader finds out that you don't find bug, he will be criticized. Yes, these are all facts, but you can also do better. I think if you often complain about your work and leadership, you can totally leave. It is meaningless for you to go on, if there is, you are also a walking corpse. Since you don't like it, you're not interested. It's a waste of your youth and the company's money to stay.

I think if you want to do a good job, you should have fun in your work. Now the work and life in Beijing is so stressful that you spend most of your time in the company. If your daily work makes you feel boring and depressed for a long time, it will affect your mood, which in turn will affect your health. Functional testing really does not have much technical content, but to do a good job to achieve a certain level, it is not so easy to easy. I personally think that to do a good test, we should do a good job in three points, understand the business, sum up methods, and communicate well.

Business: can do testing software, the general business is not very simple, you understand the business, you can stand on a higher point of view to examine their own work, to analyze the logical relationship of the entire system, you can not foolishly test those basic functions, you have finished testing, you know that these functions can be added, deleted, changed, imported and exported, but is this meaningful? Can you improve if it goes on like this for a long time? Can you increase your work experience after doing this for a few years? To make others think that you are a qualified tester, you must know more about the business than the programmer. Usually, each programmer only knows the business that he is responsible for developing the module, and you need to know the whole business, so that you can accumulate more experience.

Method: a good method can save you a lot of time, on the other hand, it can greatly improve your work efficiency. No matter what you do, you find an effective method that suits you, and testing is the same. You must have keen insight. When you get a function, you must be able to guess that there must be bug in that place. This ability depends on your work experience, but if you master the testing method, it won't take long, you can do it, and you have to learn the summary method at any time. If you can sum up a method that suits you, your work will certainly be enhanced.

Communication: when I talk about communication here, I mainly mean the communication with programmers. You test out that other people's programs have bug to convince others. Generally, programmers are very confident in what they do, and they don't want others to say that their things are wrong, because I come from programmers. At this time, you want them to know that they are really wrong and can't hit others too much. Sometimes I test a programmer's program, his bug I found nearly 20, he said, how not so many, sometimes a little careless and careless will cast a lot of bug, when he changed all the bug, I said you are too good, change so fast, and all right, you have to affirm other people's efforts, but also constantly praise others, this is not a kind of hypocrisy, but a kind of positive energy transmission.

Okay, that's it. Personally, I've always wanted to learn some non-functional tests, otherwise my development experience will really lose its value. I'm too busy to study. Maybe I'm making excuses for myself not to study. Slowly squeeze out time to study.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.