Test Requirements

  • Partners must complete three phases of testing: End-to-End Testing in Sandbox, Finance User Acceptance Testing in Sandbox, and End-to-End Testing in Production.

  • Partners need to provide specific artifacts for each test phase for review and approval before launch.

  • Testing and development are conducted in a sandbox environment with potentially shorter duration SKUs for convenience.

  • Successful completion of all test phases and submission of required artifacts are essential for partners to get approval for launch.

Integration milestones

To ensure a successful integration and launch, you must adhere to the following technical milestones :

  • End-to-End (E2E) Testing (Sandbox, Production): You are required to execute a predefined list of end-to-end test cases to verify the Critical User Journeys (CUJs) on the final front-end User Experience (UX) in both sandbox and production environments.
    • In Production, it is recommended to limit the number of transactions as this will incur charges.
  • Testing Environment and SKUs: Testing and development activities are to be conducted in the staging environment.
  • Invoice Validation: Google and yourselves will verify the contents of the invoice and attest to their correctness, or make changes where needed.

Your Google Integration Team will provide you with a copy of the test cases for your product.

Required Artifacts for review/approval

You must provide artifacts to meet the test requirements before proceeding to subsequent integration steps. The final E2E test results must pass and be submitted to Google for launch approval:

  • Finance UAT: Transaction details for all test cases.
  • Payments Test: Process payments on the invoice
  • E2E Testing: This includes the test results for all test cases, accompanied by a video capture of the main user journey.

Testing Environment and SKUs

Testing and development activities are to be conducted in the staging environment. For streamlined development and testing, you can request Google to configure SKUs with shorter durations (e.g., 1-day SKUs).