Testing checklists

Select one of the following pass verticals to learn more about how it can be used.


Google suggests the criteria in the following tables to determine if your transit passes are ready for public release.

All UI testing should be done with the use of the Google Pay app on Android-based devices.

General

This section lists criteria for general functional tests.

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

Classes and objects

This section lists criteria for tests that exercise classes or objects functionality.

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 offer on the Google Pay app*.
Set the validTimeInterval.end interval on your offer to a time in the near future. Offer should be set to expired when time has passed.
Your class contains a places ID (with associated locations) or latitude/longitude values so that consumers are notified when they are within close proximity to one of your locations. N/A
Travel to within close proximity of a location in your class or places ID. An alert should occur on your phone indicating there is a merchant nearby for your offer.
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

This section lists criteria for tests that exercise general elements of the user interface.

Test Expected result
Offer image describes the merchant or offer. 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
Offer renders correctly on device. N/A
Click on website link in Google Pay app for your offer. Website link should bring up correct merchant web page.
Merchant does not display barcode if they don't have barcode scanning capabilities in their stores. N/A

In-Store Testing

This section lists criteria for tests to be carried out at in-store locations.

Test Expected result
Test barcode scanning at merchant point of sale with Google Pay apps. Barcode scans and offer is redeemed.
Merchant's service personnel trained to handle offer scanning. N/A

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

Button Tests

This section lists criteria for tests that exercise the Save to Google Pay button.

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 web site so that the Save to Google Pay button disappears after a offer was saved: 1. Click the Google Pay API for Passes button on your web site. 2. Remove the saved offer from Google Pay. The Save to Google Pay button reappears on your web site.
If you have designed your web site so that the Save to Google Pay button disappears after an offer was saved. A string appears to indicate that the offer has been saved.

Save a pass

This section lists criteria for tests that exercise clicking the Save to Google Pay button.

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

Brand guidelines

This section lists criteria to check the brand guidelines of the Save to Google Pay button.

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