Testing
Stay organized with collections
Save and categorize content based on your preferences.
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. |
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-06-12 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-06-12 UTC."],[[["Public Transit Operators and system integrators must complete general Google Wallet API Transit QR code pre-launch testing and Motics-specific test cases before launch."],["Motics barcodes in Google Wallet dynamically rotate for security, and are verifiable using standard inspection devices."],["Motics tickets saved to Google Wallet before their validity period will only display the barcode at the designated start date and time."],["Each Motics ticket can only be saved to one device at a time, ensuring single-device usage, and can be removed and re-saved on a different device if needed through the app or the issuer's website."],["Issuers can define activation limits to prevent unlimited removal and re-saving of Motics tickets, enhancing security."]]],["PTOs and system integrators must complete specific test cases for Motics implementation in Google Wallet. This includes verifying the dynamic rotation and scannability of the Motics barcode. They must also confirm that tickets saved before their start date aren't shown, and that saving the same ticket on multiple devices is blocked. Tickets should be removable and resavable, except when activation limits are met. Additionally, general Google Wallet API Transit QR code pre-launch testing must be completed.\n"]]
