Use Case Testing and its elements

Posted By : Vaibhav Sajwan | 27-Apr-2024

QA testing

Loading...

Use Case Testing

What is the Use Case?

A use case is an approach for system analysis that identifies, clarifies, and organises needs. Use cases are a collection of conceivable sequences of interaction between the system and the user in a specific environment to achieve a specific goal.

It is a document of action performed by the user and how the system behaved on it.

Also Read JMeter For Software Testing

Elements of Use Cases

A use case has three major elements i.e Actor, Action, System

Actor :- Is a user that interacts with the system, and performs some functions to achieve a goal.

Action :- Is a system response, behavior, and final outcome that completes the process.

System : - The process and steps taken to reach the end goal, including the necessary functional requirement and their anticipated behavior.

Types of Use Case :-

1). Basic Use Case :- In this method the positive aspect of the application, and the positive scenarios are tested with valid data.

2). Alternate Use Cases :- In this case the alternate method is used to test the error handling of the system with alternate values.

3). Boundary Use Case :- This is the method of testing the use case at maximum and minimum input values.

4). Negative Use Case : - In this case, negative inputs are used to test the use case to detect and prevent errors.

5). Integration Use Case :- In this method of testing, the use case is being tested to process data within the system.

6). Performance Use Case :- In this case the objective of testing is to test the scalability, reliability, and response time of use cases.

Also Read Sanity Testing vs Regression Testing

Prerequisites for building Use Case Testing plan

  • Complete and thorough understanding of the system functionality.
  • Evaluate the associated risks and dependencies in the initial project stages.
  • Establish a proper communication plan and share it well with required stakeholders.
  • Timely and prompt communication between changes of scope and requirements.