Mantieni tutto organizzato con le raccolte
Salva e classifica i contenuti in base alle tue preferenze.
I test end-to-end vengono eseguiti in due fasi: test in sandbox e test di produzione con lancio graduale.
Test della sandbox:esegui una serie di casi di test sull'inventario della sandbox utilizzando il frontend della sandbox. Puoi accedere agli URL del tuo inventario della sandbox
in
Inventario > Inventario
, trova un commerciante "Pubblicato (in sandbox)", poi fai clic sul link nella
colonna più a destra (se disponibile) o sulla riga e poi sul link "RwG - E2E".
Test di produzione con lancio graduale:dopo aver completato i test in sandbox, contatta il tuo contatto Google e il tuo account verrà impostato in stato di "lancio graduale". A questo punto, l'inventario di produzione potrà essere prenotato, ma non sarà rilevabile esternamente dagli utenti finali su nessuna proprietà Google. Puoi accedere all'inventario lanciato in anteprima in
Inventario > Inventario
, trova un commerciante in stato "Pronto", poi fai clic sul link nella colonna più a destra
(se disponibile) o fai clic sulla riga e poi sul link "RwG - E2E". Qui sono disponibili dettagli su come accedere a questo inventario e sulle precauzioni speciali da adottare con questi URL. Esegui un insieme di casi di test simile a quello che hai eseguito nell'ambiente
Sandbox.
Scenari di test
I seguenti test end-to-end vengono eseguiti sia nell'ambiente sandbox sia nei test di produzione con lancio graduale:
Effettua una prenotazione tramite il Centro azioni e verifica che la prenotazione venga visualizzata correttamente nel tuo sistema.
Verifica che le email di conferma siano state inviate e che l'ora e la prenotazione elencate siano corrette.
Annullala tramite il Centro azioni e verifica che sia stata annullata correttamente nel tuo sistema.
Prenota un altro appuntamento tramite il Centro azioni e attiva l'annullamento dal tuo sistema con l'API Booking Notification
Rimuovi un determinato slot dal sistema e controlla se è stato rimosso correttamente nel Centro azioni tramite BatchAvailabilityLookupResponse
e gli aggiornamenti in tempo reale dell'inventario (se applicabili).
Nota: i ritardi dovrebbero durare meno di cinque minuti per l'RTU.
Modifica una prenotazione dal Centro azioni e verifica che la prenotazione modificata venga visualizzata correttamente nel tuo sistema.
Fai clic su vari slot per assicurarti che non ci siano errori BatchAvailabilityLookup
In preparazione al lancio, controlla l'elenco di controllo finale che segue:
I caricamenti dei feed avvengono ogni giorno.
I tassi di errore del server di prenotazione sono inferiori al 5%.
I tassi di errore degli aggiornamenti in tempo reale sono inferiori al 5%.
I dati degli utenti vengono trasmessi in modo sicuro.
Non ci sono richieste di prenotazione di terze parti dal tuo backend.
Lo strumento di controllo della disponibilità è stato eseguito per più di 3 giorni (preferibilmente durante un fine settimana)
con tassi di disponibilità ed errori inferiori al 5%.
Una volta completati questi passaggi, contatta il tuo rappresentante di Actions Center per pianificare la data di lancio.
[null,null,["Ultimo aggiornamento 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."]]
