Many times, when the interviewer asks this question, he doesn't really want to know how many use cases you wrote and how long it took.
After all, in an enterprise, there are still many tasks and types of work. The type and business complexity of each project will determine how many use cases are written per day.
Even if you say a piece of data, the interviewer will have questions about the data.
The only thing that can be done is that we tell a general data, and then learn to explain it according to my past.
Hello, interviewer, we wrote about 200 articles a day. I remember that last time we had a need to switch to iterations. At that time, there were several versions of functions. We had about 3 days to write 500-600 articles.
What I want to say here is that in answering this question, we are more concerned with the overall data, as long as there is no relatively large gap, the interviewer will generally not have too much doubt.
As for the design ideas of use cases here, you can generally answer according to the following words:
Our general idea of use case design: First of all, we must clarify the business logic of this software, because the essence of software is the logic and data flow direction of the business after all. On the basis of clarifying each business logic, conduct valid and invalid tests on all input field controls involved.
Finally: The following complete software testing video learning tutorial has been sorted out and uploaded. Friends can get it for free if they need it [Guaranteed 100% free]
