You are developing reusable infrastructure as code modules. Each module contains integration tests that launch the module in a test project. You are using GitHub for source control. You need to contin

A Jenkins server could be used, but 'periodically run all tests' does not align with the requirement to 'continuously test your feature branch' and 'before changes are accepted' as effectively as a direct pull request trigger.

Asking pull request reviewers to run integration tests is a manual process and does not fulfill the requirement to 'automate the integration tests' or ensure consistent execution.

Triggering all tests to run *after* a pull request is merged means that potential issues would only be discovered after the code is already integrated into the main branch, violating the 'before changes are accepted' requirement.

Using Cloud Build to run tests triggered by every GitHub pull request ensures that continuous testing is performed automatically on feature branches before merging, which aligns with the requirement for all code to be tested before acceptance. Running tests in a specific folder allows for targeted testing of individual modules, optimizing CI pipeline efficiency.