Bank Application Test Cases in Excel and PDF 2022 (2023) (2023)

Test cases for a banking application or test scenarios for a banking application or banking applicationTest case:In this post, we will learn how to write test cases for a banking application in an Excel spreadsheet. In our previous post, we also presented test case templates for the Amazon search functionality. Each bank has its own money transfer flow.

Therefore, it is difficult to generalize the flow for all banks. So I'm trying to figure out the flow most banks are likely to have in the money transfer process. You can find many differences depending on the type of bank you use.

But before you start writing test cases for banking applications, you need to understand the following:

What is online banking?

Online banking is hampered by the electronic method of transferring money through a web application. Now, in the 21st century, most people use this method of transferring money because it's faster and you don't have to wait in a long line to make a single transaction.

Using this method, you can perform various money transfers related to operations such as receiving money, paying bills and many other operations.

But when you are dealing with any banking app, both developer and testers ensure that the app runs smoothly across all browsers and devices. The web application also protects against any cyber threats, and performance does not suffer during peak hours.

Banking application testing

There are several aspects that QA experts prioritize when testing any banking application:

• Functional tests:All modules work as expected (both standalone and when all separate modules are integrated)
• usability test:In most cases, people using banking applications are not experienced computer users. Therefore, for them, the form should be transparent and have a user interface.
• performance test:Since this is developed for users, app performance should be faster. And the app should work fine across platforms.
• Safety Tests:Just like they use a banking app, people will use it to transfer money. So this is one of the prioritiestasks for the organization to develop the application in such a way that it meets standard security guidelines.

Therefore, in this post, we will go over the natural flow of a banking app with some basic scenarios:

Test steps for banking transactions

Here are the necessary steps we follow when performing any currency transfer operation:

• Go to the login page on the bank's website.
• Enter your username and password.
• Go to the transfer page.
• Add the recipient you want to transfer money to.
• Check your bank account and personal details. Make sure they are correct.
• Select a specific transfer method from the NEFT/RTGS or SWIFT transfer options.
• Select the recipient's name and funds, then send the details.
• Check the amount and other details on the confirmation page.
• Click Submit to complete the final action of transferring funds.

Regardless of the steps you see above, this is the basic flow we cover here. Or maybe if you go to a different region it might be something different than the above scenario.

For example, some of you may have SMS authentication before sending money. Some of you probably have other ways to verify user information to avoid sending money to the wrong person. But that said, the flow is pretty much the same for most banks.

Another different process that different banks go through, maybe when you add a user, regardless of the fields you see in the image below now, they may vary from bank to bank. The image below shows the number of fields that can be verified and test cases written for them.

If you add test cases for each page, the test cases cover the basic aspects of the tests.

Test scenarios for the Money Transfer banking application

• Check on the bank's websiteURL.
• Make sure your bank's website URL includes HTTPS in the address bar and in the URL.
• Make sure the login page on your bank's website doesn't look fake.
• Make sure your bank login page includes your username and password.
• Check whether the username and password are accepted or not.
• Verify that SMS authentication is triggered after login.
• Verify that the user is redirected to the dashboard after all authentication processes have gone through.
• Check that the user has access to the online transfer function.
• Check if the user can transfer funds, the option is available at a certain time (from 9:00 to 17:00).
• Check that the funds transfer option shows an out-of-hours transaction notification.
• Verify that the user can add a user.
• Check if the user's data can be verified.
• Check if the funds transfer option allows NEFT or RTGS option for nationalized money transfers.
• Check if the transfer page requires the recipient's name, IFSC code, bank name, amount of funds and purpose of the transfer.
• Check if the funds transfer page asks for a PAN number if the amount of funds is over 50,000.
• Before completing the transfer, make sure that the funds transfer site has two-factor authentication.
• Check whether the interbank funds transfer is happening now or not.
• Check how long it takes to transfer funds between business hours.
• Check how long it takes to transfer funds outside of business hours.
• Verify that notification of the transferred amount has been sent to the sender and recipient.
• Check that the amount has been transferred to the exact person indicated in the user.

In addition to this flow, there are several other scenarios; In addition, we are now added to this post. Hopefully this will also give you an idea of ​​how to write test cases for banking applications.

Banking Application Test Cases - Online Banking Application

• Verify that the user can log in with the correct username and password
• The check user can perform basic financial transactions
• Verify that the user can add a recipient with the correct name and account information
• The check user can make financial transactions according to the added user
• Check if the user can add a decimal number to the amount (limited to 2 digits)
• The reviewer cannot add a negative number to the amount field.
• The beneficiary of the check can only transfer money if there is an orderly balance on the account.
• Make sure that there is a confirmation of financial transactions
• The check user receives an acknowledgment of receipt after a successful financial transaction.
• Check if the user can send money to multiple people
• Verify that the user has permission to change the password
• Checking account information also reflects financial transactions.
• Verify that a user with an incorrect password cannot log in.
• Check after multiple attempts to log in with the wrong password (according to the restrictions), the user should be locked out.
• Make sure the timeout feature is implemented
• Please check if username or password is blank, user can't login. The user should also receive a warning.

Manual test cases for banking applications - Admin

• Verify that the administrator can log in with valid credentials and cannot log in with invalid credential date.
• Verify that the administrator can log in without valid test data.
• Check all application links for the administrator role.
• Make sure that the administrator can change the password with the correct information and should not allow the password to be changed with incorrect information.
• Check that recently used test data does not allow for reuse.
• Check whether the administrator can login successfully or not.

Banking App Test Cases - New Branch

• Check: You can create a new branch with the correct details.
• Check with invalid data. You cannot add a branch.
• Check to try to create a new branch with existing test data.
• Verify that the undo, cancel, and submit button works as expected.
• Try updating the ward details with valid and invalid test data.
• Try updating the branch data with test data.
• Update branch data with existing test branch data
• Check whether the cancel button is working or not.
• Make sure deleting branches with and without dependencies is allowed.
• Verify that the user should be able to search and locate a branch.

Test cases for banking applications in an Excel spreadsheet - a new role

Now let's look at sample test cases for the Bank app that adds a new role.

• Check whether you can create a new role with the correct information or not.
• See if you can create test data without test data.
• Validate the new role with existing test data
• Check the role description and role types.
• Verify that Cancel and Send works as expected.
• Make sure you can remove the role without dependencies.
• Verify that all connections to the new role work as expected.

If you want to add more points, please let us know. Now we will move on to other test cases for customer and visitor banking apps.

Test cases for banking applications in an Excel spreadsheet - customers and visitors

• Verify that all links in the Customers and Visitors modules work as expected.
• Verify that all users can sign in with their valid credentials.
• Check that the Customer cannot register with an invalid date.
• Check by the number of failed accesses to the account; then user account should be locked for that day or not.

Test cases for the banking application - adding new users

• Make sure you can add a new user with the correct information.
• Verify that the correct confirmation messages are displayed by entering incorrect information.
• Verify that the correct branch information should be displayed after adding a user.
• Verify that all connections work as expected.
• Verify that all buttons work as expected.
• Verification messages are displayed when incorrect data is entered during user data update.
• Check the warning message after clicking the submit button without changing any details during the update.
• Verify that the user function works as expected.

PDF Banking Application Test Cases - New Account

• Check all required fields and corresponding confirmation messages.
• Check all optional fields and their corresponding verification messages.
• Check after filling in all the required fields, click submit and check whether the new user has been added or not.
• Please check after depositing the amount to your account whether the updated balance is displayed or not.
• Check whether the user can withdraw the amount or not.
• After withdrawing the amount, check whether the balance is updated or not.
• Check all the entered information that appears in the user's profile section.
• Check whether the primary account exists or not if it is a secondary account.
• Check if company details are listed or not if it is a checking account.
• Check whether the proof is attached or not if it is a joint account.
• The zero control account is kept in the payroll account.
• Make sure you can maintain zero or less than the minimum unpaid account balance.

Test cases for the bank account number field

To test the bank account number field, follow the steps below.

Bank account number: SSSSXXNNNNNNNNNN (e.g. 35010100008033)

• SSSS - The first four digits of the account number are the POS ID [SOL ID]
• XX-The fifth and sixth digits of your account number indicate the type of scheme (01-09).

The different types of schemes are:

01 – Saving,
02 - Current account
03 – Term deposit
04 – Overrun
05 - cash loan
06 - Loans
07 – Credit for packaging
08 - Internal accounts
09 - Foreign bills
81 - Konta FI pod SB 150

NNNNNNNN - The remaining digits -8- indicate the current serial number.

Examples of test cases for the Bank account number field

• Check the billing field by entering a valid bill number.
• Check the billing field by entering an incorrect bill number.
• Check the account number field by entering an account number longer than 14 digits.
• Check the account number field by entering an account number shorter than 14 digits.
• Check the account number by inserting 14 zeros.
• Make sure the billing field allows letters and special characters.
• Check the account number field by entering an alphanumeric value.
• Make sure the account number field allows blanks.
• Check if any warning message is displayed by entering an incorrect account number.
• Check if a message appears when a user enters an account number that does not exist.
• Make sure that the user can paste the account number in the account number field.
• Check when users enter any closed account number.
• Make sure that when a user enters an account number, there should be a space between them.

Application

Hopefully we can cover a very basic test scenario for a banking app. Going through the ones in the scenario above, if you find any missing banking app test cases, feel free to mention these scenarios in the comments section.

If you want to contribute something to Softwaretestingo.com related to banking apps or other topics or tools, you can write to us atsoftwaretestingo.com@gmail.com.