You need to build a CI/CD pipeline for a containerized application in Google Cloud. Your development team uses a central Git repository for trunk-based development. You want to run all your tests in t

Git hooks are client-side and require developers to run tests *before* pushing, which doesn't guarantee testing for all new versions *in the pipeline* after a push, nor does it leverage Cloud Build for central CI.

Git hooks are client-side and require developers to run tests *before* pushing, which doesn't guarantee testing for all new versions *in the pipeline* after a push, nor does it leverage Cloud Build for central CI.

Running unit tests *with the container* after building it might be less efficient or flexible than running tests as a dedicated step *before* image creation, and it doesn't explicitly state the trigger upon push.

When code is pushed to the central Git repository, Cloud Build is triggered to automatically run unit tests. This ensures that only code that passes initial quality checks proceeds to subsequent build and deployment steps, which is crucial for trunk-based development and improving application quality.