Public Transit Operators (PTOs) and their system integrators (issuers) need to complete the following test cases for a Motics implementation in Google Wallet prior to launch.
General test cases
Complete and verify all the required Google Wallet API Transit QR code Pre-launch testing.
Motics specific test cases
In addition to the General test cases, complete the following Motics specific test cases prior to launching the integration.
| Test | Expected result |
|---|---|
| Observe the Motics barcode in Google Wallet. | The Motics barcode dynamically rotates every few seconds. |
| Inspect or validate the Motics barcode shown in Google Wallet using a validator or inspection device. | The barcode is successfully scanned and the ticket is considered valid. |
| Save a Motics barcode ticket to Google Wallet at least 4 days before the validity start date. | No barcode is shown until the ticket validity start date and time. |
| Save a Motics barcode ticket to Google Wallet on one device and then try to save the same ticket on a second device. | The save flow fails on the second device. |
| Remove an already saved Motics ticket from Google Wallet. | The ticket is removed from Google Wallet and the same ticket can be successfully re-saved on another device. |
| Unlink an already saved Motics ticket using the issuer webshop. | The ticket is removed from the initial device (if online) and the same ticket can be successfully re-saved on another device. |
| Attempt to remove & re-save a ticket several times. | The ticket can't be saved once the issuer defined activation limit has been exceeded. |