Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
O teste completo é composto por duas etapas: sandbox e produção com lançamento gradual.
Teste de sandbox:execute uma série de casos de teste no seu inventário de sandbox usando o front-end do sandbox. Os URLs do inventário do sandbox podem ser acessados em
Inventory > Inventory
. Encontre um comerciante que esteja "Ativo (no sandbox)" e clique no link na coluna mais à direita (se disponível) ou na linha e no link "RwG - E2E".
Teste de produção com lançamento gradual:quando você concluir o teste do sandbox, entre em contato com seu contato do Google e sua conta será colocada em um estado de "lançamento gradual", momento em que seu inventário de produção vai ficar disponível para agendamento, mas não será descoberto externamente pelos usuários finais em nenhuma propriedade do Google. O inventário lançado em fase de testes pode ser acessado em
Inventário > Inventário
, encontre um comerciante que esteja "Pronto" e clique no link na coluna mais à direita
(se disponível) ou clique na linha e no link "RwG - E2E". Os detalhes sobre como acessar esse inventário e as precauções especiais que você precisa tomar com esses URLs estão disponíveis aqui. Execute um conjunto semelhante de casos de teste, assim como no ambiente
do sandbox.
Casos de teste
Os testes completos a seguir são realizados como parte dos testes de sandbox e
de produção com lançamento gradual:
Faça um agendamento pelo Centro de ações e confirme se ele aparece corretamente no seu sistema.
Verifique se os e-mails de confirmação foram enviados e se o horário e o agendamento
estão corretos.
Cancele o agendamento pelo Centro de ações e confirme se ele foi
cancelado corretamente no seu sistema.
Agende outro horário pelo Centro de ações e acione o cancelamento no seu sistema com a API Booking Notification.
Remova um slot específico do seu sistema e verifique se ele foi removido corretamente na Central de ações usando BatchAvailabilityLookupResponse e atualizações em tempo real do inventário (se aplicável).
Observação: os atrasos devem ser inferiores a cinco minutos para RTU.
Modifique um agendamento no Centro de ações e confirme se ele aparece corretamente
no seu sistema.
Clique em vários espaços para garantir que não haja erros BatchAvailabilityLookup.
Para se preparar para o lançamento, preencha o
questionário de preparação para o lançamento. O envio desse
formulário informa ao Google que você está com tudo pronto para o lançamento.
Consulte também a seguinte lista de verificação final:
Os uploads de feed ocorrem diariamente.
As taxas de falha do servidor de agendamento são inferiores a 5%.
As taxas de falha das atualizações em tempo real são inferiores a 5%.
Os dados dos usuários são transmitidos com segurança.
Não há solicitações de agendamento de terceiros no seu back-end.
O verificador de disponibilidade foi executado por mais de três dias (de preferência em um fim de semana)
com taxas de erro e indisponibilidade inferiores a 5%.
Depois de concluir essas etapas, entre em contato com seu representante do Centro de ações
para agendar a data de lançamento.
[null,null,["Última atualização 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.\u003c/p\u003e\n"],["\u003cp\u003eBefore launching, partners must complete Sandbox and Soft-launched Production testing, including a series of test cases like booking, cancelling, and modifying appointments.\u003c/p\u003e\n"],["\u003cp\u003ePartners need to monitor their daily feed uploads, booking server, and real-time update error rates throughout the testing process.\u003c/p\u003e\n"],["\u003cp\u003eTo initiate the launch process, partners should fill out a launch readiness questionnaire and ensure they meet specific criteria, including low error rates and secure data transmission.\u003c/p\u003e\n"],["\u003cp\u003eFinal launch approval requires a review by an Actions Center representative after all prerequisites are met.\u003c/p\u003e\n"]]],["End-to-end testing involves Sandbox and Soft-launched Production stages. Sandbox testing uses test cases against sandbox inventory, ensuring the booking lifecycle functions without live bookings. Soft-launched Production testing, accessed via a specific URL, tests against production inventory, which is not publicly discoverable. Test cases include booking, canceling, modifying, and removing slots, with monitoring of feeds, booking server, and real-time updates. Prepare for launch by completing a questionnaire and the contact information form in Partner Portal, ensuring minimal failure rates and secure data transmission.\n"],null,["# Step 6: 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/local-services/e2e/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/local-services/e2e/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/local-services/e2e/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/local-services/e2e/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."]]
