In Software testing, the term “use case” is used to describe all the possible steps a user may perform to interact with the system. It allows you to chalk out all the possible techniques and how the end-user can use the application with a set of instructions to the system and the expected result of the interaction with the system. It is a list of actions or event steps typically defining the interactions between an actor and system to achieve a goal.
Use cases also help QAs understand the areas where errors could occur while interacting with the system and design features to solve those errors. A use case is a graphical representation of a document explaining the steps an actor should perform to test the system.
Example of a Use Case
Assuming the use case of an online shopping system between a customer and seller through an online shopping application. Here’s what the Use Case Diagram would be like.
The above use case diagram depicts an Online shopping system consisting of two main actors: Customer and Seller. Six use cases are identified to explain the high-level functionality of the online shopping system.
A customer can view products, add products to cart, checkout, and place orders. A seller can view products, update existing product details and its price, and add/remove products from inventory.
No comments:
Post a Comment