Technology Sharing

한어Русский языкEnglishFrançaisIndonesianSanskrit日本語DeutschPortuguêsΕλληνικάespañolItalianoSuomalainenLatina

As a test, it is not only necessary to find problems, but also to actively promote effective solutions to problems from the user level;

1. First, you need to actively and patiently communicate with the developers and work together to reproduce the bug. Provide the test environment, operation steps, test data, screenshots, logs, etc. to ensure that the developers have a full understanding of the bug and can better understand and locate the bug.
2. Secondly, confirm whether the bug exists only in the test environment due to environmental factors or dirty data in the test environment, and RD cannot reproduce it in the development environment; demonstrate it to RD in the test environment, and if it is a valid bug, follow up and improve it; if it is an invalid defect caused by dirty data in the test environment, close the bug;
3. The understanding of requirements between testing and development is different or unclear, which leads to the developer considering it as an invalid bug. Due to the ambiguity of requirements, it needs to be confirmed with the product.
4. Development thinks that testing is over-testing, and users will never operate in this way in the real environment; from the user's perspective, the tester thinks that it is a valid bug; at this time, it needs to be confirmed with the product; if the product confirms that it is a valid bug, the tester can follow up; if the product thinks it is an invalid bug, but the tester thinks it is a valid bug, feedback is given to the direct leader and progress is made;
5. If there is no corresponding requirement for the bug, you need to communicate with the PM and RD simultaneously, and the PM should clearly state the specific requirements of the requirement and the time node for solving the bug;
6. If the developer believes that the problem is caused by the development tools, development framework, or third-party interface, the tester needs to actively communicate with the developer and coordinate with relevant personnel to jointly solve the problem.
7. The bug is sporadic and cannot be reproduced, so the developer does not recognize it. If you cannot reproduce it, try to provide detailed problem information (screen recording, log information, screenshot information). If you cannot reproduce it again, submit the bug to the defect management system for subsequent observation and tracking (mark as sporadic);