For people who want to do automated testing

Contacted a lot of peers, because they have been doing manual testing, it is now very urgent to do automated testing, of which no lack of work for more than 5 years of people.

To automate, you first need to look at some of the common problems with automated testing:

Automated testing of some problems

2. What is automated testing?

   Automated testing, as the name implies, automatically completes the testing work. Automated testing is the test process through some automated testing tools or self-made wheels that enable manual point/write work before simulation and verify the results to complete the entire testing process. Automated testing, it looks beautiful, it feels like the first industrial Revolution, it has created a machine instead of manual labor of the era, but it is not. Because every case of automated testing is done from manual testing, without the foundation of manual testing, automated testing is impossible.

4. Why automated testing is needed

   Why automated testing starts with the benefits of automated testing and the cost of human-testing: A. Automated testing cost savings (according to project)       after all, automated testing is really liberating a group of people (the cost of labor is the biggest cost of IT companies), can let the machine to perform some repetitive work night and night. B. Some test projects are difficult to achieve manually (high manual costs)       such as 12306 of stress testing, load testing, and find so many people to test unrealistic can be simulated by the machine.    

6. Advantages and disadvantages of automated testing

   advantages To prevent testers from getting bored with repetitive work   improve test efficiency   ensure consistent and repeatable testing every time   the use of unattended time   to do some of the testing shortcomings  of manual System development time may not be shortened  without manual testing to find more defects

8. What kind of project is suitable for automated testing (dev hand shaking, auto busy)

    project is small, long cycle, project resources are sufficient (automation is not a person to complete, need a bunch of people long-term maintenance) 
    Example: 
    Internet projects, a week to go online, You do not go online others on-line people do not need you, the project cycle is short, change fast, you have not done automation, the project may be offline. For example, a treasure double 12 activities related projects, within a week on the offline. 
    Suitable for automated testing projects, such as a treasure client, each release, most of the functions are unchanged, and within 3-5 years the project will not go offline, this is more suitable for automation. 

    

10. What kind of person is suitable for automated testing?

     this question is for the people who want to do automated testing, perhaps you think the threshold of software testing is very low, as low as anyone can do, casually point on it, the industry is too cheap, so you want to do automated testing, improve their own force lattice, I would say that manual testing is not low, if let a do not understand, A bit of business-based people do not have to test, can you measure the problem? Do not neglect your business knowledge reserves. The accumulation of your business knowledge reserves can make you an irreplaceable industry expert, and the Code of automation is replaced by small meat because of an era of change. Pull so much, exactly what kind of person can do automated testing? My understanding points to a few points: a. Have the ability to master a development language, Java, Python, Ruby, C # B. Familiar with the tested system like you're a Web test, you have to understand JS, CSS, HTML, XPath. You are a mobile test, you have to have the foundation of Android Development and iOS Development Foundation, will debug app you are familiar with the C/s test you will be well acquainted with TCP, IP protocol c. Mastering a set of automated testing frameworks (tools) such as Selenium/appium nunit/testng ro    Bot Framework/cucumber D. Good at learning, to know it is the reason why it industry changes too fast, every once in a while there will be a number of emerging things, will appear the original very fire things gradually decline, who can not predict.    Once Nokia or mobile overlord, rely on Saipan eminence, but do not think enterprising, end up a prostitute to survive. Once QTP very fire, once selenium also very fire, now Appium also very fire software industry from desktop software to Web side, and from the Web to mobile end, who do not know what the next. And we as the software industry practitioners, not because of the fire of things are not fire and let themselves down, a person's core ability is learning ability, if you are good at learning, you do not have to worry about these changes, because you can move without pressure, selenium principle you mastered,        Learning Appium is a piece of cake, because Appium is using 
     Selenium webdriver protocol. If you can know the reason why, you can also build wheels, transform appium, after all, many functions need to be perfected. If you have not reached the above points, it is recommended that you do the manual test it. 

     

12. If you have a code base, how do you want to engage in automated testing to learn?

    Many beginners very tangled, learn QTP or learn selenium my advice is to learn selenium, open source, free, you can download the source research, to understand its principle, and now selenium not too much information, random search a lot of, learn more relaxed. Not recommended to learn Selenium IDE recording, of course, you can record some and then convert to the corresponding script to learn, and so you learn selenium, then to learn appium you will have a natural déjà vu. Why not suggest learning qtp/uft? Because the fees/bloated/Now do the desktop software testing work is not much. About buying books, not recommended to buy books, many books are outdated, and quality slag, you bought those books in the code has not been used, if you really want to learn, go to the official website to find example, to the corresponding community and group exchange, or directly see api/source code.

Summarize:

New Learning Automation test to:

• • Mastering a door development language
  • To master some basic knowledge
  • Buy less books, look at the document of the test framework, and go to the community exchange more
  • Keep learning, improve your ability to find problems, solve problems (do not reach the party, do more hands)

For people who want to do automated testing