1 / 20

Mobile Banking – Common Pitfalls and How to avoid them

Mobile Banking – Common Pitfalls and How to avoid them. Sanjeeb Singh Yogita Sachdeva Infosys Limited (NASDAQ: INFY). Abstract.

ella
Download Presentation

Mobile Banking – Common Pitfalls and How to avoid them

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Mobile Banking – Common Pitfalls and How to avoid them Sanjeeb Singh Yogita Sachdeva Infosys Limited (NASDAQ: INFY)

  2. Abstract With the advent of technology, there is an exponential growth in the technologies concerning Mobile Devices. Mobile banking space is seeing more traction here and with all the payments and security involved the testing of mobile banking application has become even more critical. Mobile banking QA not only relies upon functionality but usability, security, network and performance are also paramount and need to be tested properly. Majority of our clients are over the Globe and validating a banking transaction across Global carriers bring a challenge of positioning QA professionals globally. This challenge gets multi folded when the roll out happens on varied devices. Cost is ever green component to be optimized. In such a scenario, demand arises for looking at certain mechanisms which can ensure the completeness and coverage of mobile banking QA on each handset globally with optimized cost. This paper will talk about these challenges in details from all the dimensions related to mobile banking which make it so complicated. • Critical transactional scenarios in banking specifically in treasury and payments • Types of Mobile banking QA which can be and can’t done by remote testing technique • How important it is to understand end user dynamics • Network and Security challenges for mobile banking app • Performance Challenges for mobile banking

  3. Abstract (Contd..) Also, this paper will cover certain proven practices and techniques which help to overcome the challenges •Proven device sampling techniques which will ensure the complete coverage for mobile banking QA team •Cost optimization techniques •Remote testing techniques •What NOT to Automate and Why •Network parametric testing techniques This research paper is completely based on the experiences and learning’s across various reputed banks and as an outcome of this, participants will be benefitted in getting to know a good picture of challenges in Mobile Banking QA and the relevant solutions.

  4. Outline of the Paper • Mobile Banking Evolution • Mobile Banking Services • Mobile Banking Domain • Mobility Transaction Flow • Mobile Banking Testing Method • Complexities involved in Mobile Banking QA • Challenges involved in Mobile Banking QA • Common Mistakes in Mobile Banking QA- Our Experience • Scenario 1 : Our experience in Remote Based Testing • Scenario 2 : Our experience in Security Testing • Scenario 3 : Our experience in Network Testing • Scenario 4 : Our experience in Localization Testing • Scenario 5 : Our experience in Desktop and Real Device Testing • Scenario 6 : Our experience in Emulator Testing • Recommendations

  5. Mobile Banking Evolution • Radical change in end user’s technology exposure are forcing organizations to embrace new technologies and transform their businesses into tech-savvy platforms • Banking and Financial services are also embracing Mobility big time • Gradual Evolution of Banking from branch banking to SMS banking to Mobile Banking with emerging technologies. • Mobile Banking with browser-based and native applications gaining momentum • Intuitive Mobile Banking apps for IPhone, Ipad and Prominent Android Devices are launched by global banks. Branch Banking Automated Teller Machine (ATM) Internet Banking Mobile Banking IVR-Based Banking SMS-Based Banking

  6. Mobile Banking Services • Services in Mobile Banking • SMS Banking • Mobile Web Banking • Native App Banking • A2P Messaging • Location Based Services • Near Field Communication • Remote Deposit Check • Augmented Reality

  7. Mobile Banking Domain

  8. Mobility Transaction Flow Base Transceiver Carrier Network Carrier Network Internet Internet Web Apps Web Apps Network Network Mobile Device Native Apps Native Apps Server Side

  9. Mobile Banking Testing Method

  10. Complexities involved in Mobile Banking QA • Complexities in Mobile Banking QA • Technical • SOA Architecture • SMS Based, WAP, LBS, NFC, RDC • Domain • 3rd party payment systems • Rate systems • Payment & reporting engines • Operational • Development and Testing environment setup • Procurement of devices with different network carriers

  11. Challenges involved in Mobile Banking QA • Challenges in Mobile Banking QA • Screen Size – Smallest Size(128 * 128) • Largest Size(1024 * 768) • Operating Systems – Android, IoS, Windows Mobile, RIM BB • User Interface – Touch/Keypad, Track pad/Trackball • Browsers – Android, Safari, RIM BB, IE • Geography- Different carriers • Network Access and Performance – Wi-Fi, 2G, 3G • Frequent upgrades- OS versions, App versions • Skills- Immature mobile Skill Market • Alliance Change – Nokia alliance with Windows.

  12. Scenario 1 : Our experience in Remote Based Testing • Remote Based Testing- a) Security Challenge while doing validation for banking application through remote based devices. Many a times QA tester acquire the device, login with the requisite credentials into the app and release the device without logout. In such cases, the other user can acquire the device and use the same session. • b) Also using remote based testing method for network and precise usability validation.

  13. Scenario 2 : Our experience in Security Testing One-time password (OTP) is the latest tool by the financial and banking service providers to fight against the mobile fraud. OTP is send to the customer through SMS whenever they want to perform critical transactions and the password is expired once used or after a designated life-cycle Sometimes QA team can fail to capture some of the critical real time scenarios associated with OTP during the test case preparation activity

  14. Scenario 3 : Our experience in Network Testing Mobile QA validated the impact of network hop on critical transaction with only one type of network switch (say GPRS to Wi-Fi). The impact of network variability may be different for network hop between different networks. Also doing the validation only with a single network carrier.

  15. Scenario 4 : Our experience in Localization Testing Localization Failure- Spanish banking user receives English SMS with transaction related info rendering it useless for him. The application supposed to be launched in multiple geography with the local languages get extensive validation for selected few languages only(assuming it will work for other local languages as well).

  16. Scenario 5 : Our experience in Desktop and Real Device Testing Validating the application features of the desktop instead on the actual device. User got an upgraded version of android app on his device but found some broken link and image distortion.

  17. Scenario 6 : Our experience in Emulator Testing Assuming that using the emulator, one can validate functional, security, usability, performance aspects of the application is a myth. Though one can cover lot of functional aspect through emulators, the test strategy can’t be built completely on emulator. It cannot validate the usability and performance of the application. Also one cannot rely on emulator for validating the transfers and payment features of m-banking solution due to security concerns.

  18. Recommendations

  19. References • Infosys project experience • Infosys resources (www.infosys.com)

  20. Q&A: Sanjeeb_Singh@infosys.com, yogita_s@infosys.com 20

More Related