Shulou(Shulou.com)06/03 Report--

We all know that a basic theory of software testing is that the earlier bug is discovered, the less expensive it is to repair. According to this basic theory, what we need to do in testing is to intervene in the product quality control process as early as possible and find software problems as early as possible. So the question is, what can we test engineers do to cut in and affect the quality of the product as soon as possible? My experience is to find and communicate forward problems through requirements review and feedback from the case design process.

So why does the title only mention the case design process and not the requirements review? That's because I think case design and requirements review are a whole process. Generally speaking, although requirements review comes first, case design and review comes later. But in fact, for test engineers, case design is already being done the moment the requirements review starts. We use the requirements document to have a basic understanding of the function of the product, of course, just understanding is far from enough. At this point, we need to switch to the role of real users and development engineers. Because we have been thinking about how to design and implement testcase from the very beginning. Can the scenario be relevant to the actual needs of the user, and how might the development engineer design it? From this point of view, it can help us to better pay attention to the irrationality and ambiguity in the requirements document.

Of course, in order to ensure quality and move the project forward, whenever we find a problem, we should communicate with the product and development at the same time, which is consistent with the understanding of the whole team. A morning meeting is a good way, and with this form, you don't have to spend time alone bringing everyone together. Of course, it is more ideal if team members sit together, and direct face-to-face communication is the most effective. I don't recommend throwing out the problem just by email or instant message, because it's too inefficient and probably won't achieve the same effect as we understand it. These problems should be recorded, and then the test case review process will be combined with the specific case scenario to simply go through, to ensure that at the end of the development process, the submitted product features are what we want.

Standing in the case scenario, Review profile design is also important for product quality and schedule. On the one hand, we can deepen our understanding of the internal logic, and it is possible to find performance flaws in the design or improper handling of some abnormal scenarios. For example, the test engineer can ask the development engineer how some abnormal scenarios are handled and how they behave, and you can tell from the developer's face whether he has paid attention to these less obvious areas at the time of design. Most of the time, most of our reported bug is found by test cases in these extreme scenarios. So is it better to prevent in the coding phase? Moreover, after you ask some of these questions, it will help to improve the status of testing in the team, and it will be more convenient to push forward at other times. On the other hand, we also need to consider the testability of functions in our tests. Generally speaking, testcase is more end-to-end testing, we can easily cover scenarios with interfaces, but some internal logic is not easy to test coverage through the interface. At this point, you need to ask the developer whether there can be some test parameters or log output support, or request the developer to pay special attention to the code review, so that the developer can ensure the quality of the complex logic.

After talking about so many details of the process, we can find that testcase design is very simple on the surface, but in fact, it requires a lot of communication work, especially for logically complex functions. For me, a testcase is not to find a lot of bug, but to build our confidence in product release.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.