The ultimate pursuit of testers is zero bugs. How can we have zero bugs? We can operate from the following aspects:
1. Study business requirements and refer to competing product requirements
In the requirement review stage, product managers, developers, testers, and DBAs generally receive a requirement document or prototype diagram before the review meeting.
Before the review meeting, our testers must carefully study the requirements or refer to competing products, mark them well, and mark the unclear, ambiguous, or incomplete content when the product manager organizes a meeting to explain the requirements. Ask questions where you understand and record them carefully.
2. Use case quality control
For the quality of use cases, in-depth analysis of the object under test, subdividing functions, covering all test points with requirements, supplementing abnormal test points, and reviewing complex modules.
Fully understand the principle of technology implementation, architecture and dependence on the platform, etc. In-depth understanding of user groups, analysis of various scenarios of user use, design of test cases from the perspective of users, and making certain judgments on user experience.
Design the priority of test cases, use professional testing tools to filter test cases according to priority, and use different colors to identify the corresponding priority, whether it is review or execution, you can check in this way. Whether it is a smoke test case or a functional test case, it can save a lot of time.
Control the granularity of test points -- from coarse to fine, using tools to assist, sort out the test requirement framework from a large aspect in the first pass of requirements collection; in the second pass of requirements collection, start to subdivide each test point; When refining test points, common test cases that have been written before can be applied.
Test cases are updated in a timely manner. From the perspective of the entire test process, whether it is the requirements analysis stage, the development stage or the test execution stage, there may be changes in requirements. At this time, the test points we sorted out in the early stage need to be updated synchronously in a timely manner.
现在我也找了很多测试的朋友，做了一个分享技术的交流群，共享了很多我们收集的技术文档和视频教程。
如果你不想再体验自学时找不到资源，没人解答问题，坚持几天便放弃的感受
可以加入我们一起交流。而且还有很多在自动化，性能，安全，测试开发等等方面有一定建树的技术大牛
分享他们的经验，还会分享很多直播讲座和技术沙龙
可以免费学习！划重点！开源的！！！
qq群号：110685036
3. Use case review is critical
During the use case review, the testers explain the requirements in combination with the use cases, explain the understanding of the requirements, and then explain what content is covered in their test cases, and the product personnel and developers will point out whether there are missing scenarios. This reduces missed scenes.
4. Cross-testing or internal acceptance testing is necessary
Everyone's thinking is different, the problem is considered and the perspective of the station is different, so the testing methods will also be different. If conditions and time permit, you can exchange modules with other colleagues in the same project team and test each other.
5. Effective regression testing
While conducting this main business test, it is also necessary to sort out the impact of the business on the previous business. As long as there is an impact, it will be regressed in full before reassurance. Of course, for the sake of efficiency, regression testing is not required for areas that are not affected after evaluation.
(All the above pictures come from the Internet, if there is any infringement, please contact to delete it)
6. Risk analysis of legacy bugs
In the test report before going online, there must be a risk analysis of the remaining bugs, mainly explaining which BUGs are unresolved, and whether there is any risk that these BUGs will not go online in this iteration. If there are other circumvention solutions, discuss with the product, development, and test managers.
7. It is very important to find the reason after the missed test
To deal with missed testing, we should first check whether the problem exists in the test environment, and then look at the process problem or technical problem? It is enough to avoid the same pitfall once more. It is impossible to avoid missing testing absolutely. What we can do It can only be to minimize the missed test phenomenon, and the missed test phenomenon will gradually decrease with the increase of work experience. For all those who want to learn to test, now is a very good time.
The following are supporting learning materials. For friends who do [software testing], it should be the most comprehensive and complete preparation warehouse. This warehouse also accompanied me through the most difficult journey. I hope it can help you too!
Software testing interview applet
The software test question bank maxed out by millions of people! ! ! Who is who knows! ! ! The most comprehensive quiz mini program on the whole network, you can use your mobile phone to do the quizzes, on the subway or on the bus, roll it up!
The following interview question sections are covered:
1. Basic theory of software testing, 2. web, app, interface function testing, 3. network, 4. database, 5. linux
6. web, app, interface automation, 7. performance testing, 8. programming basics, 9. hr interview questions, 10. open test questions, 11. security testing, 12. computer basics
Information acquisition method:
