Automation for the first time

As a tester , We have all heard or used automation more or less , When we first entered the testing industry , Full of expectation, I thought that the end of the test was that there was no need for testers to nod , Project 1 test , Click the automatic switch with a small hand , The instant test is finished .

This is what I was most curious about when I first switched from development to testing , With this curiosity , I joined the newly established automation group of the company with passion , Find out how to get rid of manual labor and complete the test , Does is 6 year .

Next , Introduce the use process of our automation in the company one by one , I hope it can enlighten you , Help .

Automatic start up

I believe that every company that builds an automation team , Undoubtedly, I don't want to improve work efficiency through automation 、 Save time 、 Save manpower .

But there is a fatal place , Many people who first drafted Automation , He may not understand the essence and characteristics of Automation , Just know “ Automation can improve efficiency like other companies ”, This is what we did 3 The truth realized after automation in .

This is not criticism 、 Blame who , I'm grateful to walk through that 3 year , Every section of life is not wasted , It makes me deeply realize what kind of approach is feasible and what kind of approach is not feasible .

I say it here , I just think it doesn't take so long for the latecomers to understand , I hope you have a more comprehensive understanding of automation before making decisions .

2016 year , The leader decided that the testing department should do Automation , It was not long before I switched from development to testing , Still doing functional tests （ Experience the function test stage ）, After a period of time, I feel very cumbersome , In addition, I am usually looking up information in the field of Automation .

therefore , When leaders say they want to set up an automation group , I'm so excited , Decide to join the automation group , I thought I finally had a real chance to try this new thing of Automation .

Although I have some poor development skills , But after all, there is no actual combat Automation , So we recruited a big bull in the direction of automation from the outside .

Technology is different , Just use 2 Zhou set up our automation project architecture , And the related package extraction . At that time, I really knew Selenium、Webdriver、TestNg、Jenkins Workflow and usage of an integrated automation system .

Write here , You probably already know , What we have achieved is a set UI Automation solutions . The framework is finished , The rest starts to collect use cases 、 Conversion script , Also in the process of writing scripts , I gradually learned how the so-called automated testing is automated .

Early Automation , We have little experience , We only know that we should at least automate the common mainstream use cases .

therefore , So I began to extract the use cases of this type of a module based on my understanding of the business in functional testing for several months , Technical Daniel and I have transformed these use cases , This process , For me, I learned a lot , got it PO Pattern 、 Data driven 、 Element positioning and some pits inside .

Writing scripts is easy for me , Soon we finished a phase of automation use case , Then integrate these use cases into Jenkins On , thus , Even if automation is in initial operation .

Explore the meaning of Automation

After the first phase of script conversion , Start to plan the script development of phase II without stopping . For a long time , I think we seem to lose the meaning of doing Automation , We have completed script development , Why not ？ How can we use it in our work ？

When what you do doesn't play its value in your work , People who do this will gradually lose their enthusiasm for this job , Because he didn't get feedback , He doesn't know where the next goal is . Of course , Also will continue to do some dispensable work .

The following year , That is to say 2017 year , The leader began to think of ways with us , The first way is to talk to the function tester , What modules and use cases have been automated , Let them in the process of testing , If you need to execute that type of use case , Just go to Jenkins On the implementation .

It has been proved by trial operation for a period of time , Don't try to do a good job by free and voluntary means .

Most people don't choose to use automation , Even if his project can be used . There are also some students who want to use it , Because I don't know development related technology , Will not analyze the problem when it goes wrong , Often need to find automation developers to help see , Combined with the , In the early UI Automated scripts are really not that stable , The probability of running wrong is higher .

The reason why there is no need for automation comes out ：

1、 Not interested in , I think manual measurement is very good ;

2、 Want to use , However, I have a lack of Technology , Won't analyze script problems , Make it more difficult to use ;

3、 Want to use , But the stability of the script is too poor , Lose trust in Automation .

Compared with other colleagues , Think of yourself as an automation enthusiast , I don't believe that automation can't work . assume , It must be because you can't use it yourself . therefore , I applied for a period of testing suitable for automation application modules .

How did I do it ？ following , It is a flow chart of automation application in normal project testing , I still use this idea today .

  Follow this process , Stumbled over several projects . The real effect is ：

1、 Some problems were found after using automation , But the analysis shows that it is a bug It's really not obvious to the naked eye ;

2、 In terms of efficiency , If the input cost is considered / Produce , It doesn't improve my testing efficiency much , But if it is a script development and maintenance , Many people use , That's different ;

3、Jenkins It is not so convenient to execute use cases on , Often look dizzy .

Only after I really participated in the use of our automation did I realize , There are many imperfections in our automation , Then I finally know , The next step is to know the direction of adjustment .

  The way of career transformation , How can I get there ？

My path to automated testing , I can't leave the plan of each stage all the way , Because I like planning and summarizing , therefore , My friend and I spent some time to compile the following 《 Automatic test engineer learning route 》, Also sorted out a lot 【 Network disk resources 】, Friends in need can At the end of the article, you can get the link of online disk for free . I hope it will bring you help and direction .

One 、 First learn a programming language , Suggest python

Two 、Python Automated test framework application

3、 ... and 、 Automated testing - Web UI automation

Four 、 Automated testing - Mobile UI automation

5、 ... and 、 Automated testing - Interface automation testing

6、 ... and 、 Automated testing - Continuous integration Git、jenkins、Docker

7、 ... and 、 Automated testing - Performance testing LoadRunner、jmeter、app performance

8、 ... and 、 Automated testing - WEB Security testing 、 Penetration test 、 Vulnerability scanning

Nine 、 Automated testing - RobotFramework、AirTest

10、 Test and development - Automated test platform development

11、 Internet high salary test to expand knowledge 、Redis、MongoDB、Nginx Cluster practice

​ The above is a knowledge architecture diagram of the development direction of automation test engineers I sorted out for you . I hope you can follow this system in 3-4 The construction of such a system will be completed in three months . so to speak , It's a process that's going to kill you , But as long as you get through it . Life will be much easier in the future . It's just that it's hard at the beginning , Just take the first step , You're halfway there , When we look back on this journey after it's finished , You're bound to feel a lot .

Here's a message for you ：

Make yourself stronger ： Think about it , If you want to keep doing it in the testing industry , Your experience and testing skills are far from enough , You need to advance , You need to enrich your technology stack ！ What are we waiting for? ！

Last

I began to transform myself 2010 To really understand the of Automation 2014 year , And then all the way to automation , Transform into devops Now 2017 year . There are many detours in the process , Stepped on a lot of pits , Contact with various companies and projects ： Small to start-ups , Big to multinational companies , foreign , domestic investment , A joint venture , Outsourcing , Project outsourcing , E-commerce website , online finance , Cloud computing platform . Mainly in four languages , More than a dozen tools , I've seen all kinds of historical frameworks 、 Tools 、 platform , Written large and small class libraries 、 Tools 、 Modified platform . Although I only work 9 year , But instead 7 Sub unit , There are so many tears ...

A little help

Finally, thank everyone who reads my article carefully , Watching the rise and attention of fans all the way , Reciprocity is always necessary , Although it's not very valuable , If you can use it, you can take it

​ These materials , For those who want to advance 【 automated testing 】 For our friends, it should be the most comprehensive and complete war preparation warehouse , This warehouse also accompanied me through the most difficult journey , I hope it can help you ！ Everything should be done as soon as possible , Especially in the technology industry , We must improve our technical skills . I hope that's helpful …….