测试
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
在发布之前,公交运营商 (PTO) 及其系统集成商(颁发者)需要先完成以下测试用例,以在 Google 钱包中实现 Motics。
常规测试用例
完成并验证所有必需的 Google Wallet API Transit 二维码发布前测试。
Motics 专用测试用例
除了常规测试用例之外,请在发布集成之前完成以下 Motics 专用测试用例。
测试 |
预期结果 |
查看 Google 钱包中的 Motics 条形码。 |
Motics 条形码每隔几秒就会动态轮换。 |
使用验证器或检查设备检查或验证 Google 钱包中显示的 Motics 条形码。 |
条形码已成功扫描,系统认为此票有效。 |
在失效日期前至少 4 天将 Motics 条形码票证保存到 Google 钱包。 |
在票券有效期开始日期和时间之前,不会显示条形码。 |
在一部设备上将 Motics 条形码票券保存到 Google 钱包,然后尝试在另一台设备上保存同一张票券。 |
保存流程在第二台设备上失败。 |
从 Google 钱包中移除已保存的 Motics 票券。 |
该票券会从 Google 钱包中移除,您可以在其他设备上成功地重新保存同一票券。 |
通过发卡机构网店解除关联已保存的 Motics 票券。 |
系统会将该票券从初始设备中移除(如果它已连接到网络),并且您可以在其他设备上成功地重新保存同一票券。 |
尝试多次移除并重新保存票券。 |
超出发卡机构定义的激活限制后,无法保存票券。 |
如未另行说明,那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可,并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情,请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-08-29。
[null,null,["最后更新时间 (UTC):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. |"]]