Sandbox Review

Sandbox testing is a comprehensive review of your Feed uploads, Booking Server, and Real-Time Updates.

You can request a review for your integration after all the Sandbox steps are completed in your End-to-End Onboarding Plan. To review your integration, you can submit test cases to the Actions Center Support Team through a form.

Testing runs across several consecutive days and takes up to seven business days to complete, if no issues are found. If the team finds issues that need to be resolved, they will reach out to you to correct them. After you resolve the issues you can request a new review. Testing then resets and begins from scratch.

Self-test

Before you request a review of your Sandbox environment, verify the following:

  1. All inventory is uploaded to the Sandbox environment with following conditions to assure data quality:

    1. Your merchant inventory has a high match rate.
    2. Your services aren't missing availability.
    3. Availability fidelity works as intended in following way:
      1. SchedulingRules and Resources are properly defined and work as expected.

  2. Your Sandbox infrastructure doesn't place actual bookings against live merchants' inventory.

  3. You have self-tested all known edge cases dependent on your internal business logic.

Request review

After completion of self-test and the Sandbox portion of the End-to-End Onboarding Plan milestones, create a new case in the Partner Portal to request review. When you press the link, you'll receive a form from the Actions Center Support Team to submit specific merchants and bookings to test your Sandbox integration.

Test cases

The following are some of the end-to-end tests that are performed as part of both Sandbox and Production testing:

  • Make a booking through the Actions Center and confirm that 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 cancelled 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.
  • Modify a booking from the Actions Center and confirm that the modified booking shows up correctly in your system.
  • Click various slots to verify that there are no BatchAvailabilityLookup errors.