Use case testing is carried to identify the test cases with the use cases as test basis. The use cases are prepared by the Business Analyst (BA) to describe the interactions between the software items. The software functions are described using the use cases. The use case describes the process flow through the system based on its most likely in use. This makes the test cases derived from use cases good to particularly find the defects in the real world system.
A use case description is associated with different software items like end users, hardware components or any other system. All these system items are termed as Actors. Each use case describes the interactions of an actor with the system in order to achieve some specific goals. A use case can include: actors, system, interactions, preconditions, post conditions. The interactions can be represented using work flow diagrams, activity diagrams and business process models. Use cases can describe the normal behaviour, exceptional behaviour and error handling conditions.
Consider an example for flight reservation:
Actors: Customer attempting a flight reservation
System: train reservation system
Step 1:
In the login functionality of the flight reservation application form, where the Customer enters the agent name and password to login.
Step 2:
The flight reservation system will verify the password and account. If the account is active and user credentials are valid, Customer is allowed to login and menu options are displayed.
Here there could be an extension of the use case as the password is not valid the system may give the message and ask for retyping.
Or if the password is not correct for four or five times the application may close.
Step 3:
The Customer(actor) selects the book ticket option. The reservation system displays the page to enter travel details.
Step 4:
The Customer searches for available flights, selects the flight, enters travel details and proceed to payment. The payment options are provided by system. The customer completes the payment. System generates the travel itinerary. User logs out.
9 Responses
The use cases are prepared by the Business Analyst (BA) to describe the interactions between the software items.A use case description is associated with different software items like end users, hardware components or any other system. All these system items are termed as Actors. Each use case describes the interactions of an actor with the system in order to achieve some specific goals. A use case can include: actors, system, interactions, preconditions, post conditions. The interactions can be represented using work flow diagrams, activity diagrams and business process models. Use cases can describe the normal behavior, exceptional behavior and error handling conditions.
What is Use Case Testing?
Use case testing is carried to identify the test cases with the use cases as test basis. The use cases are prepared by the Business Analyst (BA) to describe the interactions between the software items
Use case testing is carried to identify the test cases with the use cases as test basis. The use cases are prepared by the Business Analyst to describe the interactions between the software items. The software functions are described using the use cases.
1.Use case testing is carried to identify the test cases with the use cases as test basis & The use case testing is designed using use case documents as reference ,also It defines the interactions between actors and system.
Actors denote the users and their interactions of each user who take part into.
Test cases which is based on the use cases are called as scenarios.
It is very effective in defining the scope of acceptance tests.
2. for example consider an Cash deposit machine(CDM)
1.User insert the card/Enter the account number
2.if its an active card or account the system asks to enter the pin or ask some personal details
3.ENTER THE Amount deposited
4.after few seconds a slot will open and the system ask to place the money in that slot and after few seconds the slot closes
5. it will start counting and on the screen it will show the denominations of the cash that dropped in
6.the customer verify it & transaction completed & receipt will receive
Use Case Testing is defined as a software testing technique, that helps identify test cases that cover the entire system, on a transaction by transaction basis from start to the finishing point.
It is a functional black box testing technique which helps testers to identify test scenarios that exercise the whole system on each transaction basis from start to finish.
A use case can include: actors, system, interactions, preconditions, post conditions.
Use case testing is carried to identify the test cases with the use cases as test basis. The use cases are prepared by the Business Analyst (BA) to describe the interactions between the software items. It is basically is also known as “need(s)”. So easily put is use case testing is testing what eventually the client needs to perform for the actor or what the actor needs from interacting with the software. The actor is also known as the customer.
Use Case testing is the testing done to check the process flow of the system based on its most likely use as requested by the client to find any defects within the software.
Use case testing is carried to identify the test cases with the use cases as test basis. The use cases are prepared by the Business Analyst (BA) to describe the interactions between the software items. The use case describes the process flow through the system based on its most likely in use. Use case document is used as reference for test case document.