測試
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
大眾運輸業者 (PTO) 及其系統整合商 (發卡機構) 必須先在 Google 錢包中,完成下列模組化實作測試案例,才能導入 Google 錢包。
一般測試案例
完成並驗證所有必要的 Google Wallet API 大眾運輸 QR code 正式發布前測試。
動詞專用測試案例
除了一般測試案例外,請在啟動整合之前完成下列 Motics 特定測試案例。
測試 |
預期結果 |
查看 Google 錢包中的 Motics 條碼。 |
Motics 條碼每隔幾秒就會動態旋轉。 |
您可以使用驗證工具或檢查裝置檢查或驗證 Google 錢包中顯示的 Motics 條碼。 |
條碼掃描成功,且系統會將票券視為有效。 |
在活動開始日期前至少 4 天,將 Motics 條碼票券儲存至 Google 錢包。 |
直到支援單生效日期和時間之前才會顯示條碼。 |
將 Motics 條碼儲存在一部裝置中的 Google 錢包,然後嘗試將同一張票券儲存在第二部裝置上。 |
第二部裝置上的儲存流程失敗。 |
從 Google 錢包中移除已儲存的 Motics 票券。 |
系統會將票券從 Google 錢包中移除,同一張票券可順利儲存至其他裝置。 |
透過發卡機構線上商店取消連結已經儲存的 Motics 票證。 |
系統會從初始裝置中移除票券 (如果已連上網路),相同的票券可順利重新儲存至其他裝置。 |
嘗試移除並重新儲存票券數次。 |
超過發卡機構定義的啟用上限後,即無法儲存票券。 |
除非另有註明,否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權,程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間:2025-08-29 (世界標準時間)。
[null,null,["上次更新時間:2025-08-29 (世界標準時間)。"],[[["\u003cp\u003ePublic Transit Operators and system integrators must complete general Google Wallet API Transit QR code pre-launch testing and Motics-specific test cases before launch.\u003c/p\u003e\n"],["\u003cp\u003eMotics barcodes in Google Wallet dynamically rotate for security, and are verifiable using standard inspection devices.\u003c/p\u003e\n"],["\u003cp\u003eMotics tickets saved to Google Wallet before their validity period will only display the barcode at the designated start date and time.\u003c/p\u003e\n"],["\u003cp\u003eEach 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.\u003c/p\u003e\n"],["\u003cp\u003eIssuers can define activation limits to prevent unlimited removal and re-saving of Motics tickets, enhancing security.\u003c/p\u003e\n"]]],["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"],null,["# Testing\n\nPublic Transit Operators (PTOs) and their system integrators (issuers) need to\ncomplete the following test cases for a Motics implementation in\nGoogle Wallet prior to launch.\n\nGeneral test cases\n------------------\n\nComplete and verify all the required Google Wallet API Transit QR code [Pre-launch\ntesting](/wallet/tickets/transit-passes/qr-code/test-and-go-live/prelaunch-testing).\n\nMotics specific test cases\n--------------------------\n\nIn addition to the General test cases, complete the following Motics specific\ntest cases prior to launching the integration.\n\n| Test | Expected result |\n|----------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|\n| Observe the Motics barcode in Google Wallet. | The Motics barcode dynamically rotates every few seconds. |\n| 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. |\n| 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. |\n| 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. |\n| 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. |\n| 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. |\n| Attempt to remove \\& re-save a ticket several times. | The ticket can't be saved once the issuer defined activation limit has been exceeded. |"]]