Thanks to visit codestin.com
Credit goes to github.com

Skip to content

test(bigquery): use special test region for integration tests #13456

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
shollyman merged 3 commits into from
Dec 10, 2025
Merged

test(bigquery): use special test region for integration tests #13456

shollyman merged 3 commits into from
Dec 10, 2025

Conversation

@shollyman
Copy link
Contributor

@shollyman shollyman commented Dec 8, 2025

This PR migrates existing integration tests to leverage a special test region for capturing failures earlier.

related: internal b/460196591

@shollyman shollyman requested review from a team as code owners December 8, 2025 22:05
@product-auto-label product-auto-label bot added the api: bigquery Issues related to the BigQuery API. label Dec 8, 2025
@gemini-code-assist
Copy link
Contributor

gemini-code-assist bot commented Dec 8, 2025

Summary of Changes

Hello @shollyman, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request centralizes the region used for BigQuery integration tests by introducing a defaultTestLocation constant and applying it across relevant test cases. This change aims to create a more controlled and consistent testing environment, thereby improving the reliability of integration tests and facilitating earlier detection of region-specific issues.

Highlights

  • Standardized Test Region: Integration tests for BigQuery now consistently use a special test region, us-east7, to ensure a uniform testing environment.
  • Early Failure Detection: Migrating tests to a dedicated region is intended to help capture and identify potential failures earlier in the development cycle.
  • Dependency Updates: The go.work.sum file was updated, indicating changes to various Go module dependencies, including AWS SDK, gRPC Gateway, Prometheus, and OpenCensus exporters.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist[bot]
gemini-code-assist bot reviewed Dec 8, 2025
View reviewed changes
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request refactors the BigQuery integration tests to use a consistent, special test region (us-east7). This is achieved by introducing a defaultTestLocation constant and replacing various hardcoded location strings like "EU", "US", and "us-east1" throughout the test files. This change improves the maintainability and consistency of the test suite. The modifications in the Go test files are correct and align with the goal of centralizing the test region. The updates to go.work.sum reflect necessary dependency changes.

@shollyman shollyman added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Dec 9, 2025
@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Dec 9, 2025
@shollyman shollyman added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Dec 9, 2025
@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Dec 9, 2025
@shollyman shollyman added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Dec 9, 2025
@kokoro-team kokoro-team removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Dec 9, 2025
@shollyman shollyman merged commit d796344 into googleapis:main Dec 10, 2025
9 checks passed
cpriti-os pushed a commit to cpriti-os/google-cloud-go that referenced this pull request Dec 16, 2025
@shollyman @cpriti-os
test(bigquery): use special test region for integration tests (google…
fb8b8ca 
…apis#13456)

This PR migrates existing integration tests to leverage a special test
region for capturing failures earlier.

related: internal b/460196591
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@alvarowolfx alvarowolfx alvarowolfx approved these changes

+1 more reviewer

@gemini-code-assist gemini-code-assist[bot] gemini-code-assist[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

api: bigquery Issues related to the BigQuery API.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@shollyman @alvarowolfx @kokoro-team