Knowledge System that testing engineers should possess

1. Master Basic Testing Theory
Although it seems to be the simplest step, as a stepping stone for job testing,

Its position is particularly important. Moreover, with the accumulation of project experience and the gradual improvement of personal abilities, we gradually realized that these basic skills are the essence of martial arts and the shortcuts that our predecessors have summed up after numerous detours. A seemingly plain definition or technique. If you can switch from a guild to a god club, you may be able to get twice the result with half the effort in your project.
Basic theoretical scope:
(1) definition, goal, purpose, and common sense of the test (the previous interview is required, and common sense is a secret of Martial Arts)
(2) Division of testing technology (the technology is divided from different perspectives. Do not simply think of them as Western food. Everyone is equal. Everything is used, maybe some of them belong to another test. This is the core of future work. We should not only understand what they do, but also what their core is and what types of software are often used for testing)

2. Standardized test process
The process is relatively simple, similar to design, execution, and other things, such: design Test Plan --- Develop test cases --- execute test cases --- submit defect report --- repair Software defects --- Test summary analysis (there is an arrow to fix Software defects to execute test cases, this stage is post-repair regression testing)

Isn't it easy? Why design so many steps? After the program is completed, can it be executed according to the customer's usage steps? (If you have such an old idea, you can't keep up with our modern new society. But you don't know what to do now? Thieves say that the robbery is not technical)
From the perspective of software engineering, how to organically combine it with the software life cycle is the key. Otherwise, you will always think that it is unnecessary to start other stages of execution. (Many companies only do
For system testing, you only need to develop a test plan and use cases throughout the test lifecycle. Standardized companies follow the unit-integration-system-acceptance steps, therefore, each stage must follow the instructions
Rows)

3. Test the document content of each phase
What do I need to do in each phase of testing? What is the basis? How can we evaluate the quality of software and the quality of testing?
All of this depends on the four sets of documents generated during the test lifecycle (Can you infer from them ?)
Test Plan (prepared by test Manager), test case (prepared by Case Design Engineer), bug report (prepared by case execution Engineer), Test Analysis Report (prepared by test Manager)
The core of each document is different. Documents corresponding to their responsibilities must be clear about what points should be paid attention to and what technologies should be mastered. Remember, they may be a direct factor for your promotion or resignation.
I personally think that this module is the core and most practical part of the four modules, but it must be built on the master of the first two knowledge modules and understand the Industrial Background of the tested program. (Otherwise, the documents written are only an ornament and there is no actual guiding value. The first two documents must be strictly reviewed because they are the only basis for testing and directly affect the efficiency and quality of testing)

4. Use and principles of automated testing tools
As the development direction after testing, automated testing has become a target that many people blindly pursue.
Because many companies have to master XXX software in their recruitment information, or have heard that xxx software will receive a high salary, it will play an important role in the company ...... A lot of people spend a lot of time on a very popular testing software before they even have a solid foundation, but I want to advise you: to learn martial arts, you must first start from the horse.
(1) A tool is a powerful tool, but it is not a necessity. The entry and mastery are not at the same level, and the skill is not reached. Even if you get a good sword, you do not know how to dance. Why is it best to use this tool with such a function? A real expert knows that a series of test cases designed before the tool is used are the most important.
(2) The tool is selected based on the software to be tested and the software with long-term changes to the requirement and interface is not suitable for the recording and playback function testing tool. Therefore, various companies purchase corresponding testing software based on their own products. One day, you may find that things you spend a lot of time learning cannot be applied to your actual work. You may feel sorry, and the most painful thing in the world is nothing more than this.
(3) The idea of a tool is the same as that of a test. With a solid foundation, you can learn and understand the essence of each tool more quickly. After understanding the standardization process of the test, the use of TD is a small case. The sword in the hand can be used as desired.

Therefore, we hope that you can differentiate the primary and secondary components. Among the four modules, it is the most professional, but not the core. It is recommended that you do not spend a lot of time on them before learning software testing, unless required by work. (From
Automated Testing is really important. It not only makes the testing work convenient and fast, but also some tools can achieve the hard-to-achieve Goal in reality, saving a lot of manpower and material resources. It will certainly become the core development direction after testing.
The more you come, the more companies you are sure. I hope you can learn more about some testing software related to your industry when your capabilities are ready and you have time to do so)