1. What is the test case?
The design of test cases is how to cover all the states of the software, that is, a series of orderly and controlled state change processes when the software is running under a set of input/output conditions.
2. Is it necessary to design a use case?
Record the test content to avoid the omission of some test points during execution. In addition, it is convenient for use case review and use case summary, which can improve the later test work. Therefore, test cases must be written, and the granularity can be changed according to the situation. Certainly, for projects with a small number of testers and a tight launch time, a mind map can be used to load out the test points.
3. How to write test points?
According to the requirements and design interactive draft, first list the function points, and then expand the function points as test points (as the title of the test). When necessary, use the power of product, development, and back-end to ensure the coverage of use cases and learn to borrow.
Test points (Note: This is not a test case, the use cases are generally more detailed, and development may not take a lot of time to do self-test) After writing, you can send it to the development for self-test, and some missing points can be recorded and recorded during testing. supplement.
4. What are the benefits of designing use cases?
The process of designing use cases allows you to have a deeper understanding of requirements, be familiar with each function point, ensure that each test point is covered as completely as possible, and it is also convenient for use case review.
5. What are the test methods for test cases?
Equivalence class division method, boundary value method, function map method, error speculation method, cause and effect map method, scene method.
6. How to ensure the coverage of use cases?
First of all, you must be familiar with requirements. Requirements analysis and disassembly are very important. You need to be familiar with the parts of the process that you don’t understand or have questions. You must find products to communicate in time to determine the results. Secondly, during the project development process, the test cases in each phase are It is better to summarize, learn to summarize, and ensure that there are as few leaks as possible. In fact, this is related to testing.
Thinking is closely related, the accumulation of work experience, and the formation of test thinking will help you design a more complete test case.
7. After the use case is written, what should we do first?
First self-inspection, after the self-inspection, list the points that still have doubts. Before the review, send the use cases to the relevant developers and products in advance, reserve time to tell them to look first, and conduct the review at a unified time.
8. Who should participate in the use case review?
product. Development (client, back-end, front-end, etc., the situation of each company is different, you can come according to the actual situation), the test needs to be reviewed together with the use case, the review needs to be increased, not just going through the scene, there must be output, otherwise there will be You may not appreciate the role of use case review. If you don’t pay attention to development, you can review the use cases with the R&D director. Every time I review the use cases, people in different positions on the product can raise issues that are not included in the relevant use cases, and the use cases need to be re-adjusted. Finally, in the second review, in the review process of the use cases, you can simply record the questions raised by everyone, and then make detailed supplements after the review. After the first review of the use cases is reorganized, the relevant parties will be notified again Participants of the review, the purpose of this is to tell everyone what we have done, what is the result of doing it, and what improvements can be made in the follow-up. It is summarized in time and the goal is clear, which can drive everyone to participate actively.
9. Is it necessary to read the use case review item by item?
Use case review does not need to read the title and expected results one by one. This is a waste of time. For example, there are hundreds of use cases after sorting out a project. If reviewing one by one is time-consuming, it is recommended to summarize the results according to the conditions. Most use case results It is known, and the steps and expected results are not necessary. Unless there are individual test points that are in doubt, you can spend time discussing and communicating together (recommendation: use mind maps to explain use cases, and refer to use cases for some special points get on).
10. What should we do if the development is not self-testing?
It is recommended to join the test-promotion link, the test will give the test standard, return it if the standard is not met, or perform the main process acceptance of the product (design to accept the UI), the product says that it has passed the acceptance and then the test will be submitted for the test. Testing can be promoted from top to bottom, and joining a certain link also requires the support of the technical director. The development of self-test can make testers easier, some easier to find problems can be avoided when entering the tester testing phase, which saves time as a whole, and the test also has more time to test complex logic problems, rather than just At the same time, put a little pressure on the research and development, and the quality of the developed functional modules will be improved. Repeated failures of the test can also be used as a standard for research and development assessment.
Written at the end,
if you are interested in python automated testing, web automation, interface automation, mobile terminal automation, interview experience exchange, etc., you can follow the WeChat official account: [Programmer Erhei] to get an interview with a software test engineer data! My learning exchange group: 785128166 There are technical experts in the group to exchange and share~
If the article is of interest to you, please reach out to make a fortune and give me a like. Thank you for your support. Your likes are my motivation for continuous updates.