QA for Mobile Banking: Security is not all you have to handle

by Emma Dallas | February 20, 2019 10:06 am

How do you test the login process to your mobile banking application? You may think that clients can only enter a valid or invalid PIN code and that’s it. And it is far from reality.

There are about 15 different scenarios of logging into m-banking application: entering invalid PIN code 5 times, using the app’s Touch ID function while it is disabled on a device, signing in with no/poor Internet connection, etc. Not to mention Face ID option. Are you sure you’ve checked the most frequent scenarios?

And this is just the log-in process, but what to expect while testing the app’s functionality? Basing on the expertise accumulated by QATestLab[1], an independent QA provider from Ukraine, we have prepared the checklist for m-banking app testing.

5 central points to add to your testing checklist

Testing process in mobile banking resembles preparation for a space flight: too much depends on it. Our QA Engineers outline main constituents of the effective checklist for testing mobile banking apps.M-banking testing checklist

We do judge by appearance. What to check in user profiles?

Mobile testing in banking starts with checking the following functions in customers’ profiles[2]:

It’s all about money. How to test money transfers?

Your clients will be annoyed if they are unable to:

Every penny counts or what to check in tariffing

Tariffs for bank services are constantly updated and you should control all possible scenarios of tariffing. Below are a few of them:

  1. card-phone operation tariffing
  2. service payment operation tariffing
  3. card-card operation tariffing
  4. tariffing of over-limit transfers

Cover all bases – control the blocking scenarios

Checklist[3] for m-banking application testing should not miss a must-have verification of blocking scripts. QATestLab shares the most typical ones:

Nothing is endless or what limits to check

The effective functioning of banking applications is hardly possible without customer limitations. They usually deal with:

  1. payment limits for unauthorized users
  2. one-time payment limits for authorized users
  3. payment limits for authorized users with no bank card

To Summarize

Working on a project for banking applications requires maximum accuracy and minimum risks. Professional QA for mobile banking applications provides additional competencies[4] in thorough software testing and confidence in the quality of this product. It is for you to decide how good this approach matches the needs of your project.

Related Posts:

Endnotes:
  1. QATestLab: http://qatestlab.com/
  2. customers’ profiles: https://blog.qatestlab.com/2017/06/16/positive-user-experience/
  3. Checklist: http://qatestlab.com/resources/knowledge-center/checklist-based/
  4. additional competencies: http://qatestlab.com/services/
  5. Difference Between Checklist and Coverage Map: https://blog.qatestlab.com/2014/05/08/what-is-the-difference-between-a-checklist-and-a-coverage-map/
  6. What Activities Should Mobile Testing Include?: https://blog.qatestlab.com/2014/01/31/what-activities-should-be-included-in-mobile-testing/
  7. Video Downloading Software: Сommon Bottlenecks and their Solutions: https://blog.qatestlab.com/2019/03/14/video-downloading-software/
  8. Before release: How focus testing helped to reveal critical bugs: https://blog.qatestlab.com/2019/03/11/e-learning-focus-testing/
  9. Checklist for Test Plan Review. Sample-Based: https://blog.qatestlab.com/2019/03/04/checklist-for-test-plan/

Source URL: https://blog.qatestlab.com/2019/02/20/qa-mobile-banking/