1. Understand the writing method of test case , there are normal use cases that fully cover the requirements, and there must also be abnormal test cases, and there must be complete expected results; the test cases must have priority;
2. A clear understanding of the requirements background, requirements purpose, relationship between upper and lower levels, and the boundaries between input and input;
3. Having a sensitive sense of touch, understanding the work habits of cooperative development, code style, first Time to discover possible errors;
4. Have good learning ability, learn and understand unknown knowledge as soon as possible, and do not let go; have reading and basic writing skills for the code;
5. Be responsible and complete the work you hand in hand within your own ability. After making mistakes, learn from experience and lessons. Do not make the same mistake twice;
6. Good communication skills, that is, you must communicate with needs and understand the needs and confirm the bug with development. Try to persuade development and modify the bug that he thinks is not a bug;
7. Be sensitive to the industry, see changes in the industry, and actively introduce it into our system;
8. When testing, you must use and observe the system from the perspective of the user, and make the system into something that most people can use, rather than just A few people can use it, especially when the users are ordinary people;
9. With a mentality of resisting pressure, testing is often the last level of release. Many people feel that the pressure of testing is low before entering, so they want to do the test, but in fact, testing is the last level of quality. It must be able to resist and start to resist;
10. To form your own efficient and high-quality testing system, you must report and solve problems as soon as possible to reserve more testing time. ;
11. Find fun from boring and repetitive labor. Testing is never a single repetition. What seems to be repeated actually contains infinite bugs.
