Login

Test Test Expected

Test Case ID Input Data Actual Output Status
Objective Description Output

Check if the
username and Username: Proper Proper
Validate
password fields valid_user@example.com, handling and handling and
WB_LOGIN_001 Input Field Pass
correctly handle Password: display of display of
Handling
valid and invalid CorrectPassword123 input, no errors input, no errors
input.

Verify that the

Password
password is Username:
Validate should be Password is
hashed and not valid_user@example.com,
WB_LOGIN_002 Password hashed and not visible in logs Fail
stored or Password:
Hashing visible in logs or databases
transmitted in CorrectPassword123
or databases
plain text.

A valid session
Ensure that a
Username: should be
session is created
Test Session valid_user@example.com, created with A valid session
WB_LOGIN_003 and managed Fail
Management Password: appropriate is not created
properly after a
CorrectPassword123 session
successful login.
cookie/token

Verify that
appropriate error Error message Error message
Test Error
messages are Username: indicating indicating
Handling
WB_LOGIN_004 displayed for invalid_user@example.com invalid invalid Pass
and
invalid Password: WrongPassword credentials or credentials or
Messaging
credentials or system issue system issue
system errors.

Verify that
Account should
multiple failed Username: Account is not
Validate be locked or
login attempts valid_user@example.com, getting locked
Account CAPTCHA
WB_LOGIN_005 trigger an Password: and no Fail
Lockout presented after
account lockout IncorrectPassword CAPTCHA is
Mechanism a threshold of
or CAPTCHA (repeatedly) presented
failed attempts
mechanism.

Ensure that users

Admin should Admin should
Check with different
Username: have access to have access to
Role-Based roles can access
WB_LOGIN_006 admin_user@example.com, admin features; admin features; Pass
Access only their
Password: AdminPass regular users regular users
Control permitted areas
should not should not
after login.

Check if the
Error message Error message
password
indicating indicating
Verify complexity
Username: insufficient insufficient
Password requirements
WB_LOGIN_007 valid_user@example.com, password password Pass
Complexity (length, character
Password: 123 complexity if complexity if
Enforcement types) are
requirements requirements
enforced during
are not met are not met
login.
 Registration

Test Test Expected

Test Case ID Input Data Actual Output Status
Objective Description Output
Check if the Email:
Fields accept Fields accept
registration new_user@exa
Validate valid inputs and valid inputs and
form fields mple.com,
WB_REG_001 Input Field reject invalid reject invalid Pass
handle valid Password:
Handling ones, proper ones, proper
and invalid NewPassword1
error handling error handling
inputs properly. 23

Verify that the Email:

Test Email email field invalid_email, Error message for Error message for
WB_REG_002 Format validates email Password: invalid email invalid email Pass
Validation formats ValidPassword1 format format
correctly. 23

Ensure that the

No Error
Validate password meets Email: Error message for
message for
Password complexity new_user@exa insufficient
WB_REG_003 insufficient Fail
Complexity requirements mple.com, password
password
Requirements (length, Password: 123 complexity
complexity
characters).
Email:
Verify that the
existing_user@ Error message Error message
Check for system prevents
example.com, indicating the indicating the
WB_REG_004 Duplicate registration Pass
Password: email is already email is already
Registration with an already
AnotherPasswo in use in use
used email.
rd123
Ensure that a Email:
new user new_user@exa Account should Account should
Validate
account is mple.com, be created and be created and
WB_REG_005 Account Pass
created and Password: details stored details stored
Creation
stored securely NewPassword1 securely securely
in the database. 23
 Booking
Test Expected
Test Case ID Test Objective Input Data Actual Output Status
Description Output

User ID: user123,

Check if the
Validate Pickup Location: Booking is Booking is
system correctly
Booking Location A, successfully successfully
WB_BOOK_001 handles a valid Pass
Request Dropoff Location: created with created with
booking
Handling Location B, Time: correct details correct details
request.
2024-09-11 10:00:00

Verify that the

User ID: user123,
system handles
Pickup Location: Error message Error message
Test Booking booking
Invalid Location, indicating indicating
WB_BOOK_002 with Invalid requests with Pass
Dropoff Location: invalid pickup invalid pickup
Locations invalid or
Location B, Time: location location
unavailable
2024-09-11 10:00:00
locations.

User ID: user123,

Ensure that the
Pickup Location: Error message Error message
system correctly
Validate Time Location A, or system or system
processes
WB_BOOK_003 and Date Dropoff Location: validation if validation if Pass
bookings for
Handling Location B, Time: booking time is booking time is
future dates
2024-09-11 too soon too soon
and times.
09:00:00

Overlapping
Verify that the User ID: user123,
bookings
system manages Pickup Location: Overlapping
Check for should be
overlapping or Location A, bookings are
WB_BOOK_004 Overlapping handled Fail
conflicting Dropoff Location: not handled
Bookings correctly, with
bookings for Location B, Time: correctly
notifications or
the same user. 2024-09-11 10:00:00
errors

Ensure that a
User ID: user123,
booking Confirmation Confirmation
Pickup Location:
confirmation is email or email or
Test Booking Location A,
WB_BOOK_005 sent to the user notification is notification is Fail
Confirmation Dropoff Location:
after a received by the not received by
Location B, Time:
successful user the user
2024-09-11 10:00:00
booking.
 Payment
Test Test
Test Case ID Input Data Expected Output Actual Output Status
Objective Description
Check if the User ID: user123,
Payment is Payment is
system correctly Booking ID:
Validate successfully successfully
processes a booking456,
WB_PAY_001 Payment processed, and processed, and Pass
payment for a Payment Method:
Processing confirmation is confirmation is
completed Credit Card,
received received
booking. Amount: $25.00
User ID: user123,
Booking ID:
Verify that the booking456,
Test Invalid Error message for Error message for
system handles Payment Method:
WB_PAY_002 Payment invalid payment invalid payment Pass
invalid payment Credit Card,
Details details details
details correctly. Amount: $25.00,
Card Number:
Ensure that the
User ID: user123,
payment
Validate Booking ID: Payment gateway
gateway
Payment booking456, processes the Payment gateway
WB_PAY_003 integration is Fail
Gateway Payment Method: payment without has some issues
functioning
Integration Credit Card, issues
correctly and
Amount: $25.00
securely.
Verify that User ID: user123,
Confirmation Confirmation
payment Booking ID:
Check email or email or
confirmation is booking456,
WB_PAY_004 Payment notification is notification is not Fail
sent to the user Payment Method:
Confirmation received by the received by the
after a successful Credit Card,
user user
transaction. Amount: $25.00

Refund is Refund is
User ID: user123,
Ensure that the processed and processed and
Booking ID:
Test Refund system handles confirmed, and confirmed, and
WB_PAY_005 booking456, Pass
Process refund requests appropriate appropriate
Refund Reason:
correctly. notifications are notifications are
Cancellation
sent sent
 Ride History
Test Test
Test Case ID Input Data Expected Output Actual Output Status
Objective Description

Check if the
List of past rides is List of past rides is
Validate Ride system retrieves
User ID: correctly displayed correctly displayed
WB_RH_001 History and displays the Pass
user123 with accurate with accurate
Retrieval ride history for a
details details
user correctly.

Verify that the

system handles Message Message
Test Empty User ID:
WB_RH_002 cases where the indicating no ride indicating no ride Pass
Ride History new_user
user has no ride history is present history is present
history.

Ensure that the

details of each
Validate Ride ride (pickup, User ID: Accurate details Accurate details
WB_RH_003 Details dropoff, time, user123, Ride for the specified for the specified Pass
Accuracy cost) are accurate ID: ride789 ride are displayed ride are displayed
and correctly
displayed.

Verify that the

system allows User ID: Ride history is Ride history is not
Check Ride
filtering of ride user123, filtered correctly filtered correctly
WB_RH_004 History Fail
history by date, Filter: Date: based on specified based on specified
Filtering
location, or other 2024-09-10 criteria criteria
criteria.

Ensure that the

Ride history is Ride history is not
system handles
Test paginated paginated
pagination of User ID:
Pagination correctly and correctly and
WB_RH_005 ride history user123, Page: Fail
and performance performance
efficiently for 2
Performance remains remains
users with
acceptable acceptable
extensive history.