INTRODUCTION:
The banking sector relies heavily on information technology to provide secure, efficient,
and reliable services to customers. A banking system's software plays a critical role in managing
transactions, accounts, and customer data. Ensuring the software's quality, reliability, and security
is vital to prevent financial losses, maintain customer trust, and comply with regulatory
requirements.
Project Objective:
This project aims to design and execute a comprehensive software testing strategy for a
banking system, focusing on functional, performance, security, and usability aspects. The
objective is to identify and report defects, validate software requirements, and ensure the system
meets industry standards and customer expectations.
Scope:
The testing scope includes:
1. User authentication and authorization
2. Account management (creation, modification, deletion)
3. Transaction processing (deposits, withdrawals, transfers)
4. Payment gateway integration
5. Reporting and analytics
6. Security features (encryption, access control)
7. User interface and user experience
Testing Methodologies:
This project will employ a combination of:
1. Black-box testing
2. White-box testing
3. Gray-box testing
4. Test-driven development (TDD)
5. Agile testing methodologies
1
Course OutComes :
1) Apply various software testing methods.
2) Prepare test case for different types and levels of testing.
SOFTWARE REQUIREMENT SPECIFICATION:
Test plan is derived from SRS(Software Requirement Specification) which is prepared by test
lead or manager. The main goalof test plan is to include all the details related to testing such
as what to test, when to test how to test and who will be the tester, Test plan is often not
updated but if there is some new feature or change is introduced thenit has to be updated
accordingly
2.1 Procedure followed for test plan creation:
1) Open the Banking System web based application.
2) Determine the scope that need to be tested and that are NOT to be tested
3) Prepare the document of Test Strategy
4) Decide Entry and Exit criteria.
5) Evaluate the test estimate.
6) Plan when and how to test and decide how the test results will be evaluated, and
define test exit criterion
7) Test artifacts delivered as part of test execution.
8) Define the management information, including the metrics required and
defect resolution and risk issues
9) Ensure that the test documentation generates repeatable test assets.
2
TEST PLAN FOR BANKING SYSTEM APPLICATION:
The purpose of this document is to create an web application test plan for Banking System.
The presented study test plan evaluates the approaches to testing this product. The purpose of
testing this program is to check the correct operation of its functionality, ease of use.
Test Items:
a) Working with the web application (opening, closing, etc.)
b) Logging in and testing functionalities.
c) Logging out from session of web application
Features to be Tested / Test Strategy:
1. User Management
- Registration
- Login/Logout
- Profile management
- Password reset
2. Account Management
- Account creation
- Account modification
- Account deletion
- Account balance inquiry
3. Transaction Management
- Deposit
- Withdrawal
- Transfer
- Transaction history
4. Payment Gateway Integration
- Payment processing
- Payment cancellation
- Payment refund
3
5. Reporting and Analytics
- Account statements
- Transaction reports
- Balance summaries
6. Security Features
- Authentication (username/password, 2FA)
- Authorization (role-based access control)
- Data encryption
- Firewall configuration
7. User Interface
- Navigation
- Error messaging
- Accessibility
4
Features not to be Tested / Out of scope:
a) Working with Help.
b) IPO section testing
c) Advisory section.
d) Interoperability testing.
Item Pass / Fail Criteria:
All test cases with high priority are closed with the result-pass. The test coverage is
checked and sufficient, where the criterion of sufficiency is not less than 99% of the
coverage of requirements by tests.
Exit Criteria:
During test application if there is 70% test cases are fall and then we should stop
testing for particular test case.
Test deliverables:
Test plan, test cases, test report.
Environmental Needs:
Testing the application will occur on the following operating systems : Windows 7/8/10.
5
TEST CASES:
Test Test case Test data Steps to be Expected results Actual results Pass/ Fail
case_id executed
1. Verify All details Enter all details Successfully entered Successfully Pass
mandatory mandatory mandatory input and checked entered and
input input parameters checked
parameters parameters
2. Verify optional -All details Enter all details Successfully entered Successfully Pass
input optional optional y input and checked entered and
parameters input parameters checked
parameters
3. Verify the user -Deposit Deposit amount Amount deposited Amount Pass
can deposit an amount and balance updated deposited and
amount in the balance updated
newly created
saving
account (and
thus updating
the balance)
4. Verify the user -withdraw withdraw Amount withdraw Amount withdraw Pass
can withdraw amount amount and balance updated and balance
an amount updated
from the newly
created
account (after
deposit) (and
thus updating
the balance)
5 Verify Adhar -Adhar Card Enter adhar card Adhar Card Adhar Card Pass
card linking no no. successfully linked successfully
linked
6 KYC updation -Upload Upload KYC KYC documents KYC documents Pass
KYC documents uploaded uploaded
documents successfully. successfully.
6
Conclusion:
The banking system project successfully demonstrated the design, development, and testing of
a comprehensive banking software application. The system provides a secure, efficient, and user-
friendly platform for customers to manage their accounts, perform transactions, and access
financial services. Banking applications are complex and vulnerable, and testing is necessary to
ensure they are bug-free, functional, and high-performing. Banking applications need to be secure
to protect sensitive information.
7
REFERENCE:
https://en.wikipedia.org/wiki/Bank
https://study.com/academy/lesson/banking-system-definition-types.html
https://eprajournals.com/IJCM/article/4511/download
https://en.wikipedia.org/wiki/Banking_in_India
