Often encountered testers do not know what to learn, or learn a thing do not know if there is no use. In fact, I also often encounter similar problems, so I also want to put the knowledge I learned to classify. I think that as long as these types of knowledge, you learn nothing wrong, always useful.
1. Product Knowledge: For the products you have tested, you must be very familiar with them. Small to the module you test, large to the entire product architecture, internal implementation, code, and so on.
2. Testing Knowledge: Black box testing, white box testing, manual testing, automated testing, performance testing, safety testing and so on.
3. Development knowledge: Programming, data structure, algorithm, debugging and so on.
4. Expertise: Above 2, 3 is the basic knowledge, you should also be proficient in some of your work more specialized technical knowledge. For example, if your product is based on. NET, you should be proficient in. NET, or similar to the Java EE and so on. (for example, I should have mastered the WIN32 system programming, Windows kernel, WDM, etc.)
5. Domain knowledge: You should be proficient in the field of your work, such as mobile phone field, database field and so on.
6. Industry knowledge: You have a clear understanding of the overall state of the computer industry, new technologies, dynamics, and trends. (For example, I am concerned about Web2.0, cloud computing, etc.) in addition to my field.
To remember, you first is a computer talent, followed by a software talent, again is a test talent, finally you are a Sqaa, Sqae, STE, Sdet and so on. To be an advanced tester, the knowledge of this line needs to be mastered.