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

Test case for bank application or test scenario for bank application or bank applicationtest case:In this article, we will learn how to write banking application test cases in an Excel spreadsheet. In our previous post, we also covered the test case template for Amazon search functionality. Each bank has its own remittance process.

Therefore, it is difficult to generalize the process of all banks. So I'm trying to develop a process that most banks probably have in their remittance process. Depending on the type of bank you use, you'll find many differences.

However, before you start writing test cases for the banking application, you need to know the following:

What is Internet Banking?

With online banking, customers and organizations use electronic means to transfer funds through web applications. Today, in the 21st century, most people transfer money this way because it's faster and you don't have to wait in long lines for a single transaction.

You can use this method to carry out various business-related remittances, such as B. Collection, payment and many other operations.

But when you're dealing with a banking application, developers and testers make sure that the application runs smoothly across all browsers and devices. In addition, the web application is protected against all cyber threats without performance degradation even during peak work hours.

Banking App Testing

When testing a banking application, QA specialists prioritize several areas:

• function test:All modules work as expected (both as standalone elements and after integrating all individual modules).
• Usability testing:In most cases, people using banking apps are not experienced PC users. So, for them, the form should be clear and have a user-friendly interface.
• Performance Testing:Since this is developed for users, application performance should be faster. And the app should work fine on different platforms.
• Safety test:For example, when you use a banking app, you use it to transfer money. so it has the highest priorityThe task of organizing the development of applications to comply with standard security policies.

In this article, we'll discuss the natural flow of a banking application using some basic scenarios:

Test Steps for Banking Transactions

So, here are the necessary steps that we follow while making money transfers:

• Go to the bank website login page.
• Enter a username and password.
• Go to the funds transfer page.
• Add the recipient you want to transfer money to.
• Check bank details and personal details. Check that they are correct.
• Select a specific money transfer method from NEFT/RTGS or SWIFT transfer options.
• Select a beneficiary name and funds, then submit details.
• Review the amount and other details on the verification page.
• Click "Send" to complete the final transfer process.

Whatever steps you see above, that's the basic flow we'll cover here. This may differ from the above if you are traveling to a different region.

For example, some of you may have SMS authentication before sending money. Some of you may have other ways to verify recipient details to avoid sending money to the wrong person. However, the process is pretty much the same for most banks.

Another different process that different banks may use is adding beneficiaries. The fields you now see in the image below may vary from bank to bank. So the image below shows how many fields you can also validate and write test cases for.

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

Money Transfer Test Scenario in a Banking Application

• Check the bank's websiteurl.
• Check the bank website URL address bar and whether HTTPS is included in the URL.
• Check the login page of the bank's website for deception.
• Check the bank's login page for a username and password.
• Check that the username and password are accepted.
• Check whether SMS authentication is triggered after login.
• Verify that the user is redirected to the dashboard after passing all authentication processes.
• Confirm that the user has access to the online money transfer function.
• Checks if the Send Money option is available to the user during the specified time period (9:00 AM to 5:00 PM).
• Check the money transfer options for notifications of after-hours transactions.
• Checks if user can add beneficiaries.
• Check if beneficiary details can be verified.
• Check if the remittance option allows NEFT or RTGS options for nationalized remittances.
• Check the transfer page for beneficiary name, IFSC code, bank name, amount and purpose of transfer.
• If the amount of funds is more than 50,000, please check the transfer page to see if a PAN number is required.
• Please check whether there is two-step verification on the transfer page before completing the transfer.
• Check that transfers between banks are instant.
• Check how long it takes to transfer money between business hours.
• Check how long it takes to send funds outside of business hours.
• Check whether a notification of the transfer amount is sent to both the sender and receiver.
• Check that the amount was transferred exactly to the person named on the beneficiary list.

There are a few other scenarios besides this flow; moreover, we've now added to this post. I hope this also gave you an idea of ​​how to write test cases for a banking application.

Banking Application Test Case - Online Banking Application

• Verify that a user can log in with a valid username and password
• Verify that the user is able to perform basic financial transactions
• Verify that a user can add a beneficiary with a valid name and account details
• Check users can make financial transactions with added beneficiaries
• Checks if user can add decimal point to amount (limited to 2 digits).
• Verify that users cannot paste negative numbers in amount fields.
• Checking users can only transfer funds if there is an appropriate balance in the account.
• Confirmation check to check if there is a financial transaction
• Check users receive confirmation of receipt if the financial transaction is successful.
• Check customers can send money to multiple people
• Check if user is allowed to change password
• Checking account details also reflect financial transactions.
• Checks whether the user is allowed to log in with an invalid password.
• Checks if the user should be locked out (per limit) after repeated login attempts with an incorrect password.
• Check the timeout function implementation
• Checks if username or password is empty. User is not allowed to log in. A warning should also be displayed to the user.

Banking Application Playbook Test Cases - Admin

• Verify that the administrator can log in with valid credentials and cannot log in with an invalid login date.
• Check that admins can log in without valid test data.
• Check all links for admin role applications.
• Check that administrators can change passwords with valid data, changes with invalid data should not be allowed.
• Make sure that the most recently used test data cannot be reused.
• Check whether the administrator can log in successfully.

Banking Application Test Case - New Branch

• Check if a new branch can be created with valid data.
• Check for invalid data. You cannot add branches.
• Check this option to attempt to create a new branch with existing test data.
• Check that the reset, cancel and submit buttons work as expected.
• Attempt to update branch details with valid and invalid test data.
• Try updating store details with test data.
• Update branch details with existing branch test data
• Check if the cancel button works.
• Checks whether it is allowed to delete branches with and without dependencies.
• Checks if users should be able to search and find branches.

Banking Application Test Cases in Excel Spreadsheet - New Role

Let's now look at some sample test cases for a banking application with a new role added.

• Check if new roles can be created with valid data.
• Check if it is possible to create test data without test data.
• Validate new roles against existing test data
• Check the role description and role type.
• Verify that cancel and commit work as expected.
• Checks if a role without dependencies can be dropped.
• Verify that all links for the new role work as expected.

If you have a few more points to add, please let us know. We will now move to other test cases for the customer and visitor banking application.

Test Cases for Banking Application in Excel Spreadsheet - Customers and Visitors

• Verify that all links from the Customers and Visitors modules work as expected.
• Check that all clients can log in with their valid credentials.
• Check if the client cannot log in with an invalid date.
• Check the number of unsuccessful account accesses; then the user account should be blocked or not blocked for that day.

Banking Application Test Case - Adding a New User

• Check if you can add a new user with valid data.
• Check for validation messages when invalid data is entered.
• After adding the user verify that the correct branch details are displayed.
• Verify that all links are working as expected.
• Verify that all buttons work as expected.
• Check validation message appears when invalid data is entered while updating user details.
• Check for the warning message when you click the submit button during the update without changing any details.
• Check that the delete user functionality works as expected.

Bank Application PDF Test Case - New Account

• Check all required fields and corresponding validation messages.
• Review all optional fields and corresponding validation messages.
• Check after filling all the required fields, click submit and check if the new user is added.
• After depositing the amount into the account, check to see if the updated balance is displayed.
• Check if the user can withdraw the amount.
• After withdrawing the amount, check to see if the balance is updated.
• Review all input details displayed in the User Profile section.
• If it is a secondary account, check whether there is a primary account.
• If it is a checking account, please check that company details are provided.
• If it's a joint account, check to see if proof is provided.
• Zero checking accounts are kept in payroll accounts.
• See if you can keep your non-salary account minimum balance at zero or less.

A test case for the bank account number field.

To test the bank account number field, just 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 plan type (01-09).

The different scheme types are:

01 – Savings,
02 – Checking Account
03 – Term Deposit
04 – Overdraft
05 – Bar Qualification
06 - Loans
07 – Package Credit
08 – Inland Notes
09 – Foreign Invoice
81 – FI account under SB 150

NNNNNNNN – The remaining -8 bits represent the serial number.

Example test case for the bank account number field.

• 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 longer than 14 digits.
• Check the account number field by entering an account number with fewer than 14 digits.
• Verify the account number by inserting 14 zeros.
• Check that the accounting field allows letters and special characters.
• Validate the account number field by entering an alphanumeric value.
• Validates that the account number field accepts null values.
• Check for warning messages by entering an invalid account number.
• Validates whether to display a message when the user enters an account that does not exist.
• Validates that the user is allowed to paste an account number into the account number field.
• Check this when the user enters a closed account.
• Check this when the user enters account numbers with spaces between them.

diploma

I hope we have covered basic testing scenarios for a banking application. If while going through the above scenarios you find banking application test cases missing, you can mention these scenarios in the comment section.

If you have any contribution to Softwaretestingo.com about banking apps or any other topic or tool, you can write to ussoftwaretestingo.com@gmail.com。