How to Test Banking Financial Applications Software Testing Help. Banking applications are one of the most complex applications in todays software development and testing industry. Edgeverve develops innovate cloud based software applications on enterprise solutions, core banking, financial services, customer service and distributive trade. In this article, Lets Talk Payments contains a list of 18 banking software providers powering online banking. EXCLUSIVE Santanders corporate banking business in the UK is embarking on a core banking software overhaul, Banking Technology understands. The bank has a. The focus of PGDB program is to craft proficient entrylevel banking professionals who are trained on banking domain, have knowledge of application software Finacle. The Shirpur peoples coop bank ltd is a cooperate bank, We proud to say that we are the only urban cooperative bank, which uses finacle software of world known. General Banking and Credit Management of AB Bank Ltd. Introduction A bank is an establishment which makes to individuals such advantage of money as may. What makes Banking application so complex What approach should be followed to test the complex workflows involved in banking applications In this article, we will be highlighting different stages and techniques involved in testing Banking applications. The characteristics of a Banking application are as follows 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. Finacle Banking Software' title='Finacle Banking Software' />Complex Business workflows. Real Time and Batch processing. High rate of Transactions per seconds. Secure Transactions. UKbased source of technology and financial systems news for the banking industry. Garena Plus Themes. An Oracle White Paper September 2013 Infosys Finacle Core Banking Solution on Oracle SuperCluster and Oracles SPARC TSeries Servers. Edgeverve Finacle is a leading universal digital banking application built to deliver better online banking, payments, treasury solutions to banks across 94 countries. Finacle Banking Software' title='Finacle Banking Software' />Robust Reporting section to keep track of day to day transactions. Strong Auditing to troubleshoot customer issues. Massive storage system. Disaster Recovery Management. The above listed ten points 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 web server. Data Base 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. If 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. Functional aspect of the application. Security aspect of the application. Data Integrity. Concurrency. User Experience. Typical stages involved in testing Banking Applications are shown in below workflow. We will be discussing each stage individually. 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 Analyst. Experts are involved in writing requirements on more than one subject as banking itself has multiple subdomains and one full fledge 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. 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 existing business workflows nor new workflows are violated. All the requirements are verified and validated. Follow up actions and requirement document revisions are done based on the same. 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 all of the 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 can have different business scenarios related to net banking account creation, online deposits, online transfers, etc. In this stage, functional testing is performed and the usual software testing activities are performed such as Test Case Preparation In this stage Test Cases are derived from Business Scenarios, one Business Scenario leads to several positive test cases 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 involving tools like QC, QTP or any other. The functional testing of a banking application is quite different from the ordinary software testing. Since these applications operate with customers 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 banking domain. Banking Application involves complex transaction which is performed both at UI level and Database level, Therefore, Database testing is as important as functional testing. The database is complicated 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 Data types. Rules Testing. Testing Stored Procedures and Functions. Testing Triggers. Data Integrity. Security Testing is usually the last stage in the testing cycle. A prerequisite to commencing security testing is the completion of functional and non functional testing. Security testing is one of the major stages in the entire Application testing cycle as this stage ensures that 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 makes sure that the application does not have any such web vulnerability that can expose sensitive data to an intruder or an attacker. It also assures that the application complies with standards like OWASP. In this stage, the major task is the whole application scan which is carried out using tools like IBM App. Scan or HP Web. Inspect 2 Most popular tools. Once the Scan is completed, the Scan Report is published. Over this report, False Positives are filtered out and rest of the vulnerabilities are reported to Development team so that they start fixing the issues depending on the severity of each issue. Penetration testing is also done at this step to reveal propagation of errors. Rigorous security testing should be done across platforms, networks, and OS. Some Other Manual tools for Security Testing used are Paros Proxy, Http Watch, Burp Suite, Fortify tools Etc. Apart from the above main stages, there might be different stages involved in Integration Testing, Usability testing, User acceptance testing and Performance Testing. Let us talk in brief about these stages as well Integration testing. As you know that in a banking application, there might be several different modules like transfers, bill payments, deposits, etc. And 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 to a wide variety of customers. Getty Images License Compliance Team there. Some of these customers might lack the skills and awareness required to perform the 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 easy to use interface is, the higher number of customers will be benefitted from the banking application. Performance Testing. Certain periods of time like payday, end of financial year, festive seasons might bring in change or spike in the usual traffic on the app. Hence, a thorough performance testing should be done so that customers dont get affected by performance failures. A significant example from the past where bank customers got personally affected due to performance failures is Nat. West and RBS cyber Monday IT outage in which the customers had their debit and credit card got declined transactions across shops in the country. User Acceptance Testing.