Before the transformation is successful, we must first
teach ourselves two tools. Commercial web automation testing tools, please teach yourself QTP; QTP learning can be skipped, I skipped it.
Open source web automated testing tools, please teach yourself Selenium; I learned watir first (1 week), and then selenium (also 1 week).
Here are mainly some things that can distinguish readers from ordinary novices. Please learn these interspersedly with the above two tools:
Basics:
1. Simple technical basics related to the browser front end: what are the html, xml, css, javascript, etc., see the w3c tutorial website
http://www.w3schools.com/
2. Learn to use a unit testing framework Or called a test executor, it is recommended to testNG. After learning testNG, you should have the ability to learn any test executor in 3 hours. I have used testNG/Junit/Nunit/ruby unit test/python test unit/visual studio Test executor, etc.;
http://testng.org/doc/documentation-main.html
3. Learn the basic syntax of a language:
static language suggests java, dynamic language suggests python; only need to learn basic syntax, generally three It can be completed within a month. I learned some ruby, groovy, shell scripts, etc. by the way.
4. Learn the use of one or two version control tools:
svn and git; I also learned hg by the way at that time, but not many people use it now.
Just use it, it's very simple, please find the information yourself
5. Learn the page object design pattern:
The selenium official website has examples, which are extremely simple; it took a day or two to understand this design pattern. It took me a month to rewrite a full set of regression test cases for a website with this model.
6. Learn how to use jenkins:
as long as you use it, it's easy, please find the information yourself; this will probably take an afternoon.
7. Learn the use of automated build tools:
at least learn ant and maven; this is handled by the way when learning testNG, only simple application is required.
Improve:
1. How does the browser work:
How browsers work
http://taligarsiel.com/Projects/howbrowserswork1.htm I heard that there is a Chinese translation for this, so please find it yourself.
2. Learn to understand a keyword-driven test executor. It is recommended that robot
Robot Framework have the previous foundation. This can be easily mastered in about an afternoon, and it can be mastered in depth and familiar with official documents.
3. Learn to understand a BDD business-driven test executor. It is recommended that Cucmber
Cucumber personally have reservations about BDD. There is a basic study of testNG for about one or two afternoons (this is using ruby, I assume you learned ruby syntax by the way) . In addition, I spent one or two afternoons looking at JBehave (Java) and Spock (groovy).
4. Learn the simple use of several databases:
mysql, mongodb; this w3cschool has tutorials. Find it yourself. I haven't actually watched it yet.
5. Learning the server-side operating system is simple to use:
linux, unix and shell scripts, etc.; this is more time-consuming, I recommend the linux private kitchen series of Brother Bird.
6. Learn other business tools or automated testing tools. The
principles are similar. There are probably dozens of them to learn, but they are all the same. I've checked everything on the Internet on and off, maybe dozens of them. There are many wonderful products such as fit and fitness
7. Continue to expand and learn 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; this is why it is so difficult for many manual testers to transform to become a full-time automated tester and test developer.
Of course, many things before the test development of Internet companies can be skipped. Some people skip too many things and will develop all kinds of weird testing frameworks/tools, but he can do this job anyway.
8. Expand to other directions such as app automation, performance, etc. If you want to go to a new startup Internet company to do test development, you must learn app automation, but with the previous foundation, learning this is easy.
1. Black box testing theory; one week to get started, three months to master. Most people learn it for three months. Students who think they know well actually need to know that you still don’t. Because this piece of deep digging can dig out a lot of magical theoretical knowledge that is not very useful for finding a good job. It is recommended that you go to the architect level to learn these theories in depth in order to better teach people and brag.
2. White box testing theory; this suggestion should be understood a little bit. For example, pile driving, coverage rate; tools can be self-taught sonar, and try to use it with jenkins, integrated into a small project. It doesn’t matter if you don’t learn the tools because few companies use them. Can be mastered in a few months. But generally when you learn many things mentioned above, you can master it by the way.
3. Automated testing theory; this number of people actually don't understand it at all. For example, if you tell him a proper term for automated testing such as data-driven, business logic and test implementation separation, and false alarms, he doesn't know what you mean. But this kind of person can also do automated testing and test development, so this is also dispensable. Of course, I still recommend it. By the way, you can look at the wrong calculation methods of automated testing ROI (because most of the calculation methods are wrong), the difference between automated testing and manual testing, and so on. What are the similarities and differences between model-based automated test design theory, orthogonal design method and pariwise design method, etc. After learning these, you can use them to brag and teach others.
4. Test management theory and project management knowledge: you can't manage if you learn it without a chance. If you don't have the chance to learn, you can sit in the management position.