The road to test development--a little engineer's look Back

About the background

Student Age

• High School: The energy is placed on the ice Throne of Warcraft 3, Race UD, the first. All the classes and the surrounding Internet cafes have challenged all over. The result of course is the ignorance of my college entrance examination failed, on the three-stream university.

• Freshman: Because of love computer games reported computer department. Freshman period also do not think enterprising, played a year of World of Warcraft, 60 's, full service of the third trade union in the first DPS.

• Sophomore: This year repentant, a bitter lesson, a reformed, reformed, re-life. It took me a year to get my English level over 4 (poor foundation ...). took so long).

• Junior: This year to learn Java, the school and a training institutions to cooperate in the school conducting. I signed up with a group of students and set up a project team, pick rejoined, the days are very happy. Fascinated by programming at the time, as if to play Warcraft as fascinated. Now think is into the right industry, put in other industries I can not so much.

• Senior: Through the training institutions to Beijing internship, but because the interests of schools and training institutions fell out of the dispute, the school block not to let. It's hard to find internships in other ways, after all, our school says no one has ever heard of it. So some of our classmates ran to the guide at night to give gifts, at least in exchange for the guide to open one eye closed the results. Our line of 5 people on the Beijing train came to the Evans slum (we joked, because the interns live in the dorm is too broken, like slums). Senior year is a handyman, with the test does not matter, finally begging into the project team, but also do the outsourcing of Microsoft, do localization testing, technical content of 0.

College seems to be a failure, bitter haha of the morning to get up to the library to study, the end of school did not have any improvement, love also did not talk about a, the real XI is so twists and turns. But I have recognized that high school did not study hard, the university has to pay the debt, I planted the cause, you have to eat their own fruit.

Entrants

After graduating from the company to do Microsoft outsourcing, after the various European and American outsourcing projects, from manual testing to automation, from C # to Java. Later, a small outsourcing start-up company, the company was founded by an executive of Pactera. Outsource projects to a company called Ariba in the United States. In the first few years so in the outsourcing of the bully living, Europe and the United States project is very leisurely, foreigners do not work overtime culture, very dependent, these years dry down the body did not fall anything wrong. And let me have time to study what I like. In those years there is no progress in technology, outsourcing, the core of things do not give you to do. However, because they are doing Europe and the United States projects, so the experience has risen a lot, I saw a lot of excellent people, see the Microsoft, Google and other giants of the working style, I now a lot of automation philosophy is to learn from them. Also through the opportunity to travel, public expense travel a lot of places. I've seen the Seoul of the Metro, San Francisco's Golden Gate Bridge, a dream-like, almost Indian-surrounded Silicon Valley, cattle in the streets of Bangalore, blue sky and white clouds in California, Los Angeles Stadium in the three-point tactic is still in the embryonic state of the warrior vs fast boat. I know that California beef noodles are really not California. Foreign women really do not do the confinement, programmers really can do to more than 60-year-old, really have the city not to mention fog and haze even a layer of dust on the street, in the outlet a sack a sack to buy luxury goods is really all Chinese aunt. Another is the oral English finally exercise out, I this English 4 level of small garbage finally a little to adapt to the Indian Jabber-style pronunciation. Remember the beginning of each meeting is the eldest brother to help me translate, as long as it is my meeting with the client boss will come to help me. At that time, I was very grateful to him, I recorded the meeting to listen again and again, I really do not understand to ask the boss. Now I can read the technical documents, thanks to the foundation that was played at that time. So though the years have not improved technically. But I don't regret it.

Twists

Things have been very dramatic, I was so in the outsourcing company leisure, one person to eat full family not hungry. But then I fell in love, and even began to talk about marriage. Suddenly the pressure doubled. In Beijing is only 1W more wages, I really do not have the confidence. Outsourcing this line is not a year-end no welfare, Provident Fund and Social Security are paid according to Beijing's lowest income. So there was a little anxiety, although the daughter-in-law did not say anything, she does not care about how much money I earn. But I don't want to go on like this. Later, I contacted the classmate, that is, we have a line of 5 people to come to Beijing. He introduced me to an internet company interview, which is 58 home, a company that I love and hate. I love it because it brings me into the internet and gives me the opportunity to practice what I've learned in a foreign company, and let me develop tools and frameworks. It gives me the chance to make a mistake, give me time to grow up, let me know a lot of good people--58, chairman of the Technical Committee of the same city Shenjian eldest brother and his following infrastructure team, I was fortunate enough to work with his men, benefited. It was a period of eruption that grew every day at a speed visible to the naked eye. Hate is that I also see the test of the industry's dark and degenerate. The political struggle seems to be the main theme of the company's testing team. My immediate boss wants to eat the other several Test boss, for her seat day-to-day intrigue, behind the yin people, auto, seize the site, suppress subordinates. Do not produce all day, everywhere Brush presence disorderly command. After the accident to shirk responsibility, let brother back pot. Although her ambition, EQ is a little low, the pattern is a little small. In addition to the other Test boss is not a fuel-saving lamp, see each other recruit under the recruit, she is gradually declining, I left when she had only 2 men. That period of time is very happy and very painful, happy is I am growing rapidly, the pain is this kind of work atmosphere is simply in the chronic suicide. Every day in the quarrel with their own boss of the characters also on me, it seems that she was angry with the two test architects after the main firepower will be borne by me. It was a sense of powerlessness to quarrel with an idiot. is a completely layman but in the backseat inside the pedestrian anger. No one of his men to take her, technology, no technology, business, to manage and not management, even wages are lower than ours. We had no idea how such a person would be able to do so in private discussions. 58 It is a magical place indeed. I love this place, there are also my reluctant people and things, but here the Test team is not the place to do things, I also jirenlixia, people light words. After a lot of effort, I also had the idea of leaving. Later she saw I was really not obedient, slowly on the overhead of me. I also go to the next house around the interview, in February this year took the year-end award left there.

Precipitation

Interview at various places before leaving 58, take the offer of Micro Shop, American Regiment, and the fourth paradigm. In fact, the fate of the four paradigm is also quite dramatic. Would have been two days to go into the job, and then in the Headhunter's recommendation, directed at the name of Davin to try. During the interview, it feels like it's a place where you can concentrate on things, and each interviewer reveals a strong foundation of technical people, and is very agreeable to the continuous integration I want to implement in 58. Finally, after chatting with Dai Shin, on the spot decided to come here, wearing God is not a bit of a muddy, directly let me come to work the next day. HR speed is also fast, the afternoon interview, the evening to send an offer, everything is full of efficiency feeling. At that time, the company has just started business for more than 1 years, the first year without QA, are developing their own tests, so come to this time testing is almost blank, need to do from 0 to 1, testing process, basic services and management tools, interface automation, UI Automation, Docker environment deployment automation, continuous integration and so on. Pile pieces are my own line of code, a document a document lei up. Although looking at the work more, but all very smooth. The development team is very helpful, help me to push the process, help me write a script, patiently explain to me the product of every structure. Some things don't need me to say, they all know. I deeply feel that with excellent people working together is how happy, do not have to earnestly persuade others the effect of continuous integration, automation facilitation, process specifications, the importance of single measurement. In their hearts, these are natural. This period of time is like fighting chicken blood chicken, even at home, have time to open the computer to study, work. Because the people around are very good, not too many things. Ai is a difficult and difficult direction. The most worrying thing about hiring is that the other person may not know what the product is doing for a year. I spent a lot of time learning the concepts and principles of machine learning, which is still a layman today. Some time ago there was a question about the AI training institutions. We all smile, if this thing can train fast then I will not be so painful. Now there are only 4 QA in the team, but everything is going in the right direction, and a lot of things are not in the 0 to 1 process. But 1 to 100 of the process. This year is no longer the same as in the 58 period of the outbreak, everything appears smooth. This year precipitated a lot, no longer so disorganized. This year also a lot of calm, no longer as the previous so edgy.

About sharing

I used to be just a spectator, looking at other people's articles, others sharing, other people's technology to enrich myself. When I suddenly wanted to write something in May of this year, I couldn't say why, suddenly there was a desire to write something. Perhaps because of that vanity, may because wants to install the force, may because helps others after that a little sense of accomplishment. At that time the motive I also said not clear, anyway "test development Road" is so born, has persisted to now. Today, looking at more than 30 posts in 7 months, the heart is a little relieved. There have been twists and turns in the middle, there have been tearing force, have been immature. Some people support, some people oppose, some people slander, some people abuse. But I also as a matter of growth in the course of the inevitable result.

About testing

• I've been paying more attention to business, returning to business and embracing business this year. Until now I have been a part of manual testing. We do not differentiate between manual and automated tests, we are business tests. Let the business force us to optimize the tools, let the business force us to make automation better.

• This past year I have become more pragmatic, no longer pursuing flashy test platforms, and no longer pursuing seemingly tall recording replays and keyword-driven frameworks. Return to the essence, a line of writing code. The person who follows me in automation must be someone who can write good code. I do not need to be vulnerable, the automatic collapse of the crash. What I need is stability, efficiency, and strain that can be added to the automation of continuous integration. Because I've seen case size thousands of UI and interface automation. At this level of magnitude I know how hard it is to record playback and keyword drivers, and I know how important it is to run stability and performance.

• I've been seeing things more and more recently this year. The primary and secondary, low-optimal to high-quality give in, low-risk to high-risk give in. No longer plunge into a technology does not come out, no longer the incensed regardless of the matter. So I haven't made much of a pattern yet. UI Automation, interface automation, environmental management automation, continuous integration automation. In addition to these few things basically nothing, no static scanning, automatic traversal, automatic generation case, the platform that platform. On the one hand, product business and architectural reasons, some things are not necessarily suitable for this business. And they're all in line. Joking, the front said that the big ye have not yet done mature, which has the manpower control you.

• The recent year I have less technical feelings, is not to see this technology on the tall on, the technology forcing grid full to do. Select only the one that is most useful for your current business, the one that best fits the current team. People have to be realistic, sometimes the project needs and technical feelings are antagonistic. We want to be more competitive, so we want to learn this technology, that technology. But this technology may not be suitable for your project. You can study in your spare time, but it is irresponsible to use it in a project.

About liability

Two years ago, I was just a general engineer who developed test tools without the pressure of the business or the responsibility of the team. And now all I think about is how to reduce labor costs, how to improve product quality, how to design team development route. The more money you earn, the greater the responsibility. Sometimes the vision is important, and I have to say that the people who come out of bat do have something extraordinary. It is true that the employees of small companies and leading enterprises see things differently. And when you take responsibility, you have to do it, every thing, every effort to after thinking, whether the investment is worthwhile, whether the input is output, whether the investment is the current stage to do. Because people are so few, with one less one. No one tells you what to do, but you decide what to do. So now I do everything I want to have output, the output is responsible for myself, the project is responsible for the boss is responsible. No output is to die, is to be engaged in the blind. What is blind sex, in the project secretly play experimental technology is blind, technical feelings flooding is blind. Want to learn, want to improve in your spare time to learn, but in the project is not responsible for the mess. I remember my current boss said a word to us, meaning that everyone to start a company is a bit of pursuit, start-up companies are also most able to give you the opportunity to give you the right to do something. So cherish your right to think clearly before making every decision, it is your responsibility. Now I can always remember this sentence, always remind myself, do not like before, the production of some seemingly tall actually no egg use of things.

About automation

This year I do automation more and more focus on cost-saving, more and more emphasis on improving team engineering. I have said before the automation of the time not to think about how many bugs found. Think first about how much automation can save you money. We say automation is not just automated testing, I want to automate a lot of things. I can always see the automation of some projects in a strange state. It takes these people to automate these days. After a long time automation is still these people, these days, even to make automation also added people. The power of automation has also led to a fundamental inability to integrate continuously. This is a very dangerous state, not a good state of responsibility. There are many reasons for this, because the quality of automation is not high, man-made maintenance costs too high. Some are not clear priorities, in the low-priority things, high-quality investment is not enough, the results of the project is still a heap of people's state. Whatever the reason, it's a vicious circle--insufficient technology to solve the time and labor costs--the project is working overtime--too much overtime, no time for technical improvement--insufficient technical input to solve the time and labor costs--project people work overtime. As previously said, the vicious circle, you have no time to do your favorite technology to improve the quality of the project. One of the main responsibilities of our automation is to save manpower, which is not well done, but is not responsible. This I want to deep introspection, before the Broken keyword Drive project is a model. I conclude this year that the virtuous state of automation should be this: the cost of investing in technology-reducing the overall cost-the spare cost to invest in other technology projects-to reduce more costs-more spare costs to invest in other products to improve the quality of the technical projects-product quality is getting better, virtuous cycle.

About Ascension

Yesterday, when I was drinking with my classmates, he told me a lot, that is to introduce me to 58 of the students, to wake up my classmates. He is now a testing director of a company that has previously worked and worked as a CTO and has a much better ability than me. He helped me a lot along the journey. Yesterday when Jiuyi was in a good time, he told me that if you want to go any further, you have to look at things in a higher angle, besides keeping the technology. You have to tell your boss what your team should do, the problem of this team, how to build a quality assurance system, how many people, how many people put into automation how many people do manual and so on, and so on, if let your boss tell you these, then you are still far. So 2017, I hope I can exercise to tell my boss the answer to these questions.

About transformation

This year has focused on a lot of things that are closely related to testing but are less straightforward, in addition to automated testing, continuous integration, and so on. I've focused more on engineering automation, DevOps. I took the initiative volunteered to take over the automated deployment and management of all product environments within the company, from compilation, out of package, to deployment. According to the development, testing, product, operation and maintenance of the different needs of the environment to customize a set of Docker-based environmental management solutions. I started to practice devops more, and the product versions and environments we deployed in our customer sites were not the same. We started to make deployment images and automated test solutions based on different operating systems and product versions, hoping to let developers build their product versions and deployed system environments at the time of an accident, solve problems and quickly automate tests and packets them out to the entry staff. In short this year, I began to march like a devops.

About family

Married, moved into a new house, son 4 months was born. This year's progress is very fast ~ two days before New Year's Day is also the impulse to endure learning and work, put down the computer dedicated to accompany the Queen to produce. Feeling is also a long time not so attentive to accompany her, I am busy working all day not to accompany her not to say, the family parents are not good, after serving my sister-in-law and the big nephew back to keep. I can only make a breakfast for her now. She always makes her own lunch and dinner, and I really feel sorry for myself. Parents of the body of the problem also makes me very worried, watching them a little bit older, the body a little bit bad, my heart is also panic. I hope the new year, I can spare more time to accompany my family, for my family to do more things.

Ext.: http://mp.weixin.qq.com/s?__biz=MzAwNjEzMDUyNw==&mid=2650198210&idx=1&sn= 2ba72a0e55863a39bd16d4c97ca34d55&chksm= 83106ef2b467e7e400122e8bfe7947c52e812c67859e67c1b449df4496426521e8121cfb5ced&mpshare=1&scene=23& Srcid=0106dph3kr4kcwwc8nrz9lg1#rd

The road to test development--a little engineer's look Back