A cigarette of time to talk with you about how novices transform from functional testing to advanced automated testing

Preface

   In order to learn automated testing, I added several automated testing groups , Communicate with many big cattle in the herd , Also communicate with many novices . Because I am also a novice in automated testing , Just want to summarize the problems encountered in the study of automated testing , I also hope that if there are children's shoes who want to learn Automation , You can read this article before you study , It may be helpful for your study . What I'm talking about below are all encountered by many novices in automation testing in the group , Technical , There are also problems about automation in work （ It's realistic ...）

Learning automation is not difficult

   Learning automation is not difficult ？ Automated testing is not difficult if you only use recording and playback for automated testing , This tool is used for automatic test of recording and playback （ for example Selenium Use SeleniumIDE） You don't need to know the code , You don't need to record it like a performance test, but also analyze and summarize it （ I don't think the most important thing in performance testing is the use of tools , Is the analysis of the test results , And give a reasonable performance optimization scheme ）. Some of this recording and playback can be for BUG Better reproduction of , There are regression tests, smoke tests . Then some novices will question , Recording and playback is automated , Writing scripts is also running Automation , Why do you have to write code ？

  1. The limitations of recording and playback are too great . Recording and playback is only an operation process or a business implementation process of a user . Take my practical work as an example , A customer's account can have multiple states （ normal , Report the loss of , Partial freezing , All frozen , Only charge but not pay , Pay or not …), If you want to test the business of accounts in different states , Do you have to record it many times ？ They are just different accounts , If you write your own scripts , Just get a data driver .

  2. From reason 1 We can see that , Recording and playback are just scattered case, As an automated test project , There is no good automated testing framework , Just a bunch of recording and playback case, Does such automated testing still have any meaning ？ If you have a problem, re record ？ The original intention of automation is to liberate repeated manual testing , Recording over and over again is also a useless repetition of work .

  3. There is a good testing framework for scripting , It can enhance the business logic of the test , More closely connected with the various needs of the business , Better improve the collaborative work between business requirements personnel and testers .

   As can be seen from the above , Just using recording and playback for automated testing is simple , But the effect is not so good , Like our company also uses testwriter Conduct automated tests , The actual effect is not very obvious . That raises another question ： Why automation is done , It's tall ？ The head of the Department will do whatever he asks ？ Solve the first problem first ..

   So what's the difficulty in writing automated scripts ？ As a developer, it is not difficult to test … Don't spray don't spray , But as a novice without development experience and code experience, is it difficult to write automated test scripts ？ It's not hard to ！！！ From my own point of view , I learned it Python, But I do java A script written by ,Python I learned it myself . Let's look at what development languages are needed to write automated scripts .

   This is my study of automated testing Selenium Books and materials for reference , Of course, from a development point of view, this stuff is not enough to plug the teeth , For people who have no language foundation , The learning of these things （ The above classes every night 2-3 For an hour of study , Don't tell me you can't squeeze out time for study ） Up to one month . Pay attention ！！！ I often see novices in the group asking , How can this line of code make mistakes , How could this report be wrong , How can I report an error according to the code I found on the Internet , This is one reason , The language foundation is not good or there is no language foundation to forcibly write scripts . I can't even understand the most basic grammar , How to write high-quality code , Writing code is not like learning how to use a tool , Using the tool, you can directly take a case to run , Learning while using , Practice makes perfect , But the code is different , Don't understand the most basic grammar , Is it useful to vaguely know what this line of code is ？ Just change the scene , Another logic will deceive you again . So don't rush for success , You must master the most basic language foundation , It's best to do some auxiliary exercises after learning one thing , The code is typed , No, I will .

Why do you do it automatically

   Why automation is done , It's tall ？ The head of the Department will do whatever he asks ？ A group of friends often say , Alas, automation has been working for a long time, but no problems have been detected , The boss took me ; Oh dear , Our boss said that automation is very powerful. Let me learn to do it ; Oh dear , Can this automation replace manual testing , Can you write scripts to execute various test cases ？ When learning automation, some children may have seen some Daniel say what kind of projects can be automated , But there is a vague concept , Through these questions, we can directly reflect what we can and must recognize ： To do automation, you must know why to do .

1. Consider whether the project is suitable for .

2. Realize that automation and manual testing are not contradictory , Not who can replace who .

3. Automated testing is generally used for regression testing and smoke testing .

The above three points can solve the problems of the small partners in the group , Even if the head of the department asks you , You can also say that .

How novices do Automation

   How novices conduct automated testing . Just one sentence. , Learning is gradual , No matter how long your leaders ask you to start Automation , We should learn step by step , Don't use lack of time and pressure as an excuse . I'm not happy with novices who ask the most basic questions in the group , A blind bear breaks a stick , No one wants to run if he can climb , It's not solid to learn like this , It will not go well . To learn Selenium For example

1. Learning code

2. Study SeleniumAPI（ Is a testing framework that encapsulates many methods ）

3. Learn how to build automated test projects …

No learning heart , It's hard to do anything , These are some of my roast and feelings , Not to complain quickly ...... If people have no dreams , What's the difference between that and salted fish ！！！