Hello friends! in this article, we are going to learn about banking application testing. Before starting with the testing part, let’s first learn about the banking process.
Today, every product and service that the organizations provide, need to have online access to it and it is also applicable to any banking organization. Banks have multiple products and services for millions of customers. To provide them, banks have arranged various physical branches where customers can go and avail of the services.
As digitization increases in every domain, many of the bank customers prefer doing every possible transaction or accessing any service at home on their laptops and mobile phones rather than going to the branch.
This trend forces the banks to have an application, both desktops, and mobile, for their customers. With banking/BFSI applications, customers can transfer the money online, view their account balances, etc. at home, without going anywhere.
Banking applications deal with money and that is why testing banking applications thoroughly is a critical process. Moreover, every such application has several users who are doing concurrent transactions.
So, testing the functions of the application is not enough. Testing the database as well as nonfunctional characteristics such as security, compatibility, performance is also crucial. In this tutorial, we will understand the testing process of a banking application along with various testing phases.
Services Provided by Banking Application
For customers, the following are various services provided by banking applications-
- Retail banking
- Corporate banking
- Investment banking
- Mutual funds
- Payments
- ATM
- Cards
- Internet banking
- Trade Finance
- Insurance
- Brokerage
- Capital Markets
Features of a typical Banking Application
Before we discuss the testing process, let’s first look at some of the vital features of any banking application-
- Sign in and Sign up feature for the users of the application
- View account details such as account number, branch name, account balance for various accounts such as savings, current, demat, etc.
- Transfer Money between accounts
- View transaction history
- Pay Third-party bills such as mobile bills, utility bills
- Pay credit card bills
- ATM locator
- Pay Loan installments
- Manage various banking products such as Fixed Deposit, Recurring Deposit
- Chatbot
- Alerts and notifications
Apart from these features, there are many other important features that any banking application would provide. Testing each feature is critical as it has a huge number of sub-features in it. For example, In the money transfer feature, the user will have options of adding an account as a beneficiary, setting a transfer limit, etc.
Moreover, the application may provide an easy and short process for transferring money to the same bank’s account, another option can be of quick transfer where with minimal details money can be transferred.
Banking Application Testing Process
A typical process of testing a banking application can have the following steps-
Requirements Gathering
The testing process starts from the first phase of SDLC i.e. requirements gathering. Usually, in agile projects, along with business analysts, the testing team is also involved in the requirements gathering process. In traditional models like a waterfall, the testing team comes into the picture later once the requirements have been collected.
For finance-related, banking projects, the testers should have adequate domain knowledge. Testers should be able to think from both the stakeholder and end-user’s points of view. In this phase, analysts gather requirements, understand and review the requirements. In addition, they gain as much domain knowledge as possible by the research, and/or taking help from the SMEs.
Test Planning
In this next phase, the testing team proceeds with the detailed planning of the testing process. Here, a test plan is created. This includes the scope of the testing, roles, and responsibilities, test deliverables, testing levels, testing tools, test environments, etc.
Test Scenario and Test Case Creation
Here, based on the requirements document, test scenarios, and test cases are created. The testing team should be careful in covering each scenario. Not only functional but also security, performance, and other nonfunctional characteristics should be covered.
Functional Testing
After test case creation, the testing team conducts functional testing to make sure the features are implemented as per the requirements.
Functional Testing Checklist
- Check whether keeping mandatory fields empty shows error messages. For example, while transferring the money, ‘Amount’ should be mandatory and cannot be kept empty.
- Check whether all the fields accept valid values and after entering an invalid value system shows error messages. For example – the ‘Account Number’ field should not accept special characters.
- Check whether all the fields have a valid character limit. For example – the ‘Account Number’ field should accept values between 9 to 18 characters.
- Verify that all the links in the application are clickable and land on the desired page.
- Check whether all the buttons are clickable and work in the desired manner.
- Check whether all the calculations are performed in the desired manner. For example – after a debit or credit transaction, the account balance should reflect the correct amount).
- Verify the scrolling functionality of the application.
- Check the application working in flight mode.
- Verify the application working during the ongoing transaction when a phone call, SMS, or any other notifications are received(for mobile applications).
- Check the application installation, uninstallation, and update processes.
Database Testing
Database testing includes testing the front-end layer, business logic layer, and database. In this type of testing, queries are executed and data flow in different tables is observed. The testing team responsible for the database testing should have in-depth knowledge of the database.
Database Testing Checklist
- Check whether the data is logically organized in the database.
- Check each field’s data type and see whether it is as per the desired specification.
- Verify the field length on the front-end side and in the database is the same.
- Check the values of the computed field. (e.g. DoB and Age)
- Check whether the naming conventions used in the database are uniform. (e.g. Names of tables, columns, stored procedures, indexes)
- Verify that the data values are stored in the correct columns and tables.
- Check whether each table has a primary key and foreign key constraints.
- Check for any redundant and duplicate data.
- Insert null values in the columns that should not accept null values.
- Check if the data is correctly stored in the database when fetched from the front end.
- Verify that the database is access is restricted to authorized users only.
- Check whether in the event of failure data is rolled back or not.
- Check application working when the database server is down.
- Verify that the database backup is taken regularly.
- Check database performance when multiple users use the application at the same time (e.g. multiple users try to transfer money simultaneously).
Security Testing
For a banking application, this is one of the most important steps. In security testing, the goal is to check the system’s ability to fight against the attacks. Also, it is checked that only authorized and authenticated users are allowed to access the application and their data is secured.
Security Testing Checklist
- Check whether the application has a proper process of authenticating the users on the platform. For example – apart from User Id and Password, users can be asked to enter the CAPTCHA.
- Check whether multiple invalid logins are allowed.
- Verify that the ‘Forgot Password’ and ‘Forgot User ID’ features have proper mechanisms to recover the password and User ID.
- Check whether the password policies are strong.
- Check whether user IDs and passwords are encrypted.
- Verify that the application has a secure protocol e.g. HTTPS.
- Check whether sensitive information is displayed encrypted at the client-side.
- Check whether input validations are performed at the server-side.
- Verify if the passwords are stored in cookies or not.
- Check whether information stored in cookies is in encrypted form.
- Check whether proper session timeout mechanisms are placed. (e.g. after a few minutes of inactivity, the user should be logged out automatically).
- Check application working when the user clears the cache. (e.g. user should be logged out).
- Check whether the URLs have sensitive information.
- Verify the application for SQL, XML, HTTP header, HTTP parameter, XPath, regular expression injections.
- Check whether the ‘Back’ icon of the browser is disabled for certain pages. Usually, in banking applications, the ‘Back’ icon click is not allowed.
Usability testing
Any banking application will have a broad spectrum of users, from tech-savvy people to non-tech friendly people. The goal of usability testing is to check the application’s working from all the users’ perspectives and see if the application is user-friendly for all types of users.
Usability testing Checklist
- Check whether the user is able to navigate through the application smoothly.
- Check whether buttons and links have uniform fonts, color, and size.
- Verify that the whole application has uniform fonts, text size, and color combination.
- Check whether important and critical, messages and buttons are visible clearly on the page. For example – in the transaction process, any important message should be displayed clearly with the bigger fonts and dark colors, if possible.
- Verify that critical information is displayed without any grammatical errors.
- Check whether critical processes of the application have smooth and easily understandable steps. For example – for deposit accounts, there can be a separate menu item where users can manage all the deposit accounts.
- Check whether each page has a title.
- Verify that all the links and buttons have text that is easy to understand.
- Check whether the error messages of the fields are easy to understand.
- Check whether all the important fields have placeholders and tooltips.
Performance Testing
The goal of performance testing is to check application performance under severe load and stress.
Performance Testing Checklist
- Check application performance when multiple users login at the same time and use different functionalities.
- Check application performance when multiple users login at the same time and use the same functionality. For example – all the users try to transfer the money.
- Verify the application performance when the device battery is low.
- Check application performance when the device battery is high.
- Check application performance when the device is charging.
- Verify the application performance when a user tries to use the same function multiple times in a defined period. For example – the user tries to transfer money from the same account to different accounts within an hour.
- Check application performance when network connectivity is low. For example – during an ongoing transaction if the network has a sudden fluctuation.
- Check application performance when network connectivity is zero. For example – during an ongoing transaction if there is no network.
- Check application performance when the network keeps fluctuating between low and high speed.
- Check application performance during a sudden crash.
User Acceptance Testing
In this step, the client or end-users of the system (usually, representatives of the client) test the system to get an assurance that the application will run smoothly as per desired behavior in real-world scenarios.
Apart from the above-mentioned phases, there are many other important phases. We include these in the testing process of a bank application such as regression testing, compatibility testing, etc.
User Acceptance Testing Challenges
- Bank applications have multiple users in the range of millions. Simulating such a high number of users may create a challenge for the testing team. Testing teams can go for automation tools used for performance testing.
- As there are multiple users, all the users will be using different devices, connections, and operating systems. Testing on each combination of devices, OS, and connections is a complex, time-consuming process.
- Testing bank applications need extra care and time as it deals with money and sensitive information.
- Checking from all the security perspectives and covering all the security testing scenarios is very critical.
- Another important challenge is to test the application for rollback mechanisms if there is a failure in the system.
- Bank applications allow utility payments and many other third-party integrations. Testing them will be a challenge for the testing team as each integration is different.
Conclusion
Banking applications are in demand even in developing countries as nowadays people prefer online services and avoid physically going to the branch. Moreover, in this fast-paced life, people will always choose fast online transactions for any service or product they are purchasing. There are many other reasons why banking applications are gaining popularity.
Given the sensitive and complex nature of these applications, it is critical to test them thoroughly. As mentioned in the above sections, there are various phases in banking application testing. Of course, many challenges are faced during the testing process. But it becomes the responsibility of the testing team to find as many bugs as possible to achieve the highest quality.
Kuldeep Rana
Kuldeep is the founder and lead author of ArtOfTesting. He is skilled in test automation, performance testing, big data, and CI-CD. He brings his decade of experience to his current role where he is dedicated to educating the QA professionals. You can connect with him on LinkedIn.
FAQs
What is banking domain project in interview for testing? ›
The banking domain is nothing but a software division in a bank. Most of the banks are computerized now, the required software which is used will be under maintenance and very little enhancements. The members who work on this s/w can say that they are in the banking domain.
How do I get domain knowledge in banking? ›Banking Domain Knowledge
It covers the transaction and distribution process; the ways in which customers interact with the system, products, and services the organization offers; and the technology involved. By combining all these components, a financial specialist can create a bank operating model.
User Acceptance Testing − User Acceptance Testing (UAT) is the final stage of testing performed by end-users to check that the application is compliant with real-world scenarios. Security testing assures that the program is free of vulnerabilities.
How do you perform a domain test? ›- Analyze beforehand what can go wrong while setting boundaries.
- Prepare strategies to handle each case.
- Checkpoints to conduct error testing.
- Use one test point to evaluate adjacent domains.
- Check off unnecessary test points.
- Run the test.
- Check for errors in boundaries.
Domain testing is an important software testing technique in domain testing, we divide a domain into subdomains and then test using values from each subdomain. For example, if a website has been given for testing, we will be dividing the website into small parts (subdomains) for ease of testing.
What is banking domain project? ›Banking Domain Testing is a software testing process of a banking application for functionality, performance, and security. The main purpose of testing banking application is to ensure that all the activities and functionalities of a banking software run smoothly with no errors and it remains protected.
What does banking domain mean? ›Banking domain concepts refers to the various areas or components for which the knowledge is collected to understand how the specific field or banking segments operate around the products and services, sales and distribution, customers, process, technology and people. Topics Below. Definition of banking domain concepts.
What are the different domains in banking? ›It can provide checking and savings accounts, Deposits, credit cards, mortgages, auto loans, personal loans, small business loans and more. A bank can also offer services such as cashier's checks, money orders, wire transfers, safe deposit boxes, currency exchange, and investing or wealth management.
What is basic domain knowledge? ›Domain knowledge is the understanding of a specific industry, discipline or activity. Anyone can have domain knowledge in any subject, even those outside their job industry. Domain knowledge can be hobbies, passions, personal research topics, professions or specializations in an industry.
Which testing is mostly used in banking application to run the transaction after banking hours? ›Banking applications are critical as they involve millions of transactions with real money and confidential financial data. Testing these applications is fundamental and includes load & performance testing, of course security testing, also usability testing and obviously functional testing.
How do you test financial applications? ›
- Check if new accounts are created correctly with valid data;
- Use functional testing type to check how an application behaves if the accounts are created with invalid data;
- To make sure your account is secure, check login functionality with invalid data;
The core banking testing process for financial systems ensures that all banking transactions are executed correctly and accurately as well as remain safe and secure. The testing process needs more time, resources, and continuous monitoring.
What are test bank questions? ›Test banks are a compilation of a professor's test questions from past semesters. When students are either given back an exam or allowed to leave the class with it, some students put the questions from these tests into a database for future students of the same class to use.
What are the 4 types of acceptance testing? ›- User Acceptance Tests (UAT) ...
- Business Acceptance testing (BAT) ...
- Contract Acceptance Testing (CAT) ...
- Regulations Acceptance testing (RAT) ...
- Operational Acceptance Testing (OAT) ...
- Alpha Testing. ...
- Beta Testing.
The UAT process can be divided into four phases. In each phase, there are several activities done, as listed below.
What are the two types of UAT? ›Types of UAT
These tests include the following: Beta testing. The software is given to groups of end users who evaluate it for its intended purpose and provide feedback to developers for improvements. Black box testing.
- BFS (Banking & Financial Sector)
- Healthcare Software Domain.
- e-Commerce Domain.
- ERP Domain.
- Mobile Application Testing Domain.
- Insurance Sector Domain.
- Retail, Travel & Hospitality sector.
Domain assessment meaning: It is a test aimed at assessing individuals' skills in specific domains. Such a test helps employers to either test job applicants or reskill employees in technical roles. The test comes in handy when recruiters aim to recruit individuals based on their domain expertise.
What comes under domain testing? ›Domain testing is a software testing technique. The output has to be tested with a minimum number of inputs, to make sure that the system does not accept invalid values or values which are out of range.
What is an example of an application domain? ›Application domains include banks, insurance companies, or hospitals. In this book, equipment management for a small software company is our main example. Internet applications have become increasingly important, especially for the home and entertainment domains.
What are three examples of domain names? ›
- bigstuff.cornell.edu.
- www.bigstuff.cornell.edu.
- server3.dept.cornell.edu.
- birdsource.org or sharedresearch.info or marysmith.us. Any domain name not ending with "cornell.edu"
- .com – commercial business (the most common TLD)
- org – organizations (typically, nonprofit)
- gov – government agencies.
- edu – educational institutions.
- net – network organizations.
- mil – military.
Banking Application Test Cases For Customers & Visitors
Check all the customers can log in with their valid credentials. Check if the Customer cannot log in with an invalid date. Check after the number of unsuccessful account access; then, the user account should be locked for that day or not.
1) Verify different user's login to the same retail banking application using different systems at same time. 2) Verify user can able to log into the retail banking application within few seconds by providing valid user id and password. 3) Verify logging into the application when the server is down.
How does domain verification work? ›You'll sign in to your domain registrar and paste the verification code in to the DNS records for your domain. Once your domain registrar publishes your verification code, we'll know you are the owner of your domain.
Why do I need to verify my domain? ›Domain Verification provides a way for you to claim ownership of your domain in Business Manager. This ownership allows you to control editing privileges of your links and other content to prevent misuse of your domain and to keep bad actors from spreading misinformation.
What are the 4 types of domain? ›- Generic Top-Level Domains (gTLD)
- Country Code Top-Level Domains (ccTLD)
- Internationalized Country Code Top-Level Domains (IDN ccTLD)
- Subdomain.
- .com: shorthand for commercial, .com was the first top-level domain in common use. ...
- net: shorthand for network, . ...
- edu: shorthand for education, . ...
- org: shorthand for organization, . ...
- mil: shorthand for military, . ...
- gov: shorthand for government, .
Learning can generally be categorized into three domains: cognitive, affective, and psychomotor. Within each domain are multiple levels of learning that progress from more basic, surface-level learning to more complex, deeper-level learning.
What are the domains skills? ›Bloom identified three domains, or categories, of educational activities: Cognitive Knowledge or Mental Skills. Affective Attitude or Emotions. Psychomotor Skills or Physical Skills.
What are the 3 domains describe each? ›
All of life can be divided into three domains, based on the type of cell of the organism: Bacteria: cells do not contain a nucleus. Archaea: cells do not contain a nucleus; they have a different cell wall from bacteria. Eukarya: cells do contain a nucleus.
What are the three types of stress testing that a bank should consider? ›The three key areas stress tests focus on the most are credit risk, market risk, and liquidity risk.
What Check system do banks use? ›Key takeaways about ChexSystems:
ChexSystems is a reporting agency that banks use to track customers who may have had issues with their prior bank account such as not paying an overdraft fee or bouncing a check. ChexSystems retains consumer records for up to five years.
Stress tests are used by financial firms (eg banks and insurance companies) for risk management purposes. They complement a financial firm's other quantitative risk management tools by providing insights into its risk profile and alerting management to vulnerabilities in the case of exceptional events.
What is API testing in manual testing? ›API testing is a type of software testing that analyzes an application program interface (API) to verify it fulfills its expected functionality, security, performance and reliability. The tests are performed either directly on the API or as part of integration testing.
How do you write a test case for a bank transaction? ›Test Steps for Bank Transaction
Add the beneficiary to whom you want to transfer money. Check the details of bank account and person. Verify if they are correct. Select the specific money transfer method from NEFT/RTGS or SWIFT transfer options.
Mobile banking apps allow you to access your banking accounts and conduct financial transactions using a mobile device, anytime and from anywhere. With a mobile banking app, you can easily keep track of your transaction activities, such as checking your bank passbook and everyday transactions.
What is an aptitude test for a bank job? ›Typically, you will be tested on numerical reasoning, situational judgement, abstract reasoning, verbal reasoning and your personality type. Results of these tests give an indication of how you might perform as an employee in a banking company.
What is big bank testing? ›Big bang integration testing is a testing methodology in which all components or modules of a system are combined and tested as a whole. It is often used when it is not practical to test all components together incrementally.
How do you explain investment banking domain project? ›Introduction to Investment Banking Domain:
The main role of the Investment Bank is to act as a mediator between the companies (who are interested in selling their securities/shares) and the individuals (who are willing to purchase the same). Investment bank operates in two ways – 'buy side' and 'sell side'.
Are test bank questions cheating? ›
By convention, using a test bank is generally considered academic dishonesty. If you don't consider it to be so for your exam, you should make sure students know this. Otherwise, you may penalize the more ethical students who would have otherwise studied from the test bank and performed better on the exam.
Is bank test easy? ›...
Why Candidates Fail To Qualify IBPS Bank Exam.
| Bank Exams Related Links | |
|---|---|
| IBPS Clerk | RBI Admit Card |
| RBI Grade B | IBPS SO |
It is a software testing technique where minimum numbers of inputs are used to access appropriate output of a system, to ensure the system does not accept invalid input values. The system is expected to give required outputs blocking the invalid inputs.
How do I test my middleware application? ›- Build and start a host that uses TestServer.
- Add any required services that the middleware uses.
- Add a package reference to the project for the Microsoft. AspNetCore. TestHost NuGet package.
- Configure the processing pipeline to use the middleware for the test. C# Copy.
February 2021) Banking, financial services and insurance (BFSI) is the industry's umbrella term for companies that provide a range of such financial products or services. This includes universal banks that provide a range of financial services or companies that operate in one or more of these financial sectors.
What are the types of domain testing? ›- Intuitive equivalence.
- Specified equivalence.
- Subjective equivalence.
- Risk-based equivalence:
- Analyze requirements from the software requirement specification document.
- Create a clear test plan.
- Write test cases that cover all the requirements defined in the document.
- Get test cases reviewed by the QA lead.
- Execute test cases and detect any bugs.
Testing the crucial connections between your systems to check they're providing the right data to the right processes - and getting the right results.
How do you write a middleware unit test? ›- Test the business logic, and nothing else. ...
- Mock or stub only the needed parts coming from Express, nothing more. ...
- Stay typed (use official Express types) ...
- Simple example — authorization header guard middleware. ...
- Keep the DRY principle (Don't Repeat Yourself) ...
- Practice, practice a lot.
Common middleware examples include database middleware, application server middleware, message-oriented middleware, web middleware, and transaction-processing monitors.