Submitted By

Sheikh Shahariar Rumi - 201002326

Pranto dutta - 201002109

Balance Checking:

1. Positive Test Case:

 Input: Valid user credentials

 Expected Output: Successful balance retrieval with accurate information.

2. Negative Test Case - Invalid Credentials:

 Input: Invalid user credentials

 Expected Output: Error message indicating authentication failure.

3. Negative Test Case - Insufficient Permissions:

 Input: User without sufficient permissions tries to check balance

 Expected Output: Error message indicating insufficient permissions.

4. Negative Test Case - Nonexistent User:

 Input: Nonexistent user ID

 Expected Output: Error message indicating the user does not exist.

Balance Transfer:

5. Positive Test Case:

 Input: Valid sender and receiver details, sufficient balance

 Expected Output: Successful transfer with updated balances for both sender and
receiver.

6. Negative Test Case - Insufficient Balance:

 Input: Valid sender and receiver details, insufficient balance

 Expected Output: Error message indicating insufficient funds for the transfer.
 7. Negative Test Case - Invalid Receiver:

 Input: Valid sender, invalid or nonexistent receiver

 Expected Output: Error message indicating an issue with the receiver's account.

8. Negative Test Case - Incorrect Transaction Pin:

 Input: Valid sender and receiver details, incorrect transaction PIN

 Expected Output: Error message indicating an authentication failure.

Request Statement:

9. Positive Test Case:

 Input: Valid user credentials requesting a statement for a specific period

 Expected Output: Successful generation of the statement with accurate information.

10. Negative Test Case - Invalid Period:

 Input: Valid user credentials requesting a statement for an invalid or non-existing period

 Expected Output: Error message indicating an issue with the requested period.

11. Negative Test Case - Insufficient Permissions:

 Input: User without sufficient permissions requests a statement

 Expected Output: Error message indicating insufficient permissions.

12. Negative Test Case - Nonexistent User:

 Input: Nonexistent user ID requesting a statement

 Expected Output: Error message indicating the user does not exist.

These test cases cover a range of scenarios to ensure the robustness and reliability of the Balance
Checking, Balance Transfer, and Request Statement functionalities in a Tourism Management System.
Automated testing tools can be used to execute these test cases efficiently and to validate the expected
outcomes.