How did I successfully transform from functional testing to automated testers?

Hello everyone, I am the tester. (Sixth brother is also OK) 
Time flies so fast, I have been in this industry for more than eight years without knowing it, and I can be regarded as a veteran of the test circle. 
Looking back on the various things I have been on the road of automated knowledge search, I still vividly remember it. It is really not easy to watch myself walking step by step... 
If you haven’t read "Just a year of testing When, how am I? ", there may be some difficulties in the connection of the story, if you are interested, you can read the first one, and you will cry. Yes, this is a true story:

Automated testing

After joining the new company, the new colleague (DJ for short) who joined me together went to an operating project downstairs to conduct "business familiarization, learning and assessment". 
During the next month of business learning, I really didn't live so much every day, and there was at most one bug a day for you to verify, and I didn't write test cases. A bug will be verified in a few minutes, and the business and baseline documents have been read many times, so it is already very familiar. If
I can’t be free, I just find something to learn and research. Later, I was discovered by chance by the test team leader, and later told me, have you been exposed to automated testing? Send you a document and have time to study it later. 
For me, I have never been exposed to automated testing, but my instinct tells me that this thing should be very "exploded", and it feels like it's tall and powerful. I
took a weekend break, spent a day, studied the content of the document, and wrote a login Demo using the company project as an example. I showed it to the test team leader on Monday, and got the affirmation from the test team leader that I was quick to get started. I
didn't expect it to be pretty good, I am not too stupid.

Persuade the edge

But the good times didn't last long, everything seemed very good, but the challenge also followed. In the interview, my vice president said that our business studies downstairs have ended and we are going to return to our department. Let me and DJ write a test case for our department’s project, one for each module. 
Of course, I don’t know how to write test cases and the correct standards. As a result, after the use cases are handed in, one can imagine. The
vice president talked to me and said that the test case I wrote was unqualified, and said that he would give me another chance. If the writing still fails, giving me seven days to find a job is actually being dissuaded. 
I deeply know the seriousness of the problem. This is my last chance. A strong desire for survival ignited in my heart. I thought I must stay, I must.

Really stayed

Based on my own understanding, I design and write use cases according to the prototype diagram. After sorting, the prototype diagram and use cases were packaged and sent to Lao Song, "the early trainees of the same training institution as me". She went through it again for me and added comments and marks to the use cases, and pointed out the shortcomings. 
According to her guidance and suggestions, I optimized and integrated the use cases, asked for help again, and sent me to the sister of the test team leader during the internship downstairs to see if there were any omissions. 
With her help, I once again integrated and revised the use cases, and after sending them to the vice president, I passed them all at once. 
In this process of designing and writing test cases, I have gained the standards and ideas for designing and writing test cases. I am really grateful to these two friends for helping me through the difficulties when I was in the most difficult time...

Staff strain

After passing the assessment, he returned to work in his group. My DJ and I formed the department's testing team. That is a total of two people. Since the company's business is very busy, it is simply too busy, 996 is basically the norm. The
leader borrowed a test classmate from downstairs to work together. He is a handsome big boy who is very clean and has great skills and business. The
point is that development colleagues always praise him for his carefulness and quick positioning of problems, especially in the preparation of test cases and business testing, I am very envious.

Use case writing enhancement

Sometimes worship may be a great help for your progress. 
Growth generally starts with "copy". 
Once you are not too busy, go to Zen Tao to read the use cases he wrote and the bugs mentioned, and carefully record the missing points. If you don't understand the business, you will sort out and go to the product manager for repeated confirmation. 
Soon, my use cases and business shortcomings were improved.

Recognized again

Of course this is not the point. At that time, I just worked very well and studied whenever I had time. 
Once the company accidentally disconnected from the Internet, it took about three hours if I remember correctly, the other colleagues were basically playing mobile phones. 
I open the IDE habitually, write and debug scripts. I wandered happily in the world of code, not knowing that the vice president stood behind me for a while. 
Suddenly, the vice president said that we will use our system to write in the future, and regression testing will also be useful. Once I will let XX find you the automation framework code written by a certain XX before to get familiar with it, and use this to write in the future. 
I just noticed that the vice president might be behind him for a while, and it was so happy to be recognized again.

The road to cross-language learning is harder than imagined

After getting the code, I still hesitated. why? When I
first started to get involved in automated testing, the PDF documents that I gave to me were based on JAVA language. Although, I can write a login demo, but it is not so smooth. The
more I look at the back, I find that there is a very serious code knowledge gap, which means that the code behind is completely unreadable. 
It is also the first time I have encountered a situation where the code will not be ignored. 
At that time, when I was studying business downstairs, the person sitting next to me was said to be a better performance tester in the company at that time. 
I saw a book called "Sharp jquery" on his desk. I dared to ask him a question about traversal for each. The other side glanced at me, and then he hummed and stopped talking. 
I feel as if I have been ignored. Of course, the other party may not hear clearly. 
I wonder if it's so difficult and my heart is shaking, whether I want to keep going.

The road to self-learning begins

Driven by evasive psychology, accidentally in a technology group, I heard that automated testing based on Python is particularly easy to use, so I started a new attempt. 
I found the second version of Python-based automated testing written by Chongshi (super easy to get started) in the group sharing to learn. At that time, I felt like I got it. The feeling of martial arts secrets is very happy. 
I have learned about this documentation for more than a month. In fact, the automated API is relatively familiar. As for maintainability, stability, and robustness, I still lack consideration. The
frame given by the vice president to my former colleague is based on JAVA language. After I got it, I couldn't understand it at all. Another more serious problem is that the code reports an error, and no one asks or who to ask. The development is all JAVA, and there is no way to start. 
Later, I gritted my teeth and thought for a while, this framework may be able to learn more, which opened the way to learn Java.

Warned again

The problem upstairs is very serious, it is increasingly exposed, and there is no test team leader. Therefore, the work and process of the test are relatively passive. The
vice president asked an elder sister of our department to manage the test group. The eldest sister does not understand testing. She often raises bugs for development because of undeveloped functions (reserved functions), and it is not pleasant to get along with development. The
test team fell into a "strange circle", which caused people to mention bugs randomly. 
The normality of the 996 rhythm may make everyone irritable. 
Every time the test group has a regular meeting, the atmosphere is solemn, and only the older sister is talking. Unless necessary, we don't have three basic words. Every meeting is as silent and embarrassing as the memorial meeting. 
Maybe this eldest sister and I are angry and at odds, no matter what I do, the eldest sister must give some guiding "suggestion", the point is that it is useless to me, and the work efficiency has not been improved, and sometimes the time cost will be More, then I stopped listening. 
Occasionally, the eldest sister used the same sentence (to persuade me to quit) and said, saying that I had a bad attitude at work, and then gave me another week to observe. 
At that time, I immediately gave up and was persuaded. I quickly said that I was arguing with my girlfriend (Where do I have a girlfriend? Every day, I don’t even have a person to talk to, and I’m arguing with a wool), and I said that I should make adjustments. 
Theoretically, if I am softened, it should be better. But I found out that the weaker you are, the more people bully you, that is, what the old man said, bullying people, always pinch soft persimmons.

Successfully transformed full-time automated testing

Once I assigned the test task, I didn't know one thing too clearly, so I asked one more question. The eldest sister said that I am not clear at the level of speaking, and I don't know how to ask questions. I have to learn the process and method of asking questions. This is obviously a fault! 
I didn't speak, and returned to the work station, I sorted out my emotions. It really drew a flow chart for asking questions. Then, first show it to the DJ and ask if there are any problems. 
Seeing the situation, the eldest sister immediately called me out to talk and asked me what I meant, saying that I put eye drops on him, and that I wanted to persuade me again. I didn't say anything, just echoed. The
next morning, I went to the vice president and asked if I could transfer to another department. I said that I was not happy with this eldest sister, but I didn't say that she wanted to dissuade me. 
I was surprised by the vice president, who asked about the situation and progress of automated testing. I said that I can use it proficiently. After listening, the vice president said that your work will be connected with me in the future, and will only do automated testing, not functional testing. 
After listening, I was stunned for a few seconds and quickly expressed my thanks. This is undoubtedly a kind of recognition for me.

Growth and transformation

To borrow a passage from Mr. Wang Er:

Set yourself a strong goal to achieve, act immediately, and study and study;
Find an environment conducive to your own development and diligence, and maintain self-discipline;
Pay attention to the accumulation of quantity, record and examine your growth periodically;
Practice deliberately and replay patiently;
Fix mistakes and persist for a long time;
Although starting in smallness, I wish to end in greatness.
Run towards a better self, to welcome a great life.
As a college student who graduated from an ordinary college, not majoring in computer science, relying on self-taught programming, he became half a "programmer". 
I was born out of college and I was just a rookie at the company. 
Beijing is very big, and there are many people who are better than me. I can only say that ordinary people cannot be ordinary. 
The mechanical nature of life and work will quickly obliterate the inner fighting spirit and ambition. If you don’t try to change and get out of your comfort zone, it’s no different from seeking stability, waiting to get your salary, or eating and dying. Obviously, it’s not for me. There
is such a desire in my heart to become stronger. Why am I so weak? Why? 
A voice deep in my heart told me very clearly that I must become the company's independent automated test engineer. In the
book "Ten Thousand Hours of Genius Theory", the author Daniel Coyle visited the world's most successful football players, violinists, fighter pilots, artists, writers... and finally unearthed a truth: 
Most results are deliberate practice. 
Starting from the environment construction, java object-oriented, maven, Javaweb and other technologies, we can overcome each knowledge point. 
In addition to completing daily work, every day is to watch java videos on the subway, read the source code, and press official documents. 
Go home at night and press the code. It is normal to learn that two or three in the morning every day. 
Of course, I also joined a lot of QQ technology groups during the period. Like many Xiaobai, I asked some very low questions. Moreover, I am the one with the most problems every time.
From asking questions in QQ groups to rigid frameworks, my self-learning ability has been greatly improved, and at the same time I have developed many good habits of self-discipline, and unknowingly formed my own set of self-learning system. 
The best thing in this world is that everything becomes what you want under your efforts. 
Soon the framework is no longer mysterious to me. It is very kind and familiar. Suddenly I felt that I could write it myself, and then refactored it a little later. Later, this framework became my own style. Slowly, he grew from a rookie to a dedicated automation tester for the company. 
Why write this book

I have no reputation or experience working in a large factory. I have a grassroots background in testing, and I have worked hard all the way. As a newcomer, I know how to transition to an automated tester. 
On the road of automated testing for knowledge, I have been hesitated and confused countless times: 
Children without umbrellas must run hard! 
As a self-learning party, I deeply feel that no one will bring it and no one asks, so I decided to write this book. I want to write into the book the techniques, self-study methods, experiences and pitfalls I have learned and used in actual work. 
I hope you, like you who want to learn by yourself, can avoid some detours through this book, and through reading this book, you can form your own system and apply it in practice. Of course, I sincerely hope that you will get promoted and raise your salary. Perhaps this is the most practical thing. 

If you have similar confusions, then this book will be your mentor and helpful friend, and may bring you some practical help and breakthroughs. 

This book is suitable for

This book is suitable for a wide range of people, students who are interested in automated testing technology or are doing automated testing, such as manual testing, automated testing, test management personnel, etc., can read it.
This book uses a large number of practical cases, from the simple to the deeper, and is easy to understand. Many code cases are added in the book to facilitate readers to understand. This book is not only suitable for beginners in automated testing, but also suitable for intermediate and advanced test engineers. And managers who are ready to lead the team to transform automated testing can be said to be an indispensable reference book in the learning process of automated testing.

The main content of this book

The whole book revolves around Selenium3.0, introduces the automated testing theory and mainstream technology step by step. Through a large number of actual cases and practices, readers can get the improvement of technical ability and the improvement of knowledge system.

What can be learned in this book

In order to help readers better implement automated testing in the enterprise, this book not only introduces automated testing theory and automated testing process, but also introduces the actual application of Maven and GIt, unit testing framework TestNg, and mainstream design patterns Page Object and Page Factory application, development and construction of automated test framework, CI continuous integration, use of test report ExtentReports, use of Cucumber of behavior-driven framework and use of distributed parallel test Selenium Grid.

Book features
Quickly master mainstream automated testing technology.
Uncover the mystery of automated testing in enterprises, and make automated testing truly practical in enterprises.
Improve comprehensive technical capabilities, enhance actual combat, improve the knowledge system, and complete the perfect transformation from entry to independence.
how to buy

The new book is currently online in Dangdang, Jingdong, Pinduoduo, Taobao, and Tmall. Readers can order through the online store or scan the code below to order.