Test

General

Test Expected result
Call customer service phone numbers provided with the flight (if applicable). Customer service department is accessible using the provided phone number.

Classes and objects

Test Expected result
Add a message to the class using the REST API. Message appears at the top of the list of messages in the expanded view of the flight on the Google Pay app*.
Set the class.localScheduledDepartureDateTime on your flight to a time in near future. Flight should send notification three hours prior to class.localScheduledDepartureDateTime.
Classes have a reviewStatus of Approved N/A

*You should also test adding messages to individual objects using the REST API if you plan on sending messages to individual users.

User Interface

Test Expected result
Flight image describes the airline. N/A
Ensure all required fields of your template are populated with correct information. N/A
Ensure your images adhere to all image guidelines in the Brand guidelines N/A
Ensure your string values adhere to all headings guidelines in the Brand guidelines. N/A
Flight renders correctly on device. N/A
Click on website link in Google Pay app for your flight. Website link should bring up correct merchant web page.

In-Store Testing

Test Expected result
Test barcode (object.barcode.value) scanning at merchant point of sale with Google Pay app. Barcode scans and flight is redeemed.
Merchant's service personnel trained to handle flight scanning. N/A

Google uses the criteria in the following tables to determine if your flight Passes are ready for public release.

Button Rendering

Test Expected result
Test button in Chrome browser. Button renders and functions correctly on partner's webpage in Chrome.
Test button in Firefox browser. Button renders and functions correctly on partner's webpage in Firefox.
Test button in Safari browser. Button renders and functions correctly on partner's webpage in Safari.
Test button in Internet Explorer 9 browser. Button renders and functions correctly on partner's webpage in Internet Explorer 9 (Citrix).
Test button at different browser zoom levels. Button renders properly at various browser zoom levels.
Test button's rendering speed. A single button renders in no more than 1 second.
If you have designed your website so that the Save to Google Pay button disappears after a flight was saved: 1. Click the Google Pay API for Passes button on your website. 2. Remove the saved flight from Google Pay. The Save to Google Pay button reappears on your web site.
If you have designed your website so that the Save to Google Pay button disappears after an flight was saved. A string appears to indicate that the flight has been saved.

Saving an Flight

Test Expected result
Click Save to Google Pay button on your website. The JWT that is created contains all valid domains for button (https and http, not www)
Click Save to Google Pay button on your website. The correct flight is saved to Google Pay.
Click Save to Google Pay button on your website. The flight is saved and you cannot press the button again.
Click Save to Google Pay button on your website. The JWT that is created references a class that is approved.

User Interface

Test Expected result
Ensure your button adheres to the Save to Google Pay button placement section of the Brand guidelines. N/A
Ensure your button adheres to the Save to Google Pay button design section of the Brand guidelines. N/A

Envoyer des commentaires concernant…

Google Pay for Passes