1.1 Project Overview
The Bank Transfer Test Plan is designed to verify that a banking application can process money transfers accurately, securely, reliably, and efficiently. The testing will cover the complete transfer process, from selecting or entering a beneficiary to transaction confirmation, account debit, recipient credit, notification, and transaction history.
The purpose of this test plan is to identify defects that could result in incorrect transactions, failed transfers, duplicate transactions, unauthorized transactions, or incorrect account balances.
2. Objectives of the Test Plan
The major objectives are to:
Verify that customers can successfully transfer money to valid bank accounts.
Confirm that the correct amount is deducted from the sender’s account.
Confirm that the recipient receives the correct amount.
Verify that invalid account details are properly rejected.
Verify that transfers cannot be made when the sender has insufficient funds.
Test transaction authentication such as PIN, OTP, or other approved verification methods.
Verify that successful and failed transactions are properly recorded.
Verify that customers receive appropriate transaction notifications.
Ensure that duplicate transactions do not occur.
Identify and document defects before the system is released.
3. Scope of Testing
3.1 In Scope
The following areas will be tested:
User login
Account balance verification
Beneficiary creation
Beneficiary account validation
Bank selection
Account number validation
Transfer amount
Transfer charges
Transaction confirmation
PIN/OTP authentication
Successful transfer
Failed transfer
Cancelled transfer
Insufficient balance
Transaction history
SMS/email/app notification
Debit and credit confirmation
Error messages
Network interruption
Transaction security
3.2 Out of Scope
The following may be excluded from this test:
Physical ATM hardware testing
Physical bank branch operations
Actual movement of real money
Third-party banking systems that are not part of the application under test
Production customer accounts
Testing should preferably be performed using test accounts and test funds, not real customer money.
4. Types of Testing
4.1 Functional Testing
This verifies that every bank transfer function works according to its requirements.
4.2 Integration Testing
This checks whether the banking application communicates correctly with other required services, such as payment gateways or banking systems.
4.3 Security Testing
This verifies that unauthorized users cannot initiate or manipulate transactions.
4.4 Performance Testing
This checks how the transfer system performs under normal and high transaction loads.
4.5 Usability Testing
This determines whether users can understand and complete the transfer process easily.
4.6 Negative Testing
This involves deliberately entering invalid information to ensure that the system responds appropriately.
4.7 Regression Testing
This verifies that new changes to the application have not broken existing transfer functionality.
5. Test Environment
The test environment may include:
Item
Description
Application
Banking/mobile banking application
Device
Android/iOS smartphone or computer
Browser
Chrome, Firefox, Edge, etc.
Database
Test banking database
Network
Wi-Fi/mobile network
Test Account
Sender and recipient test accounts
Authentication
Test PIN/OTP
Test Funds
Simulated account balance
6. Test Data
Sample test data can include:
Sender account: 0123456789
Recipient account: 9876543210
Valid transfer amount: ₦10,000
Insufficient balance amount: ₦500,000
Invalid account number: 12345
Zero amount: ₦0
Negative amount: -₦5,000
Valid authentication: Test PIN/OTP
Invalid authentication: Incorrect test PIN/OTP
These should be dummy test details only, not real bank accounts or credentials.
7. Detailed Test Cases
Test ID
Test Scenario
Test Steps
Expected Result
Priority
BT-001
Successful transfer
Login → select transfer → enter valid details → confirm
Transfer is successful
High
BT-002
Invalid account number
Enter an invalid account number
System displays an appropriate error
High
BT-003
Empty account number
Leave account number blank
System requests account number
High
BT-004
Zero transfer amount
Enter ₦0
System rejects the transaction
High
BT-005
Negative amount
Enter a negative amount
System rejects the transaction
High
BT-006
Insufficient balance
Enter amount greater than available balance
Transfer is rejected
High
BT-007
Valid authentication
Enter correct test PIN/OTP
Transaction proceeds
High
BT-008
Invalid authentication
Enter incorrect PIN/OTP
Transaction is rejected
High
BT-009
Cancel transaction
Start transfer and select cancel
Transaction is cancelled
Medium
BT-010
Verify debit
Complete successful transfer
Sender is debited correctly
Critical
BT-011
Verify credit
Complete successful transfer
Recipient is credited correctly
Critical
BT-012
Transaction history
Complete transfer → check history
Transaction appears correctly
Medium
BT-013
Transfer notification
Complete successful transfer
Appropriate notification is generated
Medium
BT-014
Failed transaction
Simulate transfer failure
Appropriate failure message appears
High
BT-015
Network interruption
Disconnect network during transfer
System handles interruption safely
High
BT-016
Duplicate submission
Submit the same transfer repeatedly
Duplicate transaction is prevented
Critical
BT-017
Invalid bank selection
Select an invalid/unavailable bank
System prevents invalid transaction
High
BT-018
Maximum transfer limit
Enter amount above permitted limit
System rejects or appropriately handles transaction
High
BT-019
Minimum transfer limit
Enter amount below permitted minimum
System displays appropriate validation
Medium
BT-020
Logout after transaction
Complete transfer → logout
User is securely logged out
Medium
8. Detailed Example of a Test Case
Test Case ID: BT-001
Test Case: Successful Bank Transfer
Priority: Critical
Precondition:
User has a valid test account.
User is successfully logged in.
Sender has sufficient test funds.
Recipient account is valid.
Test Steps:
Log into the banking application.
Select Transfer Money.
Select the recipient bank.
Enter the valid recipient account number.
Enter the transfer amount.
Review the transaction details.
Enter the valid test PIN/OTP.
Click Confirm Transfer.
Expected Result:
The system should successfully process the transaction, debit the sender’s account with the correct amount and applicable charge, credit the recipient’s account appropriately, and display a successful transaction message.
Actual Result:
To be completed during testing.
Status:
Pass/Fail — to be completed during testing.
9. Negative Test Cases
Negative testing is particularly important in a banking application.
Examples include:
Transfer without logging in.
Transfer with an invalid account number.
Transfer with an empty account number.
Transfer with ₦0.
Transfer with a negative amount.
Transfer above the permitted limit.
Transfer when the account has insufficient funds.
Transfer using an incorrect PIN/OTP.
Transfer when the network connection is interrupted.
Repeatedly clicking the transfer button.
Using an expired OTP.
Attempting to transfer from a blocked or restricted account.
The system should reject invalid transactions safely and provide understandable error messages.
10. Security Testing
Security testing is one of the most important parts of a bank transfer test plan.
The tester should verify that:
Users cannot access another customer’s account.
Authentication is required before transferring money.
Sensitive information is protected.
Incorrect authentication attempts are handled appropriately.
Users cannot modify transaction details after final confirmation without proper authorization.
Users cannot bypass transfer limits through the application.
Sessions are properly secured.
Transaction records cannot be manipulated by unauthorized users.
11. Performance Testing
The tester should determine whether the system can handle many transfer requests without becoming unstable.
Examples:
Test multiple simultaneous transfers using test accounts.
Measure transaction response time.
Check system behaviour during high traffic.
Check whether transactions are duplicated under heavy load.
Verify that failed transactions are handled correctly when the system is under stress.
12. Defect/Bug Reporting
When a tester discovers a problem, it should be documented.
Defect ID
Test ID
Defect Description
Severity
Status
BUG-001
BT-002
Invalid account number accepted
High
Open
BUG-002
BT-006
Transfer succeeds despite insufficient balance
Critical
Open
BUG-003
BT-015
Application crashes after network interruption
High
Open
Severity levels
Critical: Major financial/security failure.
High: Important functionality is seriously affected.
Medium: Functionality is affected but a workaround may exist.
Low: Minor issue with little functional impact.
13. Entry Criteria
Testing can begin when:
The application is available for testing.
Requirements are available.
Test environment has been prepared.
Test accounts have been created.
Required test data is available.
Test cases have been reviewed.
14. Exit Criteria
Testing can be completed when:
All planned test cases have been executed.
Critical defects have been resolved or formally accepted.
Major functionality has passed testing.
Regression testing has been completed.
Test results have been documented.
The testing team provides a final test report.
15. Risks and Mitigation
Risk
Impact
Mitigation
Network failure
Transfer may fail
Test different network conditions
Incorrect account details
Money could be sent incorrectly
Validate account details
Duplicate submission
Duplicate transaction
Test repeated submissions
System downtime
Transfer unavailable
Perform availability testing
Security vulnerability
Unauthorized transactions
Conduct security testing
Insufficient test data
Incomplete testing
Prepare adequate test accounts
16. Expected Test Deliverables
The project should produce:
Bank Transfer Test Plan
Test Scenarios
Test Cases
Test Data
Defect/Bug Reports
Test Execution Results
Test Summary Report
17. Conclusion
The Bank Transfer Test Plan provides a structured approach for evaluating the reliability, functionality, security, and performance of a bank transfer system. Proper testing helps ensure that customers can transfer funds accurately and securely while reducing the risk of transaction failures, duplicate transactions, incorrect account balances, and unauthorized transfers.