Testing
Google suggests the criteria in the following tables to determine if your loyalty card is ready for public release.
All UI testing should be done with the use of the Google Wallet 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 loyalty card (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 loyalty card on the Google Wallet app*. |
| Update the points balance for a consumer's loyalty program. | The updated point balance appears in the loyalty programs list view and expanded view for the specific loyalty card within 24 hours. |
Change the class that a specific LoyaltyObject references to move the consumer
to a different loyalty tier (only applicable if your loyalty program has different tiers each
represented by a different LoyaltyClass). |
The new tier appears in the expanded view of the loyalty card on the Google Wallet app within 24 hours. |
| 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 loyalty card. |
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 |
|---|---|
| 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 |
| loyalty card renders correctly on device. | N/A |
| Click on website link in Google Wallet app for your loyalty program. | 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 Wallet app. | Barcode scans and loyalty card is conveyed. |
| Merchant's service personnel trained to handle loyalty scanning. | N/A |
Google uses the criteria in the following tables to determine if your Cards are ready for public release. Print out this page and verify each item to ensure you are ready to submit your Card for release.
Button Tests
This section lists criteria for tests that exercise the Add to Google Wallet 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 Add to Google Wallet button disappears after a loyalty card was saved:
|
The Add to Google Wallet button reappears on your web site. |
| If you have designed your web site so that the Add to Google Wallet button disappears after a loyalty card was saved. | A string appears to indicate that the loyalty card has been saved. |
Save a pass
This section lists criteria for tests that exercise clicking the Add to Google Wallet button.
| Test | Expected result |
|---|---|
| Click Add to Google Wallet button on your web site. | The JWT that is created contains all valid domains for button (https and http, not www) |
| Click Add to Google Wallet button on your web site. | The correct card is saved to Google Wallet. |
| Click Add to Google Wallet button on your web site. | The card is saved and you cannot press the button again. |
| Click Add to Google Wallet 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 Add to Google Wallet button.
| Test | Expected result |
|---|---|
| Ensure your button adheres to the Add to Google Wallet button placement section of the Brand guidelines. | N/A |
| Ensure your button adheres to the Add to Google Wallet button design section of the Brand guidelines. | N/A |
Go Live
Now that you've successfully tested your integration, it's time to go live! Make sure that you complete the following go-live check list.
Complete Business Profile
In order to get publishing access you need to complete your business profile by logging in to Google Pay and Wallet Console. Click on Business Profile, set your payments profile and comple your business information.
Create at least 1 class
While you are in demo mode for Google Wallet API, make sure that you've created at least one pass class created that you want to publish live.
Request publishing access
When all the above steps are completed you can then request for production access. To do this log in to the console. Navigate to Google Wallet API and click on "Request Publishing Access".
Publishing access granted
Our team will review the request and grant publishing access. Once access is granted, your existing classes will be live! You can start creating objects and distributing it to your customers. Additional classes created after receiving publishing access will be live. However, we might assess these class time to time and reach out to you in cases of any concerns.