1) First, divide the organizational structure of test cases
If the company's testing process is still standardized and complete, when conducting requirements review, testers should classify the structure of test cases according to requirements. If it is a relatively large management system, then test cases can be based on functional modules. Classify, such as:
If it is a game, it can be divided according to the scene, such as:
The idea of dividing the organizational structure of test cases is mainly based on the test entry point of the requirements document for reference.
2) Design test cases carefully according to function points
After the requirements review, the developers will submit their own design documents for review according to the requirements documents and the work they are responsible for. If it is a management module, firstly, the function of adding, deleting, checking, and modifying can be used as the first-layer function point, and then according to the non-empty judgment of required items and input format verification as the second-layer function point; if it is a report module, it can be used according to various Query conditions to extract function points.
After dividing the function points, you can use some test methods such as equivalence class division and boundary value analysis to write test cases, and you can mark them, which is quite helpful for the later test case sorting.
3) After a round of testing is completed, the test cases must be supplemented and sorted.
After a round of testing is performed, they will have a better understanding of the content to be tested, and developers will make some changes to the details of some functions during the actual development process. The written test cases are improved, mainly to modify the test steps and supplement the abnormal conditions, and improve the coverage of the test cases to the requirements, so that more bugs can be found.
4) After the test, summarize the test ideas according to the test cases
After the test is over, the testers will generally have a short leisure period after submitting the test report. During this period, they will look at the test cases that have been continuously improved by themselves. According to the annotations in the use cases, the previous test ideas can be very Sort it out in a coherent manner, and reflect on what areas are not considered enough. This is the accumulation of experience.
After doing these tasks, the tester can answer fluently according to the test cases written by themselves when the leader asks you what functions will be tested in the functional test, what conditions will be tested, and the approximate time required to execute a round of testing. . To paraphrase Guo Degang's words: People who do science are very rigorous. Everyone, as a tester with an ID card, can improve their own level only if they do their work carefully and rigorously.
1) First, divide the organizational structure of test cases
If the company's testing process is still standardized and complete, when conducting requirements review, testers should classify the structure of test cases according to requirements. If it is a relatively large management system, then test cases can be based on functional modules. Classify, such as:
If it is a game, it can be divided according to the scene, such as:
The idea of dividing the organizational structure of test cases is mainly based on the test entry point of the requirements document for reference.
2) Design test cases carefully according to function points
进行完需求评审后，开发人员会根据需求文档及自己所负责的工作提 交自己的设计文档来进行评审，测试人员可以参考设计文档中的内容提取出各个功能模块中的功能点来设计测试用例，如果是管理模块，首先可以将增删查改功能作 为第一层功能点，然后再根据必填项非空判断、输入格式验证来作为第二层功能点；如果是报表模块，就可以根据各种查询条件来提取功能点。
划分好功能点后，就可以利用等价类划分、边界值分析等一些测试方法来编写测试用例，并且可以进行标注，这样对于后期的测试用例整理相当有帮助。
3） 执行完一轮测试之后，都要对测试用例进行补充和整理
执行完一轮测试之后，都会对所测试的内容有进一步的了解，并且开发人员在实际开发过程中，会对某些功能的细节部分做出一些修改，测试人员应该根据变更和 熟悉程度对之前编写的测试用例进行完善，主要是对测试步骤的修改和异常情况的补充，提高测试用例对需求的覆盖率，以便能发现更多的BUG。
4） 测试结束之后，根据测试用例整理出测试思路进行总结
测试结束之后，测试人员在提交测试报告之后一般基本就会有一段短暂的休闲期，在此期间，再看看被自己不断完善的测试用例，根据用例中的标注，可以将之前的测试思路很条理地整理出来，反思有哪些地方考虑不足，这就是经验积累。
做好这些工作之后，在面对领导问你功能测试会测试到哪些功能，会测试哪些情况，执行一轮测试所需的大概时间问题时，测试人员就可以根据自己编写的测试用 例进行流利回答。套用郭德刚的一句词：做科学的人都是很严谨的。大家作为都是有身份证的测试人员，只有工作做得细致严谨，自身的水平才能得到提高。