Test Analysis for a Banking application

Why test banking applications?

Data safety and security of the customers

Since banking apps handle sensitive customer data and financial facts, like account details and transactions, when an unauthorized user gets access to these data it may result in identification theft, fraud or harm to the bank itself.

Making sure the app runs smoothly

A lot of banking apps tend to focus a lot on the security aspects and often forget about the user experience resulting in a sluggish, slow and a bad UI. User experience and security must go hand in hand for maximum growth of the company.

It is essential for the application to handle major loads as there are going to be hundreds and thousands of people logging in, checking their balance, making transactions etc.

Staying ahead of the vulnerabilities

Since the application is the front of the bank, it is essential for it to hold up the best standard possible when it comes to quality and making sure there are absolutely no vulnerabilities that malicious people can exploit.

Test Cases

  • Testing account management

  1. A complete sign up from start to finish

  2. If key details are missing, the joining process has to fail

  3. After transaction, account balances should reflect accordingly

  4. Closing an account should remove all employee info (according to their terms and conditions of the bank).

  5. Account names should follow the set policies.

  6. The ability to link or unlink joint accounts.

  7. Recovering forgotten credentials must be possible.

  8. The account must lock quickly after a certain set failed attempts.

  • Transaction

  1. Transactions like deposits, withdrawals, transfers need to be tested.

  2. Transactions should be processed in real-time or within described time frames.

  3. Transaction costs are appropriately deducted.

  4. Capability to cancel or reverse the pending transaction.

  5. Transaction receipts should be generated correctly.

  6. Duplicate transaction detection and prevention.

  7. Mapping of correct transaction ID with its metadata should be verified

  • Safe user auth and security

  1. Successful login with accurate credentials

  2. Expected error messages on wrong credentials.

  3. Expected lock after a set of incorrect attempts.

  4. Password reset capabilities.

  5. Changing pins and verifying it has been changed.

  • Mobile Banking

  1. Installation and security checks of the mobile itself - like developer options is enabled or not.

  2. Compatibility across multiple phone types.

  3. Confirm push notifications and alerts are sent correctly.

  4. Sync with net banking.

  5. Ensure it is smooth to use with people with disabilities as well.

  6. Check app performance and appropriate errors when using with WiFi, cellular data.

GDPR

General Data Protection Regulation (GDPR) is a law made by the European Union that governs how personally identifiable information is collected, processed and eventually deleted from a computer system.

Personal data identified by GDPR are,

  • Basic identity info like Name, Address, and ID numbers.

  • Health and genetic data.

  • Biometric data.

  • Racial data.

  • Political Opinion.

References

https://www.geeksforgeeks.org/test-cases-for-banking-application/

https://www.geeksforgeeks.org/general-data-protection-regulation-gdpr-considerations/

Updated on
Payment Gateway
Introduction to Selenium