1. What is the testing process?
Recently, this project is relatively complete because when I went there, I followed it from the beginning. At that time, we had a project establishment meeting, and then our team leader wrote his test plan, and then he divided us into modules and assigned them to the project. Schedule, and then design his first round, second round, and third round of tests, the scope of his test, and then after he assigns us modules, I have to think about his test points, and then what to do Write test cases and then we also go to review. Start its round of testing. After the development team submits the code, we first conduct a smoke test to test one of its main functions. Then the first round is mainly to solve one of its serious functional problems. The most common bugs are crashes or severe lags. The main purpose is to solve these problems. In the second round, these will be covered. In the second round, the main purpose is to solve one of his lags and some functional bugs. , then for the third round, we mainly do a regression test of it
2. How to design test cases?
As for test cases, we generally determine them based on product requirements. For example, in my last company, our test cases include test numbers, test modules, test steps, expected results, test results, etc. Of course, they can be further detailed. We consider many factors, such as a registration function, what needs to be verified for product requirements, user name, password, email, etc. Of course, we will also take into account the habits of ordinary users using software as well as some special situations and extreme situations. Condition. Moreover, the test cases must be representative, targeted, and reproducible, because if the bug we detect cannot be reproduced, it will be meaningless. Generally, we will use the equivalence class division method, boundary value, and scenario method. , waiting for some test methods to set different scenarios, different scenarios will have different operations. You also need to indicate the software and hardware environment, such as whether you are mac or Windows, pc or mobile. These environmental information must also be taken into consideration. There is also the design of test scenarios. This is a special part of performance testing. For example, the use case specifies the number of concurrent users, specifies the pressure method, whether it is random, one-time startup, or gradually increasing, and specifies the load test time, whether it is 10 minutes or 1 hour. This information should also be included in the use case.