I have been engaged in testing for several years. As an important part of the testing process, test cases are often designed and used in daily work. However, how to design concisely has a high reuse rate, and everyone can guide their work through use cases Yes, there is indeed a certain knowledge. The following are a few opinions compiled from a personal point of view.
1. The title is concise and the purpose is clear. The tone should be an affirmative statement name and preferably no longer than 25 words.
Such as: verify that the **** function is correct; verify that the *** handles errors.
2. The prerequisites and restrictions are clear.
For example: the user is logged in; the user account has sufficient funds. . .
3. The test steps are well organized. Here, if the function points contained in the test title can be further subdivided and explained one by one, then the corresponding test results should also be explained separately, corresponding to the steps one by one.
Such as: 1.*****; 2.*****,
4. The expected results are concise and clear. The tone should be an affirmative statement name and preferably no longer than 25 words. If the length is too long, it can be subdivided with test steps.
In order to design test cases to meet the above requirements, you need to be familiar with the product requirements. We can use some tools and charts to assist in analyzing requirements, such as using tree diagrams to analyze the relationship between operation items, which can better clarify ideas and lead to the design of test cases.
In short, a test case design must be like this, simple and efficient, with high reuse rate, and it can be said to be foolish, that is, a newcomer can follow the test case when he does not know much or does not know much about the requirements. to guide the test, and there is almost no other ambiguous understanding during the test.
The above is just a little personal opinion, if anyone has a different opinion, welcome to throw a brick.