In the process of software testing with TestWriter yesterday, I remembered the operation problems I encountered, but fortunately I can solve it myself. When I used QTP before, the biggest headache was to encounter some fatal defects, but I still reported it to the development to solve it, and the ability was limited. Positioning yourself is important. Then, for example, when using automated testing tools to test, test compatibility problems, data-driven aspects, and crashes, such as tasteless problems.
What to do, talk about encountering similar defects, find the root cause, and solve it very well. Share it here,
1. Problem classification
Encountered a fatal problem, stuck in one place and cannot continue, the essence is that there are too many defects in the test product. Identify the severity level of the defect to categorize the problem.
Blocks (fatal): The problem that more than 80% of users cannot use due to product functions or performance . For example: 1. Frequent crashes and restarts; 2. Loss or destruction of user data; 2. Seriously Huaping ; 3. Memory leaks, etc.
Circular (Critical): For example, some performance is very unstable, and there are frequent service interruption problems. For example: some operation problems, functional errors, etc.
Major (general error): Refers to some general problems that can be solved by other means.
Minor (minor bug): Minor functional defects, the following interactivity problems may occur, resulting in unsmooth operation.
Trivial (suggestive): some user suggestions such as usage habits.
Clearly state the severity of the various defects, and rank the problem.
2. Correctly report test bugs
Confirm the level and classification of the problems encountered. When encountering problems, testers must understand their own work, and the testers' knowledge of possible problems in the inspection program. They can use the correct bug reporting process to report the bug to the programmer. If a fatal flaw is encountered, it still needs to be reported to the person in charge, and the decision-making power is handed over to the leader and resolved through consultation.
Third, the perfect solution to the problem
It is what a software tester should do in the right situation. When encountering a defective problem, grasp the overall situation to complete the testing task.