Exercise 8 Date:

Aim : Test the software system for all the scenarios identified as per the

usecase diagram.

Objective : Test the software system for all the scenarios identified as per the

usecase diagram for railway reservation system.

Use Case Testing : Use Case Testing is a software testing technique that helps to

identify test cases that cover entire system on a transaction by transaction basis from

start to end. Test cases are the interactions between users and software application.

Use Case: Passenger Login

Test Case 1: Successful Login

1.Precondition: User is on the login page.

2.Test Steps:

Enter valid username and password.

Click the "Sign In" button.

3.Expected Result: The user should be successfully logged in and redirected to the dashboard.

Test Case 2: Invalid Credentials

1.Precondition: User is on the login page.

2.Test Steps:

Enter an incorrect username or password.

Click the "Sign In" button.

3.Expected Result: System should display an error message indicating incorrect credentials.

Use Case: Search Train

Test Case 3: Search Available Trains

1.Precondition: User is logged in and on the train search page.

1
2.Test Steps:

Enter source and destination stations.

Click the "Search Train" button.

3.Expected Result: The system should display a list of available trains for the selected route.

Test Case 4: Search Train for an Unavailable Route

1.Precondition: User is logged in and on the train search page.

2.Test Steps:

Enter an invalid or non-existent route.

Click the "Search Train" button.

3.Expected Result: System should display a message indicating no trains are available for the
selected route.

Use Case: Book Ticket

Test Case 5: Successful Ticket Booking

1.Precondition: User has searched for an available train.

2.Test Steps:

Select a train from the search results.

Choose class and seat type.

Confirm booking details.

Click the "Book Ticket" button.

Expected Result: Ticket should be successfully booked, and a confirmation message should be
displayed.

Test Case 6: Booking with Insufficient Seats

1.Precondition: User has searched for a train that has limited seats.

2.Test Steps:

Attempt to book more seats than available.

2
Click the "Book Ticket" button.

3.Expected Result: System should display an error message indicating insufficient seat
availability.

Use Case: Make Payment

Test Case 7: Successful Payment

1.Precondition: User has selected a train and is on the payment page.

2.Test Steps:

Enter valid payment details.

Click the "Make Payment" button.

3.Expected Result: Payment should be successfully processed, and a confirmation message

Test Case 8: Payment Failure Due to Insufficient Funds

1.Precondition: User has selected a train and is on the payment page.

2.Test Steps:

Enter payment details with insufficient funds.

Click the "Make Payment" button.

3.Expected Result: System should display an error message indicating payment failure due to
insufficient balance.

Use Case: View Booking

Test Case 9: View Confirmed Booking

1.Precondition: User has successfully booked a ticket.

2.Test Steps:

Navigate to the "View Booking" page.

Check the list of booked tickets.

3.Expected Result: The system should display a list of booked tickets along with details.

3
Test Case 10: View Booking with No Tickets

1.Precondition: User has not booked any tickets.

2.Test Steps:

Navigate to the "View Booking" page.

3.Expected Result: System should display a message indicating no bookings found.

Use Case: Cancel Booking

Test Case 11: Successful Ticket Cancellation

1.Precondition: User has a confirmed ticket in the system.

2.Test Steps:

Navigate to the "Cancel Booking" page.

Select a booking to cancel.

Confirm the cancellation.

3.Expected Result: The ticket should be successfully canceled, and the user should receive a
refund if applicable.

Test Case 12: Attempt to Cancel an Already Canceled Ticket

1.Precondition: User has already canceled a ticket.

2.Test Steps:

Navigate to the "Cancel Booking" page.

Select the canceled ticket again.

Click the "Cancel" button.

3.Expected Result: System should display an error message indicating the ticket has already
been canceled.

Use Case: Verify Booking (Ticket Clerk)

Test Case 13: Successful Booking Verification

1.Precondition: A ticket clerk is logged into the system.

4
.2Test Steps:

Enter passenger ticket details.

Click "Verify Booking" button.

3.Expected Result: System should confirm whether the ticket is valid or not.

Test Case 14: Verification of Invalid Booking

1.Precondition: A ticket clerk is logged into the system.

2.Test Steps:

Enter details of a non-existent or fake booking.

Click "Verify Booking" button.

3.Expected Result: System should display an error message indicating the ticket is invalid.

Use Case: Process Payment (Ticket Clerk & System)

Test Case 15: Payment Processing by Clerk

1.Precondition: Passenger has provided payment details.

2.Test Steps:

Ticket clerk enters passenger details.

Click "Process Payment" button.

3.Expected Result: Payment should be processed successfully, and a receipt should be

Use Case: Show Train Schedule

Test Case 16: View Available Train Schedule

1.Precondition: User is logged in.

2.Test Steps:

Navigate to the "Show Train Schedule" page.

3.Expected Result: System should display a list of available train schedules.

Use Case: Generate Ticket

5
Test Case 17: Generate a Ticket After Payment

1.Precondition: Payment has been completed.

2.Test Steps:

Click "Generate Ticket" button.

3.Expected Result: The system should generate a digital ticket with a unique PNR number.

Use Case: Cancel Ticket (System)

Test Case 18: System Cancels Ticket for Policy Violation

1.Precondition: A ticket is flagged for cancellation due to policy violations (e.g., fraud).

2.Test Steps:

System detects fraudulent activity.

System cancels the ticket automatically.

LIBRARY MANAGEMENT SYSTEM:

Aim : Test the software system for all the scenarios identified as per the

usecase diagram.

Objective : Test the software system for all the scenarios identified as per the

usecase diagram for library management system.

Use Case Testing : Use Case Testing is a software testing technique that helps to

identify test cases that cover entire system on a transaction by transaction basis from

start to end. Test cases are the interactions between users and software application.

Use Case: Member Submits Book

Test Case 1: Successful Book Submission

1. Precondition: Member has a book to submit.

6
2. Test Steps:

- Member selects the "Submit Book" option.

- System prompts for book details.

- Member enters valid book details.

- Click on "Submit."

3. Expected Result: The book is successfully submitted, and a confirmation message is

Test Case 2: Submitting an Unregistered Book

1. Precondition:Member has a book not registered in the system.

2. Test Steps:

- Member selects the "Submit Book" option.

- System prompts for book details.

- Member enters book details that do not exist in the database.

- Click on "Submit."

3. Expected Result:System displays an error message stating the book is not registered.

Use Case: Checking Book Condition

Test Case 3: Check Book Condition Before Acceptance

1. Precondition: The book is submitted by a member.

2. Test Steps:

- Librarian selects "Check Book Condition."

- System prompts to inspect book details.

- Librarian verifies the book condition.

3. Expected Result:The book condition is marked as acceptable or damaged.

Test Case 4: Damaged Book Notification

7
1. Precondition: Book is submitted with visible damage.

2. Test Steps:

- Librarian selects "Check Book Condition."

- Librarian marks the book as damaged.

- System prompts for damage details.

3. Expected Result: System notifies the member about book damage and applicable penalties.

Use Case: Logging into the Library System

Test Case 5: Successful Login

1. Precondition: User has valid credentials.

2. Test Steps:

- User enters a valid username and password.

- Clicks on "Log in."

3. Expected Result: User is successfully logged in and redirected to the dashboard.

Test Case 6: Invalid Login Attempt

1. Precondition: User enters incorrect credentials.

2. Test Steps:

- Enter an invalid username or password.

- Click on "Log in."

3. Expected Result: System displays an error message stating incorrect credentials.

Use Case: Confirming Book Return

Test Case 7: Successful Book Return

1. Precondition: The book is submitted by a member.

2. Test Steps:

8
 - Librarian selects "Confirm Book Return."

- System verifies the book against records.

- Librarian confirms return.

3. Expected Result: The book return is recorded, and a receipt is issued.

Use Case: Issuing Return Receipt

Test Case 8: Generate Return Receipt

1. Precondition: Book return is confirmed.

2. Test Steps:

- Librarian selects "Return Book Receipt."

- System generates and prints receipt.

3. Expected Result:Receipt is generated and provided to the member.

Use Case: Overdue Fee Notification

Test Case 9: Notify Overdue Fee

1. Precondition: Member returns a book past the due date.

2. Test Steps:

- Librarian selects "Notify Overdue Fee."

- System calculates the fine and sends a notification.

3.Expected Result: Member is notified about the overdue fee.

Use Case: Updating Book Record

Test Case 10: Update Book Status After Return

1. Precondition: Book has been returned and verified.

2. Test Steps:

- Librarian selects "Update Book Record."

- System updates book availability.

9
3. Expected Result:Book is marked as "Available" in the system.

10