Testing is important, very important. Here we try to give you an overview of how you can test your Mobile Connect integration.

Pre-requisites

Develop against the sandbox and learn to use the different operators in your testing. The sandbox allows you to disable the authenticator which enables you to test faster. The sandbox documentation explains how you can use the sandbox.

Request access to operator API as soon as possible but don't test until you feel all is working ok. Testing with operators networks allows you to understand how the authenticators will impact the user flow.

 

Create a test plan

Before you start testing it is important to prepare a comprehensive test plan that covers as many different scenarios as possible to reduce the risk of bugs/crashes. As every test plan is going to be different for each application below is set out the general criteria that should be taken into account when testing your application and includes a number of use cases.

 

General Advice

  • Use actual Operator subscriptions/SIM cards from the operators you’re planning to use Mobile Connect with.
  • Use different kinds of SIM cards (data, voice).
  • Use dual SIM-devices with a different combination of SIM cards.
    • 2 unregistered SIMs from same MNO.
    • 2 unregistered SIMs from different MNOs.
    • 1 registered and 1 unregistered SIM from the same MNO.
    • 1 registered and 1 unregistered SIM from different MNOs.
  • Use a mobile phone in hotspot mode.
  • Use 3g/4g mobile hotspots.
  • Use a broadband modem.
  • Check different types of authenticators.
  • Check multiple devices and browsers from different vendors.
  • Understand what type of devices your users may have (e.g. feature phone/smartphone).

The above shows how important it is to test different scenarios not just PC+Phone.

 

Authentication use cases

The Mobile Connect Authentication product category offers a simple and globally ubiquitous log-in mechanism, below are some common authentication use cases

  1. User has a Mobile Connect account and uses mobile network connection (HTTP header enrichment authenticate method)
  2. User doesn’t have a Mobile Connect account and uses mobile network connection (HTTP header enrichment authenticate method)
  3. User has a Mobile Connect account and uses a Wi-Fi hot spot (successful authentication)
  4. User has a Mobile Connect account and uses Wi-Fi hotspot (unsuccessful authentication)
  5. User has a Mobile Connect account and uses a Wi-Fi hotspot (successful authentication)
  6. User has a Mobile Connect account and uses a Wi-Fi hot spot (unsuccessful authentication)

 

User has a Mobile Connect account and uses mobile network connection (HTTP header enrichment authenticate method)

Steps

  • Make sure you use mobile network connection
  • Authenticate

Result

  • The user is authenticated

Notes

  • Try to check with different types of mobile network connection (2g, 3g, 4g) and switching between these types (2g -> 3g, 2g -> 4g, 3g -> 2g, 3g -> 4g, 4g -> 2g, 4g -> 3g)
  • Try to check it works with an unstable mobile network connection. This includes cases with low signal connection and lost connection
  • Use dual SIM devices with same and different operators

 

User doesn’t have a Mobile Connect account and uses mobile network connection (HTTP header enrichment authenticate method)

Steps

  • Make sure you use mobile network connection
  • Authenticate
  • Confirm Mobile Connect account creation

Result

  • The user should be authenticated

Notes

  • Try to check it works with different types of mobile network connection (2g, 3g, 4g) and switching between these types (2g -> 3g, 2g -> 4g, 3g -> 2g, 3g -> 4g, 4g -> 2g, 4g -> 3g)
  • Try to check it works with an unstable mobile network connection. This includes cases with low signal connection and lost connection
  • Use 2SIM devices with same and different operators

 

User has a Mobile Connect account and uses a Wi-Fi hot spot (successful authentication)

Steps

  • Make sure you use Wi-Fi connection
  • Authenticate
  • Enter valid MSISDN or choose MCC/MNC pair on the discovery screen
  • Accept the authentication on the authentication device:
    • Send confirmation response in case the endpoint uses a USSD authenticator
    • Click on link in case the endpoint use SMS + URL authenticator
    • Enter valid PIN if the endpoint uses SIM applet authenticator

Result

  • The user should be authenticated

Notes

  • Try to check in cases where the user switches network connection between Wi-Fi hotspot and mobile network connection
  • Try to check with different types of mobile hotspots and working using connection to the mobile phone in hotspot mode
  • Try to check it works using broadband modems
  • Check with a consumption device different from the authentication device (for example, try to authenticate using a tablet as consumption device and mobile phone as authentication device)

 

User has a Mobile Connect account and uses Wi-Fi hotspot (unsuccessful authentication)

Steps

  • Make sure you use Wi-Fi connection
  • Make authentication
  • Enter valid MSISDN or choose MCC/MNC pair on the discovery screen
  • Refuse the authentication on the authentication device:
    • Send cancel response in case the endpoint use USSD authenticator
    • Not to click on link in case the endpoint use SMS + URL authenticator
    • Enter invalid PIN in case the endpoint use SIM applet authenticator

Result

  • The user should not be authenticated

 

User has a Mobile Connect account and uses a Wi-Fi hotspot (successful authentication)

Steps

  • Make sure you use Wi-Fi connection
  • Authenticate
  • Confirm Mobile Connect account creation
  • Enter valid MSISDN or choose MCC/MNC pair on the discovery screen
  • Accept the authentication on the authentication device:
    • Send confirmation response in case the endpoint uses USSD authenticator
    • Click on link in case the endpoint uses SMS + URL authenticator
    • Enter valid PIN in case the endpoint uses SIM applet authenticator

Result

  • The user should be authenticated

Notes

  • Try to check it works in cases where user switch network connection between Wi-Fi hot spot and mobile network connection
  • Try to check it works with different types of mobile hot spots and working using connection to the mobile phone in hot spot mode
  • Try to check it works using broadband modems
  • Check authentication using consumption device different from authentication device (for example, try to authenticate on a tablet as consumption device and mobile phone as authentication device)

 

User has a Mobile Connect account and uses a Wi-Fi hot spot (unsuccessful authentication)

Steps

  • Make sure you use Wi-Fi connection
  • Authenticate
  • Confirm Mobile Connect account creation
  • Enter valid MSISDN or choose MCC/MNC pair on the discovery screen
  • Refuse the authentication on the authentication device:
    • Send cancel response in case the endpoint use USSD authenticator
    • Not to click on link in case the endpoint use SMS + URL authenticator
    • Enter invalid PIN in case the endpoint use SIM applet authenticator

Result

  • The user should not be authenticated

 

Authorisation use cases

The Mobile Connect Authorisation offers contextual authentication with a Yes/No option for users to authorise requests on their mobile phone. The most common authorisation use cases are:

  1. User has a Mobile Connect account and uses mobile network connection (successful authorisation)
  2. User has a Mobile Connect account and use mobile network connection (unsuccessful authorisation)
  3. User has a Mobile Connect account and use Wi-Fi hot spot (successful authorisation)

 

User has a Mobile Connect account and uses mobile network connection (successful authorisation)

Steps

  • Make sure you use mobile network connection
  • Make authorisation request
  • Confirm the authorisation using following authenticators:
    • Send confirmation response in case the endpoint use USSD authenticator
    • Click on link in case the endpoint use SMS + URL authenticator
    • Enter valid PIN in case the endpoint use SIM applet authenticator

    Result

    • The user should be authorised

    Notes

    • Try to check it works with different types of mobile network connection (2g, 3g, 4g) and switching between these types (2g -> 3g, 2g -> 4g, 3g -> 2g, 3g -> 4g, 4g -> 2g, 4g -> 3g)
    • Try to check it works with unstable mobile network connection. It includes cases with low signal connection, lost connection
    • Use 2SIM devices with same and different operators

     

    User has a Mobile Connect account and use mobile network connection (unsuccessful authorisation)

    Steps

    • Make sure you use mobile network connection
    • Make authorisation request
    • Confirm the authorisation using following authenticators:
      • Send cancel response in case the endpoint use USSD authenticator
      • Not to click on link in case the endpoint use SMS + URL authenticator
      • Enter invalid PIN in case the endpoint use SIM applet authenticator

      Result

      • The user should not be authorised

       

      User has a Mobile Connect account and use Wi-Fi hot spot (successful authorisation)

      Steps

      • Make sure you use Wi-Fi connection
      • Make authorisation request
      • Enter valid MSISDN or choose MCC/MNC pair on the discovery screen
      • Accept the authorization on the authentication device:
        • Send confirmation response in case the endpoint use USSD authenticator
        • Click on link in case the endpoint use SMS + URL authenticator
        • Enter valid PIN in case the endpoint use SIM applet authenticator

        Result

        • The user should not be authorised

        Notes

        • Try to check it works in cases where user switch network connection between Wi-Fi hot spot and mobile network connection
        • Try to check it works with different types of mobile hot spots and working using connection to the mobile phone in hot spot mode
        • Try to check it works using broadband modems
        • Check authentication using consumption device different from authentication device (for example, try to authenticate on a tablet as consumption device and mobile phone as authentication device)

         

        Identity use cases

        The Mobile Connect Identity product category helps end users engage with digital services quickly and efficiently, share data when they want to, and assert their identity when needed

        1. Mobile Connect Phone Number
        2. Mobile Connect Sign-up
        3. Mobile Connect National ID

         

        Mobile Connect Phone Number

        Steps

        • Make sure you use Wi-Fi connection
        • Make identity call (Phone Number type)
        • Enter valid MSISDN or choose MCC/MNC pair on the discovery screen
        • Accept the identifying on the authentication device:
          • End confirmation response in case the endpoint use USSD authenticator
          • Enter valid PIN in case the endpoint use SIM applet authenticator

        Result

        • The user’s MSISDN should be shared with service provider

         

        Mobile Connect Sign-up

        Steps

        • Make sure you use Wi-Fi connection
        • Make identity call (Sign-up type)
        • Enter valid MSISDN or choose MCC/MNC pair on the discovery screen
        • Accept the identifying on the authentication device:
          • Send confirmation response in case the endpoint use USSD authenticator
          • Enter valid PIN in case the endpoint use SIM applet authenticator

        Result

        • The user’s first name/last name, street address, postal code, country should be shared with service provider

         

        Mobile Connect National ID

        Steps

        • Make sure you use Wi-Fi connection
        • Make identity call (National ID type)
        • Enter valid MSISDN or choose MCC/MNC pair on the discovery screen
        • Accept the identifying on the authentication device:
          • Send confirmation response in case the endpoint use USSD authenticator
          • Enter valid PIN in case the endpoint use SIM applet authenticator

        Result

        • The user’s first name/last name, date of birth, national identifier should be shared with service provider