Stay organized with collections
Save and categorize content based on your preferences.
End-to-end testing happens in two stages: Sandbox testing and Soft-launched
Production testing.
Sandbox testing: Run through a series of test cases against your
sandbox inventory using the sandbox frontend. URLs to your Sandbox inventory can be accessed
under
Inventory > Inventory
, find a merchant that is "Live (in Sandbox)" then either click on the link on the
rightmost column (if available) or click on the row and click on the "RwG - E2E" link.
Soft-launched Production testing: When you have completed Sandbox
testing, reach out to your Google contact, and your account will be placed
into a "soft-launched" state, at which point your production inventory will
become bookable, but will not be externally discoverable by end users on
any Google properties. Your soft-launched inventory can be accessed under
Inventory > Inventory
, find a merchant that is "Ready" then either click on the link on the rightmost column
(if available) or click on the row and click on the "RwG - E2E" link. Details on how to access
this inventory, and special precautions you need to take with these URLs, are
available here. Run through a similar set of test cases as you did in your Sandbox
environment.
Test cases
The following end-to-end tests are performed as part of both Sandbox and
Soft-launched Production testing:
Make a booking through the Actions Center and confirm the booking shows
up correctly in your system.
Check that the confirmation emails are sent out and that the time and
booking listed are correct.
Cancel the booking through the Actions Center and confirm that it's
canceled correctly in your system.
Book another appointment through the Actions Center and trigger the
cancellation from your system with the Booking Notification API
Remove a particular slot from your system, and check to see if it's
removed properly on the Actions Center through BatchAvailabilityLookupResponse
and inventory real-time updates (if applicable).
Note: Delays should take less than five minutes for RTU.
Modify a booking from the Actions Center and confirm the modified booking shows up correctly
in your system.
Click on various slots to ensure there are no BatchAvailabilityLookup errors
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-05-20 UTC."],[[["\u003cp\u003eEnd-to-end testing involves two stages: Sandbox testing using a simulated environment and Soft-launched Production testing using real inventory in a controlled setting.\u003c/p\u003e\n"],["\u003cp\u003eBefore launch, conduct thorough testing covering booking creation, confirmation, cancellation, and modification, as well as inventory updates and error handling.\u003c/p\u003e\n"],["\u003cp\u003eSoft-launched Production testing uses real inventory, resulting in actual bookings and transactions, requiring careful coordination with merchants.\u003c/p\u003e\n"],["\u003cp\u003eMonitor crucial metrics like daily feed uploads, booking server, and real-time update error rates, ensuring they remain below acceptable thresholds.\u003c/p\u003e\n"],["\u003cp\u003ePrior to launch, complete the launch readiness questionnaire, provide mandatory contact information, and ensure system stability through the availability checker.\u003c/p\u003e\n"]]],["End-to-end testing involves Sandbox and Soft-launched Production stages. Sandbox testing uses test cases against sandbox inventory, accessible via the Partner Portal, ensuring no live bookings. Soft-launched Production testing, after contacting Google, makes production inventory bookable but not externally discoverable. Test cases include booking, cancellation, slot removal, and modification through Actions Center. Monitor feed uploads, booking server, and real-time update error rates. Prior to launch, complete the launch readiness questionnaire, fill contact information, and verify checklist items.\n"],null,["# End-to-end testing happens in two stages: Sandbox testing and Soft-launched\nProduction testing.\n\n1. **Sandbox testing:** Run through a series of test cases against your sandbox inventory using the sandbox frontend. URLs to your Sandbox inventory can be accessed under **[Inventory \\\u003e Inventory](https://partnerdash.google.com/apps/reservewithgoogle/inventory?env=sandbox)** , find a merchant that is \"Live (in Sandbox)\" then either click on the link on the rightmost column (if available) or click on the row and click on the \"RwG - E2E\" link. **Note:** While your sandbox should reflect real world inventory, it should not place live bookings against it. Ensure the entire booking lifecycle can be tested without live bookings.\n2. **Soft-launched Production testing:** When you have completed Sandbox testing, reach out to your Google contact, and your account will be placed into a \"soft-launched\" state, at which point your production inventory will become bookable, but will not be externally discoverable by end users on any Google properties. Your soft-launched inventory can be accessed under **[Inventory \\\u003e Inventory](https://partnerdash.google.com/apps/reservewithgoogle/inventory)** , find a merchant that is \"Ready\" then either click on the link on the rightmost column (if available) or click on the row and click on the \"RwG - E2E\" link. Details on how to access this inventory, and special precautions you need to take with these URLs, are [available here](/actions-center/verticals/dining/partner-portal/inventory/merchant-matching#soft-launched-inventory). Run through a similar set of test cases as you did in your Sandbox environment.\n\n| **Note:** During end-to-end testing, it is important to monitor the daily feed uploads, as well as the error rates for the booking server and real-time updates.\n\nTest cases\n----------\n\nThe following end-to-end tests are performed as part of both Sandbox and\nSoft-launched Production testing:\n\n- Make a booking through the Actions Center and confirm the booking shows up correctly in your system.\n- Check that the confirmation emails are sent out and that the time and booking listed are correct.\n- Cancel the booking through the Actions Center and confirm that it's canceled correctly in your system.\n- Book another appointment through the Actions Center and trigger the cancellation from your system with the Booking Notification API\n- Remove a particular slot from your system, and check to see if it's removed properly on the Actions Center through `BatchAvailabilityLookupResponse` and inventory real-time updates (if applicable). Note: Delays should take less than five minutes for RTU.\n- Modify a booking from the Actions Center and confirm the modified booking shows up correctly in your system.\n- Click on various slots to ensure there are no `BatchAvailabilityLookup` errors\n\n| **Note:** Bookings made against your \"soft-launched\" production inventory are real bookings, and any payment that is collected will result in a real transaction. It is strongly recommended that you inform the merchant that you are running a test, and that you cancel (and optionally refund) any test bookings that were created during testing.\n\nDebugging\n---------\n\nWhen debugging availability slot related issues, use the\n[Availability Viewer](/actions-center/verticals/dining/partner-portal/inventory/availability-viewer) in the\n[Partner Portal](https://partnerdash.google.com/apps/reservewithgoogle/inventory/availability) to see a history of slot changes.\n\nLaunch Readiness\n----------------\n\nTo prepare for launch, fill out the\n[launch readiness questionnaire](https://docs.google.com/a/google.com/forms/d/e/1FAIpQLSchnCLZ1NczAMrJsxiR1gIf4hutQnGM8wAbgKrEtkQ4a_i4Iw/viewform). Submission of this\nform tells Google that you're ready to launch.\n\nAdditionally, please fill out all required fields in the\n[**Configuration \\\u003e Contact Information**](/actions-center/verticals/dining/partner-portal/testing/mandatory-information) tab\nin the [Partner Portal](https://partnerdash.google.com/apps/reservewithgoogle/contactinformation). It is required to fill out the contact information form before launch.\n\nIn preparation for launch, review the following final checklist:\n\n- The feed uploads occur daily.\n- The booking server failure rates are less than 5%.\n- The real-time updates failure rates are less than 5%.\n- Users' data is transmitted securely.\n- There are no third-party booking requests from your backend.\n- The availability checker has run for \\\u003e 3 days (preferably over a weekend) with unavailable and error rates less than 5%.\n\n| **Note:** Enable or disable the availability checker via the [Features](/actions-center/verticals/dining/partner-portal/testing/features) page in Partner Portal.\n\nOnce these steps are complete, reach out to your Actions Center\nrepresentative to schedule your launch date."]]