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

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

It is therefore difficult to generalize the flow for all banks. So I'm trying to come up with a flow that most banks are likely to have in their 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?

In online banking, they prevent customers and organizations from using an electronic method to transfer money through a web application. Now in the 21st century, most people use this transfer method because it's faster and you don't have to stand in line for a long time for 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 dealing with any banking app, both developers and testers ensure that the app runs smoothly across all browsers and devices. The web application also secures all cyber threats and performance does not suffer during peak hours.

Testing of banking applications

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

• Function test:All modules work as expected (both standalone and when all separate modules are integrated)
• usability test:In most cases, those who use banking applications are not proficient PC users. Therefore, the form for them must be transparent and have a user-friendly interface.
• performance test:Since this is developed for users, the performance of the app should be faster. And the app should work fine across platforms.
• Safety test:Just like using a banking app, people will use it for money transfers. 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 review the natural flow of a banking app with some basic scenarios:

Test steps for bank transactions

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

• Go to the login page of 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 details and person. Check that they are correct.
• Select a specific fund transfer method from the NEFT/RTGS or SWIFT transfer options.
• Select the recipient's name and funds, then submit the information.
• Check the amount and other details on the confirmation page.
• Click Send to complete the final action of transferring funds.

Whatever steps you see above is the basic flow we cover here. Or maybe if you go to a different region it could be something other than the above scenario.

For example, some of you may have SMS verification before sending money. Some of you may have other ways to verify recipient 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 that different banks follow, maybe when you need to add a beneficiary, whatever fields you see in the image below, probably varies from bank to bank. So the figure below shows the number of fields that can also be verified and write test cases.

If you add test cases for each page, then there will be a lot of test cases covering the basic aspects of testing.

Test scenarios for the remittance banking application

• Verify the bank's websiteURL.
• Verify that your bank's website URL contains HTTPS in the address bar and in the URL.
• Check that the login page for the bank's website does not look fake.
• Check that the bank's login page contains your username and password.
• Check whether username and password are accepted or not.
• Check if SMS authorization is triggered after login.
• Confirm that the user is redirected to the dashboard after all authentication processes are completed.
• Verify that the user has access to the online money transfer feature.
• Check if the user can transfer money during the selected period (9:00 a.m. to 5:00 p.m.).
• Check that the money transfer option includes an out-of-hours transaction notification.
• Verify that the user can add a recipient.
• Check if the recipient's information can be verified.
• Check if the remittance option allows NEFT or RTGS option for nationalized remittances.
• Check that the money transfer page asks for the name of the recipient, IFSC code, bank name, amount of money and the purpose of the transfer.
• Check that the money transfer page asks for your PAN number if your money exceeds 50,000.
• Before completing your transfer, check that the money transfer site has two-factor authentication.
• Check if the interbank transfer is instant or not.
• Check how long it takes to transfer money between business hours.
• Check how long it takes to transfer money between non-working hours.
• Check that notification of the transferred amount is sent to sender and recipient.
• Confirm that the amount will be transferred to the exact person mentioned in the recipient.

In addition to this flow, there are several other scenarios; we too are now added to this post. Hopefully this also gives you an idea of ​​how to write a test case for a banking app.

Test cases for the banking application - Internet banking application

• Verify that the user can log in with the correct username and password
• Verify that the user is able to perform basic financial transactions
• Verify that the user can add a recipient with the correct name and account information
• Check if the user can make financial transactions with the added recipient
• Check if the user can add a decimal number to the amount (limited to 2 digits)
• Verify that the user cannot add a negative number to the amount field.
• Check that the user can only transfer money if the account balance is correct.
• Check if there is a confirmation of financial transactions
• The check user receives a confirmation after a successful financial transaction.
• Check whether the customer can send money to several people
• Verify that the user can change the password
• Check account information that also reflects financial transactions.
• Confirm that a user with an incorrect password cannot log in.
• Check after multiple attempts to log in with the wrong password (according to the limits), the user should be blocked.
• Implemented timeout control function
• Please check if the username or password is empty, the user cannot log in. The user must also receive a warning.

Manual Test Cases for Banking Applications - Admin

• Verify that the administrator can sign in with valid credentials and cannot sign in with invalid credentials.
• Verify that the administrator can log in without valid test data.
• Check all application links for the administrator role.
• Check that the administrator can change the password with the correct data and should not allow the change with incorrect data.
• Check that recently used test data should not allow reuse.
• Check whether the administrator can login or not.

Test cases of bank applications - new branch

• Check: With the correct details you can create a new branch.
• Check with invalid data. You cannot add a branch.
• Check to try to create a new branch with existing test data.
• Verify that the Reset, Cancel, and Submit buttons work as expected.
• Try to update the department information with valid and invalid test data.
• Try updating the branch details with test data.
• Update branch details with existing branch test data
• Check if the cancel button is working or not.
• Verify that branch deletion is allowed with and without dependencies.
• Confirm that the user must be able to search for and locate a branch.

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

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

• Check whether you can create a new role with valid details or not.
• See if you can create test data without test data.
• Validate the new role against existing test data
• Check the role description and role types.
• Verify that the Cancel and Submit button works as expected.
• See if you can remove the role without dependencies.
• Verify that all new role links work as expected.

If you want to add a few more points, 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 guests

• Verify that all links to the client and guest modules work as expected.
• Verify that all customers can log in with valid credentials.
• Verify that the client cannot log in with an invalid date.
• Check by the number of failed attempts to access the account; then the user account must be locked that day or not.

Test cases for banking applications - Adding new users

• Check if you can add a new user with valid details.
• Confirm that the correct confirmation messages are displayed by entering incorrect data.
• Confirm that the correct branch information should be displayed after adding a user.
• Verify that all links work as expected.
• Check that all buttons work as expected.
• Confirm that validation messages are displayed when invalid data is entered while updating user data.
• Check the warning message after clicking the submit button without changing any details during the update.
• Check to remove the user feature if it works as expected.

Test cases for banking applications PDF - New account

• Check all required fields and their associated confirmation messages.
• Check all optional fields and their associated confirmation 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 your account, check whether the updated balance is displayed or not.
• Check whether the user can withdraw the amount or not.
• After withdrawing the amount, check if the balance is updated or not.
• Check all the entered data displayed in the user profile section.
• Check if a primary account is available if it is a secondary account.
• Check if business details are listed or not if it is a current account.
• Check whether proof is provided or not if it is a joint account.
• Check whether the zero account is on the salary account.
• See if you can maintain zero or less than the minimum balance in your non-salary account.

Test cases for the field Bank account number

Follow the steps below to test the bank account number field.

Bank account number: SSSSXXNNNNNNNNNN (eg 35010100008033)

• SSSS - The first four digits of your account number are your Service Center 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 – Savings,
02 - Current account
03 – Installment payment
04 – Overdraft
05 – Cash loan
06 - Loan
07 – Credit for packaging
08 - Inland accounts
09 - Foreign accounts
81 - Konta FI pod SB 150

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

Example of test cases for the bank account number field

• Check the billing field by entering a valid invoice number.
• Check the invoicing field by entering an incorrect invoice number.
• Check the account number field by entering an account number of more 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.
• Verify that the billing field allows alphabets and special characters.
• Check the account number field by entering an alphanumeric value.
• Check that the account number field allows blank fields.
• Check if a warning message appears about entering an incorrect account number.
• See if a message appears when a user enters an account number that doesn't exist.
• Verify that the user can enter the account number in the account number field.
• Check it when users enter a closed account number.
• Check this when the user enters an account number with a space.

Application

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

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