Test Cases for Banking Application in Excel Sheet and PDF 2022 (2023) (2023)

Test cases for banking application or test scenarios for 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. And in our previous post we also test Amazon Search Functionality templates. Each bank has its own flow for transferring money.

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

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

What is internet banking?

In Internet banking, problem clients and organizations use an electronic way of transferring money through a web application. Currently, in the 21st century, most people use this method of money transfer because it is faster and does not require long queues to complete a single transaction.

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

But when it comes to any banking app, both the developer and the testers ensure that the app runs smoothly on all browsers and devices. And the web application also secures against all cyber threats and the performance also does not drop during peak hours.

Testing banking applications

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

• Function test:All modules work as expected (both as standalone elements and after integration of all separate modules)
• Usability test:Most of the time, those who use banking applications are not experienced computer users. Therefore, for them, the form must be clear and have a user interface.
• Performance test:Since this is developed for users, the performance of the application should be faster. And the app should work correctly on different platforms.
• Security test:Like using a banking app, people will use it to transfer money. So that is one of the high prioritiestasks for the organization to develop the application in such a way that it meets standard security guidelines.

So in this post we will discuss the natural flow of a banking application with some basic scenarios:

Test steps for bank transactions

So here are the necessary steps we follow while doing any currency transfer:

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

Regardless of the steps you see above, we cover the basic flow here. And maybe if you go to another region, then it can be something other than the above scenario.

For example, some of you may receive SMS approval before sending money. Some of you probably have other ways of verifying the recipient's information to avoid sending money to the wrong person. But having said that, the flow is pretty much the same for most banks.

Another different process followed by different banks, maybe when you need to add a payee, whatever fields you see in the image below, may differ from bank to bank. So the image below shows the number of fields for which you can also validate and write test cases.

If you add test cases for each page, then the test cases will cover a lot of important aspects of the tests.

Test scenarios for money transfer in the banking application

• Check the bank's websiteURL.
• Make sure the bank website URL has HTTPS in the address bar and in the URL.
• Check if the login page on the bank's website is showing as fake.
• Make sure the bank login page has a username and password.
• Check whether the username and password are accepted or not.
• Check if SMS authentication is triggered after login.
• Verify that the user is redirected to the dashboard after passing all authentication processes.
• Check if the user has access to the online money transfer feature.
• Check whether the user can transfer money during a certain period (9:00 a.m. to 5:00 p.m.).
• Check if the money transfer option shows an out-of-hours transaction alert.
• Confirm whether the user can add a recipient.
• Confirm whether the recipient information can be verified.
• Confirm whether the NEFT or RTGS remittance facility allows for nationalized remittances.
• Check if the funds transfer page asks for the recipient's name, IFSC code, bank name, amount of funds and purpose of transfer.
• Confirm if fund transfer page asks for PAN number if fund amount will be more than 50k.
• Make sure the money transfer site has 2-step verification before completing the transfer.
• Check whether the interbank transfer is instant or not.
• Check how long it takes to transfer funds between business hours.
• Check how long it takes to transfer funds between non-business hours.
• Verify that the transferred amount has been sent to the sender and recipient.
• Check whether the amount has been transferred to the exact person specified in the recipient.

Apart from this flow, there are several other scenarios; Also, we are now added to this post. We hope it also gives you a little idea how to write a bank application test case.

Test Cases for Banking Application - Online Banking Application

• Verify that the user can log in with a valid username and password
• Verify that the user is capable of performing basic financial transactions
• Verify that the user can add a recipient with a valid name and account information
• Check if the user can make financial transactions to the added recipient
• Check if the user can add a decimal number to the amount (limited to 2 digits)
• Make sure the user cannot add a negative number to the amount field.
• The user of the check may transfer money only if there is a correct account balance.
• Make sure there is a confirmation check for financial transactions
• The user of the check receives a confirmation of a successful financial transaction.
• Check if the customer can send money to more than one person
• Make sure the user has permission to change the password
• Current account information also reflects financial transactions.
• Make sure that a user with an invalid password is not allowed to log in.
• Check after repeated login attempts with wrong password (according to restrictions), the user should be blocked.
• Check if the timeout feature is implemented
• Check if the username or password is empty, the user is not allowed to login. The user must also have a warning.

Manual Test Cases for Banking Application – Admin

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

Test cases of banking applications - new branch

• Mark You can create a new branch with valid data.
• Check with invalid data. You cannot add a branch.
• Check to try to create a new branch with existing test data.
• Check if Cancel, Cancel and Submit buttons are working as expected or not.
• Try to update the branch data with valid and invalid test data.
• Try updating the branch data with the test data.
• Update the branch data with the existing test branch data
• Check if the cancel button is working or not.
• Make sure file deletion is allowed with and without dependencies.
• Check if the user can search and locate the branch.

Test cases for banking application in Excel spreadsheet - new role

Now let's look at some example test cases for a banking application that adds a new role.

• Check whether you can create a new role with valid 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.
• Check if Cancel and Send is working as expected or not.
• Make sure you can delete the role without dependencies.
• Verify that all connections to the new role work as expected.

If you want to add some more points, please let us know about them. Now we will move on to other test cases of banking applications for customers and visitors.

Test cases for banking application in Excel sheets - customers and visitors

• Verify that all links to the Customer and Visitor modules work as expected.
• Verify that all users can log in with their valid credentials.
• Make sure the customer can't check in with an invalid date.
• Check the number of failed account accesses; then user account must be locked for that day or not.

Test cases for banking application - Adding new users

• Make sure you can add a new user with valid information.
• Verify that the correct confirmation messages are displayed by entering invalid information.
• Check after adding the user the correct branch information should be displayed.
• Verify that all connections work as expected.
• Check that all buttons work as expected.
• Validation messages are displayed when invalid data is entered while updating user data.
• Check the warning message when you click the submit button without changing any details during the update.
• Check to delete the user function works as expected or not.

Test Cases for Banking Application Pdf - New Account

• Check all required fields and their associated validation messages.
• Check all optional fields and their associated validation messages.
• Check after filling all the required fields, click submit and check whether the new user is added or not.
• After depositing the amount in the account, check whether the updated balance is showing 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 entered information displayed in the user profile section.
• Check whether the primary account exists or not if it is a secondary account.
• Check whether the company information is listed or not if it is a checking account.
• Check whether the proof is attached or not if it is a joint account.
• The check zero account is kept in the salary account.
• Make sure you can maintain zero or less than the minimum balance for a non-salary account.

Test cases for the bank account number field

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

Bank account number: SSSSXXNNNNNNNN (eg 35010100008033)

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

The different types of schemes are:

01 – Saving,
02 – Current account
03 – Installment payment
04 – Exceeding
05 – Cash loan
06 – Borrowing
07 - Credit for package
08 – Domestic accounts
09 – Foreign bills of exchange
81 – FI accounts under SB 150

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

Example test cases for bank account number fields

• Check the accounting field by entering a valid account number.
• Check the accounting field by entering an invalid account number.
• Check the account number field by entering an account number that is longer than 14 digits.
• Check the account number field by entering an account number of less than 14 digits.
• Check the account number by inserting 14 zeros.
• Make sure the accounting field allows letters and special characters.
• Verify the account number field by entering an alphanumeric value.
• Make sure the account number field allows a blank value.
• Check whether the warning message is displayed or not by entering an invalid account number.
• Check if a message is displayed when the user enters an account number that does not exist.
• Make sure the user has permission to insert an account number in the account number field.
• Check when users enter a closed account number.
• Check it when the user enters an account number with a space in between.

Conclusion

I hope we can cover a very basic test scenario for a banking application. While going through them in the above scenario, if you find any missing test cases of the banking application, you can mention those scenarios in the comment section.

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