Learning route from manual test to NB automated test

Learn two tools before you start
Commercial Web Automation testing Tools please learn QTP;QTP learning can be skipped, I skipped.
Open source Web Automation Test Tool please learn selenium; I was the first to learn Watir, and then learn Selenium

Here are some of the things you can distinguish between the reader and the average rookie, and these are the two tools that have been interspersed with the above:

Basis:
1. Browser front-end related to the simple technical basis: what HTML, XML, CSS, JavaScript, and so on, see the Web site tutorial
http://www. w3schools.com/
2. Learn to use a unit test framework or called Test actuators, suggest testng, Finish testng, you should have 3 hours to learn any test executor ability, I used to have Testng/junit/nunit/ruby unit Test/python Test Unit/visual Studio Testing actuator, etc.;
http/testng.org/doc/documentation-main.html
3. Learn the basic grammar of a language:
Static language recommendations Java, dynamic language suggested Python, only need to learn basic grammar, generally within three months can be completed. I learned some ruby, groovy, shell scripts and so on by the way.
4. Learn about the use of one or two version control tools:
SVN and git; I learned Hg by the way, but not many people use it now.
As long as the use, very simple, please find your own information
5. Learn Page object design mode:
Selenium official website There are examples, extremely simple; it took a day or two to understand the design pattern. It took me one months to rewrite a full set of regression test cases for a site using this pattern.
6. Learn how Jenkins is used:
As long as the use, very simple, please find your own information, this is about to spend an afternoon time.
7. Learn how to use automated build tools:
Learn at least Ant and maven; This is a learning testng, and it just needs to be applied in a simple way.

Improve:
1. How the Browser works:
How Browsers
http://taligarsiel.com/projects/howbrowserswork1.htm This is heard to have Chinese translation, find it yourself.
2. Learn about a keyword-driven test actuator, recommended robot
Robot Framework has the basis of the previous, this probably learn an afternoon can be easy to master, in-depth mastery of the official documents.
3. Learn about a BDD business-driven test executor, recommended Cucmber
Cucumber individuals have reservations about BDD and have testng fundamentals for about one or two afternoons (this is in Ruby, and I'm assuming you're learning ruby grammar by the way). In addition I spent one or two afternoons looking at JBehave (Java), Spock (Groovy).
4. Learn the simple use of several databases:
Mysql,mongodb; This w3cschool has a tutorial. Find it yourself. I haven't actually seen it yet.
5. Learn the simple use of the server-side operating system:
Linux,unix and shell scripts and the like, this is a time-consuming and recommended series of Linux private dishes for brother Bird.
6. Learn about other business tools or automated testing tools
The principle is similar, there are about dozens of kinds of can learn, but all the same. This I can find all over the Internet to see, probably looked at dozens of kinds of it. Some of them are very exotic products such as fit and fitness
7. Continue to expand learning various development frameworks, network protocols, etc. If you want to go to a giant internet company to do test development, Learning This is just the beginning, which is why transformation to do full-time automated testing, test developers for many manual testers is so difficult.

Of course, the test development of internet companies in front of a lot of things can skip not learning. Some people skip too many things, will develop a variety of wonderful test framework/tools, but he can do this position anyway.

8. Expand to other directions such as app automation, performance, and more. If you want to go to the new start-up Internet company to do test development, app automation must learn, but there is the basis of the previous, learn this easy.

Other optional knowledge (the main purpose is to brag, to teach others, to write the article blow):

1. Black box test theory; one week introductory, three months proficiency. Most people learn three months is enough. The students who feel that they know well are actually aware that you are not very understanding. Because this piece dug deep enough to dig up a lot of magic, but to find a good job is not much use of theoretical knowledge. It is recommended that you go to the architect's level to learn more about these theories in order to give people a better lecture and a great blow.

2. White-box test theory; This advice should be understood a little. For example, the pile-driving ah, coverage ah, tools can learn sonar, and try to work with Jenkins, integrated into a small project. It doesn't matter if the tools are not learned because few companies use them. A month to master. But generally in the foregoing many things learn by the way.

3. Automated test theory; This n-many people don't really understand. Like, you talk to him. Data-driven, business logic, and test implementations are separated, False alarm false positives, and so on. He doesn't know what you're talking about. But such people can also do automated testing, test development, so this is optional. I suggest, of course, that we should have. By the way, you can look at the error calculation method of the automated test ROI (because most of the computational methods are wrong), the difference between automated testing and manual testing, and so on. What else is the model-based automated test design theory, the orthogonal design method, and the similarities and differences between the fully paired (Pariwise) design methods, etc. These lessons can then be used to brag about Shong to others.

4. Test management theory, project management knowledge: You learn if you do not have the opportunity to do management. You can also take a seat in management if you don't learn to have a chance.

Learning route from manual test to NB automated test