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

In general software companies, designing test cases and writing test cases has always been a very important basic work for testers.

However, many software testers or others always feel that there is no need to write test cases.

The software development process goes like this:

Product personnel determine user requirements-> product personnel, developers, testers, UE personnel, etc.-> developers design and develop (test design and write use cases-> developers submit-> testers execute tests according to requirements and use cases-> release online.

In my opinion, test cases must be written. However, many software testing practitioners think that the writing of test cases is futile, because the final execution of the test is often very different from the test case. In fact, I think the main reason for this phenomenon is that it is not done well in the requirements review stage, and the development, product, and UE have different understanding of the requirements, which leads to changes in subsequent requirements, and it is even possible that the requirements themselves are not perfect, so they are constantly changing in the process of development.

But in fact, these reasons, we can control them within an acceptable range, of course, this is mainly the content of the requirements review stage. Personally, even if the requirements review process is perfect, there will be few changes in requirements. When writing test cases, in order to have higher coverage of use cases, we will often find some omissions in requirements, communicate in time, and improve efficiency. Thus, the process of writing use cases is more helpful for testers to understand requirements.

Test cases are like scripts or batons, so it is necessary to write test cases. But in many Internet companies, agile development is basically adopted, and product iterations are very frequent, so the time for testers to execute tests is very short, not to mention the time to write test cases. at this point, we can simplify the test points. However, it is recommended that when you encounter a more complex process, you can describe it in detail with test cases as much as possible.

In fact, you can also talk to developers about how this function is implemented before writing test cases and when you are ready to execute tests. This makes it easy to grasp the points for attention in the test and can be reflected in the use case. For example, developer An once did a function in some way, and bug appeared, and now that developer B has implemented a similar function in the same way, it is likely that the previous bug will appear again.

Use case review is also a very important stage, especially some experienced software testing "old drivers", who can quickly help point out the missing points of the use cases, help to open up ideas and cover as many user scenarios as possible.

It is worth noting that the uncertain situation encountered during the use case review should be recorded immediately, and after the end, it should be confirmed with the relevant personnel and dealt with in time.

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.