Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
Las pruebas de extremo a extremo se realizan en dos etapas: el análisis de la zona de pruebas
y el de producción en vista previa.
Pruebas de la zona de pruebas: Ejecuta una serie de casos de prueba con tu
inventario de esta zona usando el frontend de este entorno. Puedes acceder a las URLs de tu inventario de la zona de pruebas en
Inventario > Inventario
. Busca un comercio que esté en "Publicación (en la zona de pruebas)" y, luego, haz clic en el vínculo de la
columna más a la derecha (si está disponible) o en la fila y, luego, en el vínculo "RwG - E2E".
Prueba de producción con lanzamiento previo: Cuando hayas completado las pruebas en la
zona de pruebas, comunícate con tu contacto de Google y tu cuenta se colocará
en un estado de "lanzamiento previo". En ese momento, tu inventario de producción se
podrá reservar, pero los usuarios finales no podrán encontrarlo de forma externa en
ninguna propiedad de Google. Puedes acceder a tu inventario lanzado de forma gradual en
Inventario > Inventario
. Busca un comercio que esté en "Listo" y, luego, haz clic en el vínculo de la columna más a la derecha (si está disponible) o en la fila y, luego, en el vínculo "RwG - E2E". Aquí puedes ver los detalles sobre cómo acceder a este inventario y las precauciones especiales que debes tener con estas URLs. Ejecuta un conjunto de casos de prueba similar al que usaste en tu
entorno de zona de pruebas.
Casos de prueba
Las siguientes pruebas de extremo a extremo se realizan como parte del análisis
de la zona de pruebas y de producción en vista previa:
Realiza una reserva a través del Centro de acciones y confirma que se muestre
correctamente en tu sistema.
Verifica que se envíen los correos electrónicos de confirmación y que la hora y la
reserva que se muestran sean correctas.
Cancela la reserva a través de Actions Center y confirma que se haya cancelado
correctamente en tu sistema.
Reserva otra cita a través del Centro de acciones y activa la cancelación desde tu sistema con la API de Booking Notification
Quita un horario disponible específico de tu sistema y comprueba
si se quitó correctamente en el Centro de acciones a través de BatchAvailabilityLookupResponse
y las actualizaciones en tiempo real del inventario (si corresponde).
Nota: Las demoras deberían tardar menos de cinco minutos en la RTU.
Modifica una reserva desde el Centro de acciones y confirma que la reserva modificada se muestre correctamente
en tu sistema.
Haz clic en varios horarios disponibles para asegurarte de que no haya errores de BatchAvailabilityLookup.
Como preparación para el lanzamiento, revisa la siguiente lista de control final:
Las cargas del feed se realizan a diario.
Las tasas de error del servidor de reservas son inferiores al 5%.
Las tasas de error de las actualizaciones en tiempo real son inferiores al 5%.
Los datos de los usuarios se transmiten de forma segura.
No hay solicitudes de reservas de terceros de tu backend.
El verificador de disponibilidad se ejecutó durante más de 3 días (preferentemente, durante un fin de semana)
con tasas de error y de falta de disponibilidad inferiores al 5%.
Una vez que completes estos pasos, comunícate con tu representante de Actions Center para programar la fecha de lanzamiento.
[null,null,["Última actualización: 2025-07-26 (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 before public launch.\u003c/p\u003e\n"],["\u003cp\u003eBoth testing stages require running a series of test cases, including booking, cancelling, modifying appointments, and validating data flow and system updates.\u003c/p\u003e\n"],["\u003cp\u003eBefore launch, ensure daily feed uploads, monitor booking server and real-time updates error rates, secure user data transmission, and run the availability checker for a minimum of 3 days with low error rates.\u003c/p\u003e\n"],["\u003cp\u003ePartners need to complete a launch readiness questionnaire and fill out mandatory contact information in the Partner Portal to signal launch readiness and schedule the launch date with Google.\u003c/p\u003e\n"],["\u003cp\u003eBookings made during Soft-launched Production testing are real and involve real transactions, requiring careful coordination with merchants to avoid unintended consequences.\u003c/p\u003e\n"]]],["End-to-end testing involves Sandbox and Soft-launched Production stages. Actions include running test cases, accessible via the Partner Portal, to make, cancel, and modify bookings. Verify booking details, confirmation emails, and inventory removal. Monitor daily feed uploads, booking server, and real-time update error rates. Before launch, complete the readiness questionnaire, contact information in the Partner Portal, and ensure low error rates, secure data transmission, and no third-party booking requests. Then contact the Actions Center representative to schedule the launch.\n"],null,["# Step 4: End-to-end testing\n\nEnd-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/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.\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/reservations/waitlists/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/reservations/waitlists/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/reservations/waitlists/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."]]
