How can you implement automated performance testing in Cloud Build for each commit to prevent Cloud Spanner performance regressions, while handling potential concurrent test executions from multiple simultaneous commits?

Exam-Like

Create a new project with a random name for every build. Load the required data. Delete the project after the test is run.

3.3%

Create a new Cloud Spanner instance for every build. Load the required data. Delete the Cloud Spanner instance after the test is run.

66.7%

Create a project with a Cloud Spanner instance and the required data. Adjust the Cloud Build build file to automatically restore the data to its previous state after the test is run.

13.3%

Start the Cloud Spanner emulator locally. Load the required data. Shut down the emulator after the test is run.

16.7%

Google Professional Cloud Developer

Get started today

Comments

How can you implement automated performance testing in Cloud Build for each commit to prevent Cloud Spanner performance regressions, while handling potential concurrent test executions from multiple simultaneous commits?