Give you a requirement, how do you turn it into a final use case?
Just translate the requirements document and that's it.
Standard operations for veteran workers after receiving requirements:
Step 1: Analyze requirements
Analyze the requirements first - find out the verbs in all requirements, and then list all test points. The test point process continues to diverge, and for unclear standards, it is necessary to communicate with the product manager in a timely manner to confirm.
For example: "A toast pop-up window will pop up here." Laodian Union asked the product manager how many seconds it would take for this pop-up window to disappear.
For example: "The avatar here needs to read the cached avatar first, and then go to the interface to request the avatar if it is not available." Laodian Union asked the product manager to add: after the interface gets the avatar, should it be written to the cache first, or displayed on the app first.
Believe me, product managers will never dare to raise demands casually again.
Step 2: Delineate the test range of test points
This step is mainly to further review and determine the test scope of all the test points just mentioned.
For example: "Test the username input box", then do you want to use non-connected testing for testing? Do you want to test visible and invisible fields? Do you want to test all three input processing and output items? Divide the test range of all test points.
Step 3: Use eleven black box testing methods to write use cases
Standard use cases written by veteran workers often make everyone on the scene fall into silence and fall asleep during the use case review...
Step 4: Improve the use case attribute header
The use case header is divided into: [Requirement number] [Use case number] [Test project] [Test title] [Importance level] [Preset conditions] [Input parameters] [Execution steps] [Expected output] [Remarks] [Use case submitter 】
Step 5: Write use case procedures
What is a use case specification? It is to design the execution sequence of a use case so that the executor can significantly reduce the execution time.
For example, there are two use cases for the player: "A: Click the stop button during playback" and "B: Fast forward to 1 hour after clicking the play button.". If these two use cases are executed in the order of AB, then the executor must first click the play button - then click the stop button after playing for a while - then click the play button again - and then fast forward to 1 hour.
If you follow the order of BA, then you can: first click the play button - fast forward to 1 hour - click the stop button. This completes the execution of the two use cases. Saves environment preparation time.
This use case procedure is the most complex and most IQ-testing step. Many companies are unable to perform it and do not know this step at all.
Of course, use case procedures are a costly gamble. Unless an experienced person is familiar with it, it is better for newcomers not to waste time.
Finally, I would like to thank everyone who reads my article carefully. Reciprocity is always necessary. Although it is not a very valuable thing, if you can use it, you can take it directly: "Test Case Template Collection"
How to obtain documents:
This document should be the most comprehensive and complete preparation warehouse for friends who want to engage in [software testing]. This warehouse has also accompanied me through the most difficult journey. I hope it can also help you! All of the above can be shared, click on the small card below to join the group and get it for free.