# Step 4: End-to-end testing

End-to-end testing happens in two stages: Sandbox testing and Soft-launched
Production testing.

1. **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](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]
   > **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.

2. **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](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](https://developers.google.com/actions-center/verticals/reservations/waitlists/partner-portal/inventory/merchant-matching#soft-launched-inventory). Run through a similar set of test cases as you did in your Sandbox environment.

> [!NOTE]
> **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.

## 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

> [!NOTE]
> **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.

## Debugging

When debugging availability slot related issues, use the
[Availability Viewer](https://developers.google.com/actions-center/verticals/reservations/waitlists/partner-portal/inventory/availability-viewer) in the
[Partner Portal](https://partnerdash.google.com/apps/reservewithgoogle/inventory/availability) to see a history of slot changes.

## Launch Readiness

To prepare for launch, fill out the
[launch readiness questionnaire](https://docs.google.com/a/google.com/forms/d/e/1FAIpQLSchnCLZ1NczAMrJsxiR1gIf4hutQnGM8wAbgKrEtkQ4a_i4Iw/viewform). Submission of this
form tells Google that you're ready to launch.

Additionally, please fill out all required fields in the
[**Configuration \> Contact Information**](https://developers.google.com/actions-center/verticals/reservations/waitlists/partner-portal/testing/mandatory-information) tab
in the [Partner Portal](https://partnerdash.google.com/apps/reservewithgoogle/contactinformation). It is required to fill out the contact information form before launch.

In preparation for launch, review the following final checklist:

- The feed uploads occur daily.
- The booking server failure rates are less than 5%.
- The real-time updates failure rates are less than 5%.
- Users' data is transmitted securely.
- There are no third-party booking requests from your backend.
- The availability checker has run for \> 3 days (preferably over a weekend) with unavailable and error rates less than 5%.

> [!NOTE]
> **Note:** Enable or disable the availability checker via the [Features](https://developers.google.com/actions-center/verticals/reservations/waitlists/partner-portal/testing/features) page in Partner Portal.

Once these steps are complete, reach out to your Actions Center
representative to schedule your launch date.