A Complete Guide to Testing Banking Applications: BFSI (Banking, Financial Services, and Insurance) Testing Process and Tips
Banking applications are one of the most complex applications in today’s software development and testing industry.
What makes banking applications so complex? What approach should be followed to test the complex workflows involved in banking applications?
In this tutorial, we will be highlighting the different stages and techniques involved in testing Banking applications.
Table of Contents:
How To Test Banking Applications?
The various Functions performed by Banking Applications are:
Let’s first understand the characteristics of a Banking Application:
- Multi-tier functionality to support thousands of concurrent user sessions.
- Large-scale Integration: Typically, a banking application integrates with numerous other applications such as Bill Pay utility and Trading Accounts.
- Complex business workflows
- Real-Time and Batch processing
- High Rate of Transactions per second
- Secure Transactions
- Robust Reporting section to keep track of day-to-day transactions.
- Strong Audit to troubleshoot customer issues.
- Massive storage system
- Disaster / Recovery Management
The 10 points listed above are the most important characteristics of a banking application.
Banking applications have multiple tiers involved in performing an operation.
For example, a Banking application may have:
- Web Server to interact with end-users via Browser.
- Middle Tier to validate the input and output for the webserver.
- Database to store data and procedures.
- Transaction Processor which could be a large capacity Mainframe or any other Legacy system to carry out Trillions of transactions per second.
When we talk about testing banking applications, it requires an End to End Testing methodology involving multiple Software Testing techniques to ensure:
- Total coverage of all banking workflows and Business Requirements.
- The functional aspect of the application
- The security aspect of the application
- Data Integrity
- Concurrency
- User Experience
What makes banking applications so complex?
- Banking software mainly deals with confidential financial data so the performance of software should be error-free and secure.
- Developers prefer a complicated design to develop these applications to ensure that the application runs in a desired secure manner.
- Banking is a constantly changing world. Banking, today, is made available to the customer using different channels like brick & mortar branches, ATMs, online banking and customer care.
- With the advent of technology, many wallets have flooded the markets that connect to the banking systems for financial transactions.
- Banking is also expected to be up and running 24/7 with high performance. Software upgrades, instant fixes, etc. cannot be allowed to impact this availability.
- The banking world is also highly impacted by the constant changes brought in by the government in the form of banking regulations. Any changes to the tax structure will impact the banking system as well.
- The banking system also needs to be up-to-date as far as new technologies are concerned. Data analytics like Big Data Processing and getting instincts out of big data using Data Science is growing traction in the banking world.
The above mentioned points make the banking system complex for developers to create a software application around it.
Importance of Testing Banking Application
- Testing the Banking application assures that all the activities are not only executed well but also remain protected and secured.
- Banking software is complicated with thousands of dependencies, and the testing process requires more time, resources, and continuous monitoring.
- As finances are involved here guidelines have to be followed strictly. Both testers and developers should have good domain knowledge.
- Most importantly, it has to be ensured that the laws and regulations are enforced correctly in financial transactions. This can only be ensured with testing.
- It’s also important to ensure that the application and the infrastructure on which the application has been deployed is able to handle the load, especially during peak business hours, without causing any disruption. This can be ensured by performing performance testing.
- In today’s digital world, the one thing that concerns everyone is that of security. The banking applications and the financial transactions that are performed within it need to be secure from any attempt to break-in. This can be ensured by performing security testing. Security testing helps to enforce industry standards to secure financial transactions.
- It’s also important to ensure that different modules of a banking application are integrated properly and the objective of the client is achieved. System Integration Testing helps to achieve this task.
Banking App Testing Workflow
The typical stages involved in testing Banking Applications are shown in the below workflow. We will be discussing each stage individually.
This is the Waterfall model for testing an application.
#1) Requirement Gathering
Requirement Gathering Phase involves documentation of requirements either as Functional Specifications or as Use Cases. Requirements are gathered as per customer needs and documented by Banking Experts or Business analysts.
Experts are involved in writing requirements on more than one subject as banking itself has multiple sub-domains and one full-fledged banking application will be the integration of all these domains.
For example, a banking application may have separate modules for Transfers, Credit Cards, Reports, Loan Accounts, Bill Payments, Trading etc.
#2) Requirement Review
The deliverable of Requirement Gathering is reviewed by all the stakeholders such as QA Engineers, Development leads and Peer Business Analysts.
They cross-check that neither the existing business workflows nor new workflows are violated. All the requirements are verified and validated. Follow up action and requirement document revisions are done based on the same.
#3) Business Scenario Preparations
In this stage, QA Engineers derive Business Scenarios from the requirement documents (Functions Specs or Use Cases); Business Scenarios are derived in such a way that all Business Requirements are covered. Business Scenarios are high-level scenarios without any detailed steps.
Further, these Business Scenarios are reviewed by Business Analysts to ensure that all Business Requirements are met. It is easier for BAs to review high-level scenarios rather than reviewing low-level detailed Test Cases.
For example, a customer opening a Fixed deposit on the digital banking interface can be a business scenario. Similarly, we have different business scenarios related to net banking account creation, online deposits, online transfers, etc.
#4) Functional Testing
At this stage, functional testing is performed and the usual software testing activities are performed such as:
Test Case Preparation: At this stage Test Cases are derived from Business Scenarios, one Business Scenario leads to several positive and negative test cases. Generally, tools used during this stage are Microsoft Excel, Test Director, or Quality Center.
Test Case Review: Reviews by peer QA Engineers
Test Case Execution: Test Case Execution could be either manual or automatic by involving tools like QC, QTP, etc.
The functional testing of a banking application is quite different from ordinary software testing. Since these applications operate with customer’s money and sensitive financial data, they are required to be tested thoroughly. No important business scenario should be left to be covered.
Also, the QA resource who is testing the application should have the basic knowledge of the banking domain.
#5) Database Testing
Banking Application involves complex transactions which are performed both at UI level and Database level, Therefore, Database testing is as important as functional testing. The database is complicated & is an entirely separate layer in the application and thus its testing is carried out by database specialists.
It uses techniques like:
- Data loading
- Database Migration
- Testing DB Schema and Datatypes
- Rules Testing
- Testing Stored Procedures and Functions
- Testing Triggers
- Data Integrity
The major purpose of database testing is to ensure that:
- The Application is able to store and retrieve data from the database without any loss of data.
- Completed transactions should be committed and aborted transactions should be reverted back to avoid any mismatch in data stored.
- Only authorized applications and users are allowed to access the database and the underlying tables.
There are primarily three ways of Database Testing:
- Structural Testing
- Functional Testing
- Non-Functional Testing
Structural Testing
It involves testing database objects like databases, schemas, tables, views, triggers, access controls, etc. Ensuring that data types in tables are in sync with the corresponding variables in the application. Validating data and referential integrity in the tables.
For example, the amount field in the application should have a data type of decimal/float in the table.
In order to comply with these standards, users should be given access controls through views.
Functional Testing
It involves testing the databases that satisfy user requirements. There are two ways to achieve this i.e. black box testing and white box testing.
For Example, when we do an online money transfer, the sender’s account should be debited and the recipient account should be credited with the exact same amount. If the transaction fails then the whole transaction should be reverted and the sender’s account should not be debited or credited back.
Non-Functional Testing
It involves load & stress testing and performance optimization. Load testing helps in identifying the most number of transactions that can be performed concurrently without impacting database performance.
For example, based on the input from load and stress testing, banking applications can decide to add more resources to their application during peak business hours and reduce the resources during off business hours. This helps the bank to make optimum use of resources and save money.
#6) Security Testing
Security Testing is usually the last stage of the testing cycle. A prerequisite for commencing security testing is the completion of functional and non-functional testing. Security testing is one of the major stages of the entire Application testing cycle as this stage ensures that the application complies with Federal and Industry standards.
Due to the nature of the data they carry, banking apps are very sensitive and are a prime target for hackers & fraudulent activities.
Security testing ensures that the application does not have any such web vulnerability that can expose sensitive data to an intruder or an attacker. It also ensures that the application complies with standards like OWASP.
At this stage, the major task is the whole application scan which is carried out using tools like IBM AppScan or HP WebInspect (these are the most popular tools).
Suggested read =>> Top competitors to WebInspect
Once the scan is completed, the Scan Report is published. Over this report, False Positives are filtered out and the rest of the vulnerabilities are reported to the Development team so that they can start fixing the issues depending on the severity of each issue.
Penetration testing is also done at this step to reveal the propagation of errors. Rigorous security testing should be done across platforms, networks, and OS.
A few other Manual tools for Security Testing used are Paros Proxy, Http Watch, Burp Suite, and Fortify.
The main purpose of security testing is to pinpoint any vulnerabilities that the software application may have.
Security Testing tests the application against:
- Any external attack or attempt to hack the application with malicious intent.
- Any loophole in the software application could be exploited causing data or monetary loss.
- Any vulnerability in the network, servers, or workstations that hosts the application.
Given below are the various types of Security Testing:
Vulnerability Testing: An automated program is developed and executed to check for various vulnerabilities.
Security Scanning: This variant revolves around investigating network & system vulnerabilities, thereby providing solutions to reduce the associated risk.
Penetration Testing: This variant of security testing imitates a hacking attempt to capture vulnerabilities and loopholes, which otherwise could have gained access to the database or the application data.
Security Audit: This involves auditing the application and the associated networks for any security lapses.
Risk Assessment: This variant does an analysis to assess the level of risk, in an event when a vulnerability or loophole is exploited for malicious intent. Such risk could be categorized into low, medium, and high. Based on the level of risk, proper measures are advised by the testing team to reduce or avert the risk.
Ethical Hacking: This is performed by an organization on its systems to identify loopholes that could be exploited in its application or network. The intent of this kind of hacking is not to steal or cause damage to the application or network.
Posture Assessment: This is an umbrella assessment that comprises security scanning, risk assessments, and ethical hacking.
SQL Injection: SQL Injection could be used to gain access to the server database. Testing is done to ensure that the code is working correctly, which executes queries in the database based on the following inputs from the user:
- Brackets
- Apostrophes
- Commas
- Quotation Marks
Other Stages in Testing the BFSI App
Apart from the above main stages, there might be different stages involved such as Integration Testing, Usability testing, User acceptance testing, and Performance Testing.
Let’s talk briefly about these stages as well:
Integration Testing
As you know, in a banking application, there might be several different modules like transfers, bill payments, deposits, etc. Thus, there are a lot of components developed. In integration testing, all the components and integrated together and validated.
Usability Testing
A banking application serves a wide variety of customers. Some of these customers might lack the skills and awareness required to perform banking tasks over the app.
Thus, the banking application should be tested for simple and efficient design to make it usable across different groups of customers. The simpler & easier use interface is, the higher the number of customers will benefit from the banking application.
Further Reading => List of the TOP Online Business Banks of the Year
It’s about examining the level of ease that business users or bank customers have in using the application. This testing is not performed by the developer or tester but is performed by the business users.
For example, nowadays everyone uses mobile apps. The banking app should be user-friendly and easy to understand and use by the end-user.
Types of Usability Testing
Comparative Usability Testing: This is a comparison-based testing, where the ease of usability of one website or application is compared with another. The target for such testing is to provide the best user experience.
Explorative Usability Testing: The aim of this testing is to identify what features the new application or software should possess in order to meet the bank’s customer requirements.
Given below are the advantages and disadvantages of Usability Testing
Advantages:
- The end-users of the application are usually involved with the testing, hence first-hand feedback is obtained.
- Rather than spending time on analysis and discussion about a feature that a product should have or not, it is better to get the inputs from the end-user directly.
- We can catch any potential issues beforehand.
Disadvantages:
- As multiple end-users are involved in testing, their opinions, if not precise, can affect the requirement.
- The feed from end-users may be influenced.
Performance Testing
Certain periods of time, like payday, the end of the financial year, and the festive season, might bring in change or spike in the usual traffic on the app. Hence, thorough performance testing should be done so that customers don’t get affected by performance failures.
A significant example of the past where bank customers were personally affected due to performance failures is the NatWest and RBS cyber Monday IT outage in which customers had their debit and credit card declined transactions across shops in the country.
User Acceptance Testing
This is done by involving the end-users to ensure that the application complies with real-world scenarios and will be accepted by users if it goes live.
In today’s scenario majority of Banking Projects are using: Agile/Scrum, RUP, and Continuous Integration methodologies and Tools packages like Microsoft’s VSTS and Rational Tools.
As we mentioned about RUP above, RUP stands for Rational Unified Process, which is an iterative software development methodology introduced by IBM which comprises of four phases in which development and testing activities are carried out.
Four phases are
i) Inception
ii) Collaboration
iii) Construction and
iv) Transition
RUP widely involves IBM Rational tools.
Sample Test Cases for Banking Application
Test cases for New Branch
- Create a new branch with valid and invalid test data.
- Create a new branch without data.
- Create a new branch with existing branch data.
- Verify the reset and cancel options.
- Update branch details with valid and invalid test data.
- Update branch details with existing branch test data.
- Verify if the new branch can be saved.
- Verify if the cancelation option is working.
- Verify the branch deletion with and without dependencies.
- Verify if the branch search option is working.
Test Cases for New Role
- Create a new role with valid and invalid test data.
- Create a new role without data.
- Verify if a new role can be created with existing test data.
- Verify the role description and role type.
- Verify that the cancelation and reset options are working.
- Verify the role deletion process with and without dependency.
- Verify the links in the role details page.
- Verify the admin login without test data.
- Verify all home links for the admin role.
- Verify if the admin can change the password with valid and invalid test data.
- Verify the admin log out successfully.
Test cases for Customer and Banker
- Verify if all visitor and customer links are working properly.
- Verify the customer’s login with valid and invalid test data.
- Verify the customer’s login without any data.
- Verify the banker login without any data.
- Verify the banker’s login with valid or invalid test data.
- Verify if the customer or banker was able to log out successfully.
Test cases for New users
- Verify if the new user can be created with valid and invalid test data.
- Create a new user with existing branch test data
- Verify if the cancel and reset options are working properly.
- Update user details with valid and invalid test data.
- Verify the deletion of the new user.
- check if the new user can be verified.
- Verify mandatory input parameters.
- Verify optional input parameters.
- Verify if a user can be created without optional parameters.
Test cases for the creation of a New Account
- Create a new account with valid and invalid user data.
- Verify if the user details can be updated.
- Verify if a new user can be saved.
- Create a new account with existing user data.
- Verify that the user can deposit the amount into the newly created account (and update the balance).
- Verify if the user can withdraw the amount from the new account (after depositing and updating the balance).
- In the case of salary, the account verifys the company name and other details provided by the user.
- Verify if the primary account number is provided in case of a secondary account.
- Verify the user details provided in the case of the current account.
- Verify the provided proof for the joint account in case of a joint account.
- Verify whether you are able to maintain a zero balance in your salary account.
- Verify whether you are able to maintain a zero balance or minimum balance for a non-salary account.
- Verify that the new user was able to log out successfully.
Test Cases For Net Banking Application
- Check if the user is able to open the bank site.
- Check if all the links on the site are working.
- Verify if the user is able to create a new account.
- Check if the user is able to log in with a valid and invalid username and password.
- Verify if either the username or password is blank while logged in, the user should not be allowed to log in and an alert message should be shown.
- Check if the user is allowed to change the password.
- If an invalid username or password is entered, a proper error message will be shown.
- Users with an invalid password should not be allowed to log in.
- Verify that after repeated attempts to log in with an incorrect password, the user should be shown an error message and blocked.
- Check if the user is able to perform some basic transactions.
- Verify that the user is able to add a beneficiary with valid and invalid details.
- Verify if the user can delete the beneficiary.
- Verify that the user is able to make transactions to the newly added beneficiary.
- After the transaction, verify if the accounts of both the user and beneficiary have been updated.
- Check if the user is able to enter the amount in decimal numbers.
- Verify if the user is not able to enter negative numbers in the amount field.
- Verify if the user is allowed to make transactions with or without a minimum balance.
- Verify if the user can make a new RD.
- Verify that the correct message is showing in case of a transaction done with insufficient balance.
- Check if the user is asked for confirmation before any transaction is made.
- Verify if acknowledgment receipts are provided on each successful transaction.
- Verify if the user is able to transfer money to multiple accounts.
- Verify if the user can cancel the transaction.
- Verify that the account details reflect the financial transactions done.
- Verify that the timeout feature has been implemented.
- Verify that in case of session time out a user should log in again.
- Verify that the proper session time out is done in case of any inactivity.
- Verify that while doing the transaction the user is taken to secure mode.
- Verify if the user was able to log out successfully.
- Verify search and reset options.
Conclusion
In this tutorial, we discussed how complex a banking application could be and what are the typical phases involved in testing the application.
Apart from that we also discussed the current trends followed by IT industries including software development methodologies as well as tools.
Feel free to share your experience or queries on this topic!
Was this helpful?
Recommended Reading
-
In this article, you will learn in detail how to test an Investment Banking Application. We have provided you with enhanced clarity on the Investment Banking Domain. Before we dive deeper into how to test investment banking applications, it's important to understand this domain first. We will first learn about…
-
In this article, we are going to see all about “How-to” test the retail banking system. So, come on along. Introduction to Retail Banking: It refers to the banking that executes direct transactions with consumers/customers rather than corporations / companies or other banks. Retail banking is also known as Consumer…
-
This guide is a detailed understanding of the Healthcare Domain and Healthcare Application Testing. Also explore, the test scenarios for different applications under the Healthcare domain: This is going to be all about healthcare- domain/business information, components, what to test, and how to test. Towards the end, we will pick…
-
Upload and install your mobile application on any device to kick off your Appium testing directly from Eclipse: Your mobile applications can be managed within the Eclipse through a dedicated Application Pane in Appium Studio for Eclipse. Your application can quickly and easily be uploaded and launched on any device. This…
please share to this mail id : bgh209@yahoo.in
Hi,
I have worked in Insurance Domain throughout where I have dealt with modules viz New Business, Underwriting, Admin, Commissions, etc. and this is standard in all the admin systems (read applications).
I would like to know if there is any such standard or best practice that Banking Domain follows.
Thanks!
hi..manushri,can u pls share the flow of insuance domain application..and what are the different modules in it?
this is nice article and easily understand to who are new in banking sector for testing …….
keep it up
We are doing the software exclusive business in Nepal. Please advise to us, Thanking you
can u provide us with some examples of business scenario preparations from business requirement documents by QA team
Whereas a Use Case contains User Actions and FOrmat is like :
1. Pre Condition : ATM should be up and Running , Use has an ATM Card
2. Basic Flow:
* User Inserts ATM Card
* User Enters PIN
* User selects Enter
* User selects Withdrawl
* User Enters Amount
* User Confirms
* User Selects YES for Reciept
* User Collects Cash
* User Collects Reciept
* User Collects Card
3. Exceptions :
* User enters Wrong PIN
* User enters Wrong Amount
* ATM is out of Cash
* Any Other
This is an Use Case from which Business Scenarios and Test Cases are Derived
Can anyone pease tell me how can i explain auto insurance project in the interview. I showed on my resume that i worked on geico Auto insurance in the usa But i Need some Help How can i explain the geico INSURANCE project. How Can i explain what modules i tested . Please if anyone can help to answer it.
Is there any particular exams that one could give in order to get a “Certification” in Banking domain?
Very Nice article really.
Very nice article on banking application. helpful to the readers.
HIII
anyone can send home loan test cases….?
Kya koi muje Manual testing me job dilwa sakta h?? , i can pay for this
I also want
@Mah
You are correct , Thanks for correcting the Typo
which model(sdlc) is used in banking project
Superb!!!! Very helpful
very nice article it is very useful
Really cool stuff. Whenever I have free time, I come here and explore. Thanks for the great content.
hi all, any guide for billing testing? thanks
I like her
Structured, informative article. Could you let me know how to frame E2E test cases for modules related to core banking application & associated applications connected to it?
Hi Mohit,
Can you take a real time example and explain me the flow of testing for any banking application like for example online payment system or any other application. I am a fresher in software testing and i need your help in understanding how the projects are handled within a team in a banking environment
Thanks in advance!
For Banking Application testing,Tester must Banking domain knowledege. Tester must have to relate the day to day banking activity and logic while testing the Banking Application.
hi,
i need live project help on banking domain.please help me out.
Hi ,
Need to know how Banking and financial services applications captures Country Code data and currency code data via API integration
I’m doing software testing course.getting a testing job in banking domain is it that much difficult?
Above articale is very knowledgeable
Can anyone send me Banking domain Project Detail and
easy understandable with sample documents on my email
akritivaidya50@gmail.com
Thanx
Hai ,very nice article .i have also one question
How to write regression test case for banking application??
Can anyone please tell me how can i explain State Street project in the interview. I showed on my resume that i worked on State Street Bank in the usa But i Need some Help How can i explain the project. How Can i explain what modules i tested . Please if anyone can help to answer it.
Testing banking applications sounds more interesting and it’s massive system. But i am still a greenhorn in testing so i would like to know that what is the difference between business scenario and use case?
if some can help me with Mortgage Application / banking
Test cases , UAT test cases . And sanerios
What No.of tools use in banking application software testing ?
Its really nice article for those who have just entered in Banking domain
Business Scenario is a High Level Scenrario from which Test Cases are Written.
Lets take an Example of ATM.
Test Scenarios : Withdraw Cash , Balance Enquiry Etc.
Test Cases would be with detailed steps and covering negative and positive condition.
Test Case 1 : Withdraw valid Amount
Test Case 2 : Withdraw Invalid Amount
Test CAse 3 : Withdraw 0 INR Etc.
With Detailed Steps
Hi..Can anyone help me out…
I want to know how stubs are actually used for testing banking applns in real time.. Will we have real database to check or does this have any thing to do wiyh these stubs or drivers?
I don’t see what makes your article specific to banks. this is just a summary of methods.
I am disappointed
good article
Can you explain the complete testing with an real time application and test cases
I want some test cases for zerodha -buy and sell function..if possible please help
thank you very much ,this article is really informative..
but i just want to say that second phase in RUP development cycle is not “collaboration” , it’s “elaboration”
source : http://www.ibm.com/developerworks/rational/library/content/03July/1000/1251/1251_bestpractices_TP026B.pdf
this article really very helpful for banking knowledge
good stuff for beginners
Hi,
Where do we get std spec documents for financial applications?
This article is good and definitely help me in testing of banking products
can anyone help me out.. test cases for “contactus” page in bank
Sir,
I am a fresher i want to know the different domains in testing for my career growth.
Can you please explain some of the modules in Banking Domain.
Can we check that manually?if yes,please explain how?
I am an official with one of the top public sector banks. I have been working in many softwares like bankmaster, banc@24, exim bills, mercury (Forex), SWIFT etc. Now I prefer to switch over to IT industry in the area of testing. Can u please tell me Whether I am already exposed to testing (User acceptance)? If so, How I can project the same in my CV?
Very nice article. It gave me an over view to prepare for my project .Iam trying hard to put my foot in to the testing field.Can you also give me an over view of how
Health Insurance domain ,auto insurance domain,general motors work’s.It would be huge help.
Thank you
How to explain banking project with tax registration purpose please help me
Really nice article it is really helpful for me
Thank you….
ITS VERY USEFUL ARTICLE. I THANK TO U FOR GIVING SUCH A GOOD ARTICLE.
Good one……..
hi,am a fresher.please help me out.what is system integration testing?who does it manual or automated tester ,if then how in banking or finance application
please tell me how to write Test cases about Banking Domain.
hello, manishak003@gmail.com this is my email id. plz send me the testcaes related to funds transfer, customized bank statement and account creation.
if you have test cases then please send me too…. testdlpuploads@gmail.com
Thank you for your article. Its very useful for beginners.
please anyone share banking domain related docs. which will be useful to manually test banking applications. i.e. how to test funder trfr module end to end
My email is ppratixa5@gmail.com. Please anyone can send me email for the above request which would be a great help for me.
thanks for the article. please post some test cases related to banking sector.
hai iam anand have nice year
If any job requrement or job vacancy
contact me raysoftanand@gmail.com
Hi,
Can anyone send me Banking domain Project Detail and
easy understandable with sample documents or sample module on my email.my email is madhu09438@yahoo.com.
basically Mini statement, Customized statement , balance inquiry ,
hey have you get the project from any1
i am also searching for the same.
Hi,
Where do we get std spec documents for financial applications?
which is the best site for prepare the banking application in software testing
SI No Internet Banking
1 Verify the bank website URL.
2 Verify if the bank website URL has HTTPS on the address bar and in the URL.
3 Verify if the bank website login page does not appear forged.
4 Verify if the bank login page has username and password.
5 Verify the username and password are being accepted or not.
6 Verify that user with invalid password is not allowed to login.
7 Verify that if either of the username or password is blank, user is not allowed to login. User should be given an alert also.
8 Verify that after repeated attempts to login with incorrect password( as per the limits), user should be blocked.
9 Verify if the SMS authentication is triggered after login.
10 Verify that user is allowed to change password
11 Verify if the user is redirected to the dashboard after passing all authentication processes.
12 Verify if the user has access to the online money transfer feature.
13 Check if the user can transfer funds option is available during specific time period (9 am to 5pm).
14 Check if the fund transfer option shows notice for off-business hours transaction.
15 Verify if the user can add the beneficiary.
16 Verify if the beneficiary details can be verified.
17 Verify that user is able to add decimal number into amount ( limited by 2 numbers)
18 Verify that user is not able to add negative number into amount field.
19 Verify that user is allowed to transfer money only if there is proper account balance.
20 Verify that there is a confirmation check for financial transactions
21 Verify that user is given an acknowledgment receipt upon successful financial transaction.
22 Verify that customer is able to send money to multiple people
23 Verify if the fund transfer option allows NEFT or RTGS option for nationalized money transfers.
24 Verify if the fund transfer page asks for beneficiary name, IFSC code, bank name and fund amount and purpose of transfer.
25 Verify if the fund transfer page asks for PAN number if the amount of funds gets over 50k.
26 Check if the fund transfer page has an 2-step authentication before you finalize transfer.
27 Check if the inter bank fund transfer happens instantly or not.
28 Check if the amount of time it takes for the funds transferred between the in-business hours.
29 Check if the amount of time it takes for the funds transferred between the off-business hours.
30 Check if the amount transferred notification is sent to sender and receiver.
31 Check if the amount gets transferred to the exact person mentioned in the beneficiary.
32 Verify that time-out feature is implemented
Thanks, this information is very useful for me. I have 2.5 year experience in banking domain.
Hi sir I am a fresher, I wanted to work on some projects and put it in my resume, i have to work on a project “Online Banking” module is to make payment. give me some ideas how to proceed with testing
What a nice article. Thank you very much!
can you please share banking domain most interview questions and answers?
hi this article is just a summary of Testing methods and not for specific Banking Project…..
I am disappointed
hi,
nice article can you please send banking related qtp scripts, manual testing projects for writing test cases, scenarios,… my mail id-“apparao.upp@gmail.com”
thank u sir..
HAI,This is a brilliant article and really appreciable.Few
Questions :1) What are the documents Used and produced in requirements gathering,review and business scenario preperation phases? 2)Are functional specifications derived from business scenario? or Are Business scanarios derived from Functional spec? Pls let me know.
Hi Team
Please help me how to prepare UAT script to test General Banking transactions in the banking application.
Sir, I wanted to work on some projects and put it in my resume, i have to work on a project “Online Banking” module is to make payments.Please can you please send banking related qtp scripts, manual testing projects for writing test cases, scenarios, and other support docs.
Thanking You
Nice Article. Thanks for giving tools for security testing
Can anyone send me Banking domain Project Detail and
easy understandable with sample documents or sample module on my email.my email is nileshnikam2012@gmail.com
Please help me….
Thanks
Nice article, Presently i am working in retail domain as qa . I am interest in banking domain,can you please tell me how Can I improve banking domain knowledge because I do not have enough knowledge about it
Hi frnds gud eveng to one an all who involved in this posting the opinions before asking my query i request to all to give your valuable advice without fail my queryis i am about 5 n half yrs got experienced in the qc dept as a testing engineer on core field now planning to shift to software testing i passed my graduation in 2007 how should i forward my resume as a fresher or exp.if not so can i get any real time project pl guide me.
What is requirment analysis?
Hi sir ,I am a fresher, I wanted to work on some projects and put it in my resume, i have planeed to work on a project “Online Banking for Retail Customers” module is to make payment. give me some ideas how to proceed with testing
Hi Mohit,
Do you have any idea about finacle application testing?
send me some examples in banking applications
Hi, I just started learning Banking applications. This post really helps me.
I want to know about Cards and Payments options used in a Banking application.
Thanks in advance !!!
Can u provide some test scenarios for bank application
Worthful!
This is what every newbie wants to get his concepts cleared at one stroke. @Mohit , Good work. Keep us posted.
A good article which is very informative and easy to understand.
very informative article to know about various types of testing. Another good resource would be nyift.com/banking-domain-knowledge/ as it give a good foundation on banking domain
@ Abdelkrim
Nothing specific to banks , that is correct.
The aim of the article is to give an Overview of how testing for Financial Apps is carried out and what is followed diffrently then a Generic Applicaiton.
However , diffrent Projects may follow diffrent Approaches.
its very nice and useful information to whose doing testing and who will be done testing job. it is all purpose .
i am unable to find scenarious from functional specification document is there any methods to identify scenarious from functional specification document
It is really very web site for information gathering & acquire & great job.
Really Nice article.
Can any one tellme
how to create or get the logs?
what is cache memory?
In security testing means only authetication or others also?
while doing testing I executed application in different platforms like window 2003 and AIX .
why we do that and even what is the difference between them?
very informative article to know about various types of testing. Excellent information
Great Article. Need some improvements.
Can anyone send me Banking domain Project Detail and
easy understandable with sample documents on my email.my email is alpesh667@gmail.com
Thanks
Hi Team
Please help me How to test NEFT and RTGS . Please proved step by step instruction.Also which is the best site for prepare the banking application in software testing
Hellosss Guyzz,
Those have experience in banking domain, could you please solve few interview questions for me.
1. List Security Testing Scenarios and How to test using open source tools?
(I already know that there should be padlock,https:// and disable back/refresh button)
2. Database Testing Scenarios and list queries that a tester executes?
Thanks a lot
Nandini
@sdf
dndsjgvdifuvjdf
I would be happy if somebody could help me with this query.
Please send me how to write the testcases in retailbanking application domain
Good stuff for begineers and very useful for me
Banks and FinTech firms today have geared up to implement effective digital strategies to enhance the overall banking experience. However, the financial services industry juggles multiple priorities within its technology function. What they need is Automation and:
1. Speed of change
2. Complexity of environment
3. Frequency of change/ deployment
4. Digital transformation
In 2019 Why QA Automation Matters: With most financial organizations moving towards continuous delivery and agile based development models, the frequency of testing increases.
Hi ,
I have worked in 2 projects for banking and this article is really helpful in briefing the testing in financial systems. It very simple and easily explained … Really appreciate it 🙂
good article.its very helpful!!!
I am in the teaching field for the last 20 years teaching IT in schools. I have a fair knowledge in SQL and java. Recently underwent training in QTP and QC. I would like to shift(transition) to System testing or Coporate learning. Can anyone pl guide me as to how to build my career toward this goal?
Hi,
I am working in energy domain for the past 7 years. I want to switch my career in other Domains like Banking, Healthcare.
Please give me a suggestion how to change??
can you please send banking related qtp scripts, manual testing projects for writing test cases, scenarios,
my mail -Id-test4rhsoftware@gmail.com
I am looking for help on how to get some test data for checking, savings, customer, loan and credit card accounts. Any pointers on how to get this data so that I can build my test bed will be helpful. I am in nascent stage of building a product. Srinivas_vadali@yahoo.com
HAI…its very nice article and i hope that it wil be very helpful for freshers/others….
THANQ………..
this is very good article and very useful. send some scenarios related to banking application.
nice article and is very helpfull for the new comers in banking secter for testng.
Nice article .Thank u so much,
Can u tell me hw integration testing is done (practically)for banking application
It’s a very nice article on banking application. Its helpful to the every readers/people belongs to same domain and different domain people who are wants to change the domain.
This article is really nice….
Hi,
Nice one. One quick query. Why Security testing comes before UAT? why not after UAT testing?
Kumar
Hi ,
Currently am residing in US.I don’t have any experience in IT field.I went through some desi consultancy and they put fake experience in my resume and marketed my resume that i had 6 yrs experience working in financial domain.I have undergone a 3 months software testing course in US.But i don’t have real time experience.Is it hard for me to work in financial domain without prior experience?pls help me friends…
Hi Gayathri.
Do you still need help or now you are able to manage on your own?
First of all the consultants should not have mentioned 6 years of work exp because in market for this much of exp companies expect you to be an expertise of the domain,rather they judge you on your Team Lead skill as well by now.
What now you may do is, study about software testing basics through Online tutorials, youtube has got a lot many knowledgeble sessions. And it is not a one day task,the basics need to be clear, start practiising online only.
Once you are through with the basics your next step should be studying about the domain knowledge.
Because frankly when the interviewer interviews you for a 6year+ vacancies they are hardly intereted in knowing your basics rather they just want to know about how you handled your last finanicial projects and ask about their workflow rule.
Hope this gives you a rough idea about how you can manage your situation.
If you need more help knowing what sessions you should start studying,i can help you out with that.
Good Luck :}
hey Stuti,
I have the same issue. I have studied for SDET in online course for 6 months, and I got the offer from the company that works with credit cards. I need some job support. Because I don’t have any experience with banking domain. Please can you email me to
Hi Stuti,
I have the same issue. I have studied for SDET in online course for 6 months, and I got the offer from the company that works with credit cards. I need some job support. Because I don’t have any experience with banking domain. Please can you email me to showmshaman@gmail.com.
Hi … I have 1.2 years of experience but I tried so many companies but im not selected in last round can u plz share me how can I study and what I exactly do … actually i don’t get my prob …
Please can you tell me more about Wed Service? Thanks, My Email is bakpotohor@yahoo.com
I am 2+ testing professional, i am looking for job change, can anyone please help in this regrad, my phone numbers: 09035532329
Really very very informative…..it’s really helpful to the guys who are new to the banking domain…..Good Article
Hi Vishal
There is an Article on DB Testing on this Forum …please read that for more details.
Pls send any projects on Testing to my id
lovelysindhu143@gmail.com
how to write a test cases for leave application form
Good article.
Informative………
Hi, thanks.
I have a question. Is there a application that do automation functional testing?
Hi,
I am working in energy domain for the past 7 years. I want to switch my career in other Domains like Banking, Healthcare.
Please give me a suggestion how to change??
sir i need some sample resume for the experience of 2.3 years also i want the project description for online banking as a test engineer
This process resembles waterfall model. Though arrows are not specified. Truth of reality is that all stages are Agile and TDD. I feel platform testing (Linux,windows,Symbian etc.) is also part of whole process. Profit to risk ratio is also calculated.
very informative..thanks
what is Database testing? and how to make in MS-access ?
Security testing is the crucial part in testing any banking application. The tools u mentioned are really helpful and I know are used in many high end banking application testing.
Nice article.
I am 4+ yrs of experienced testing professional,looking for a job at Bangalore it self?Can anybody help me to get the same?
@gayathri,
Hi!!
You will face the following issues.
1) You will be considered as a 6 year experienced and the level of questions asked in the interview will be too high..Three month of course will give you just an overview of basic testing concepts..The actual testing process is way too different.
2) In case you crack the interview and get a job you will not be given any kind of training.The expectations will be too high…and it will be difficult to meet those expectations.
What i suggest is don’t show 6 years of experience. Make it to max 2 or 1.8.It will be pretty easy for you to face the interview…You might get less package in the beginning but surely this will give you an opportunity to gain knowledge..
Thanks!!!
Hi,Thank u.It is very useful.
Could u please tell me how to start the scenarios,cases,logs etc,,,
hi team,
if assume banking application we are transfers the amount
the process is
1.login with user details
2. funds transfer next
3.already added account select
4. amount
5.text box
6.check the accept the terms and condition
7.enter the password
8.submit
this is the flow of application in this case what is the end to end testing and also backend what will happen pls tell me
1) What are the documents Used and produced in requirements gathering,review and business scenario preperation phases?
Requirement gathering may use Tickets/Service Requests/Change Requests generated by Internal and External Customers as Input and Output of Requirement Gathering are Specs , Use Cases and Mock Screens
2)Are functional specifications derived from business scenario? or Are Business scanarios derived from Functional spec?
Its other way round Business Scenarios derived from Functional Specs and is done by QA Engineer , Domain knowledge most important skill needed in Business Scenario Prep.
please reply access to test cases for mobile banking applications user acceptance and design elements testing.hkb.harekrishna.bag@gmail.com
Hi Team,
I am working in energy domain for the past 3 years. may i know test cases of operational issue after ATM switch magaration. Kindly provide me Test cases of ATM operational issue or its solution
Can any one describe end to end testing in banking application
Quicken Error CC-503 usually occurs when you try to update your banking account. It happens if you are using an older version of Quicken you can update this you can visit our website if you having any issue our technical assistance guide you the complete information.quicken-error-cc-503