SBN

Methods for Automation Testing QR Code Flows

QR-code-flow-testing

Brief Intro to QR Codes

Quick Response (QR) codes are ubiquitous nowadays; scanning the QR code can take you to a restaurant’s menu, direct you to a customer’s website, download apps, access theme park maps, etc. For the past couple of years, smartphones have provided support for using native cameras to scan the QR code directly; the deep-linked QR code then navigates the user to the respective App’s specific page.

How HYPR Uses QR Codes

At HYPR, we use QR codes in the user registration and authentication flow in both the Desktop MFA client and Customer Authentication website products. Following is an example of the Customer Authentication website flow:

  1. User registration process:
    1. During the registration process, for an authenticated user, a QR code is generated with relying party (server) details and displayed on the Website. 
    2. By scanning the QR code, the user submits a request to register their device to the relying party. 
    3. As per the FIDO2 protocol (the user’s private/public key is generated from a biometric such as a fingerprint or FaceID and is used to sign transactions initiated by a relying party), the device is registered to the relying party. 
  2. User authentication process:
    1. During the process, the username is entered on the website login form
    2. HYPR server validates the user name and generates a QR code with the relying party (server) and user’s session details, and is displayed on the Website. 
    3. The user scans the QR code and authenticates with the previously registered biometric.
    4. The relying party validates the authentication request per FIDO2 protocol, and the passwordless authentication flow is complete. 

Some Challenges We Encountered in Automation Testing the QR Code Flow

Challenge 1

The automation script needs to context switch between mobile and web/desktop to complete a registration process or an authentication process.

Solution

The automation framework was modified to address this problem using the following steps:

  1. Create separate drivers for each application
  2. Implement Selenium Grid (a smart proxy server that makes it easy to run tests in parallel on multiple machines) and customize the framework to context switch between mobile and web/desktop applications
  3. Keep the Mobile driver active to overcome the screen timeouts
  4. Collate the results from these different drivers
  5. Handle various points of failure and errors

Challenge 2

An app may have transaction timeouts for security reasons. Once a QR code is generated, the script must coordinate across multiple systems and complete the flow. The flow must be completed in a short time frame; otherwise, the transaction will fail.

Solution

The automation framework was customized to address various delays with device procurement, app download, installation delay, node registration delays, etc. The automation script was thoughtfully built to kick off the execution only once all the test prerequisites were satisfied.

Challenge 3

In automated tests, tests must run unassisted, so it’s impossible to access the camera and scan the QR code.

Solution Part A: Programmatically Decoding the QR code in Automation Tests

The following tools were used in the implementation of this solution:

  • Selenium WebDriver is an open-source framework used to automate a web-based application
  • Selenium Grid allows to run tests in parallel on multiple devices
  • Appium is a mobile open-source framework and is used to automate mobile-based applications and windows based application
  • Cucumber  framework allows defining the tests in feature file format using Behavior-Driven Development (BDD) methodology.
  • Java programming language
  • Maven is a software project management and comprehension tool. Using Maven, we can build, test, and manage Java-based projects.

ZXing (“zebra crossing”), an open-source, multi-format 1D/2D barcode image processing library, is used to decode the QR code. 

Steps:

  1. Add maven dependency in the pom.xml as shown here.

QR-Flow-Testing-Screen1

  1. Website use case — QR image’s src attribute is used to the decode the QRCode.

QR-Flow-Testing-Screen2

  1. Windows client use case — Please note that the approach used to decode a native Windows desktop application’s QR code differs from website use cases! A screenshot of the QR image is used to decode the QR code.

QR-Flow-Testing-Screen3

Solution Part B: Use Decoded QR Code in a Custom HYPR Mobile App

As mentioned, automated tests can’t scan the QR code via camera. So, our solution at HYPR was to enter the decoded QR code text in a special test version of the HYPR mobile app. The benefits of automated test validation far outweigh the maintenance of an additional test app version.

qr-code-test-app-opt

Summary:

Automated testing of QR code flows can pose challenges for teams, but there are steps you can take to overcome them. We hope the methods of the approach outlined here help your own efforts.

New call-to-action

*** This is a Security Bloggers Network syndicated blog from HYPR Blog authored by Sachin Gaikwad, SDET Team Lead, HYPR. Read the original post at: https://blog.hypr.com/automation-testing-qr-code-flows

Secure Guardrails