test(integration): migrate TPC operations tests to config file by PranjalC100 · Pull Request #4763 · GoogleCloudPlatform/gcsfuse

PranjalC100 · 2026-06-06T10:44:09Z

Description

Migrates the operations integration tests on TPC endpoint to execute from the common configuration file (test_config.yaml).

Adds a new tpc boolean property to ConfigItem to identify TPC-specific configurations.
Declares standard flat/hns/zonal compatibility for TPC configurations in test_config.yaml, combined with tpc: true.
Modifies BuildFlagSets() in setup.go to filter configurations based on whether the test is running on a TPC endpoint.
Deletes the custom/hardcoded RunTestOnTPCEndPoint flow in operations_test.go and handles it within the standard config setup.
Cleans up redundant local helpers in operations_test.go and uses package-level ones instead.

Link to the issue in case of a bug fix.

Fixes b/469970353

Testing details

Manual - Checked local compilation using go test -c ./tools/integration_tests/operations and checked general repo lint/compilation using make buildTest.
Unit tests - N/A
Integration tests - N/A (requires TPC endpoint and credentials)

Any backward incompatible change? If so, please explain.

N/A

gemini-code-assist · 2026-06-06T10:46:15Z

Summary of Changes

Hello, I'm Gemini Code Assist¹! 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 streamlines the integration testing framework by unifying TPC endpoint test execution with the existing configuration-driven approach. By moving hardcoded test parameters into the common YAML configuration, the codebase becomes more maintainable and consistent with other test suites, while also simplifying the test entry point.

Highlights

TPC Configuration Migration: Migrated TPC-specific integration tests from hardcoded logic in operations_test.go to the centralized test_config.yaml configuration file.
Config Schema Update: Added a tpc boolean property to ConfigItem to identify and filter TPC-specific test configurations.
Logic Refactoring: Updated BuildFlagSets in setup.go to handle TPC compatibility filtering and removed redundant local helper functions in the operations test suite.

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 the 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 counterproductive. 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.

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. ↩

codecov · 2026-06-06T10:46:36Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (d046938) to head (e574496).

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #4763       +/-   ##
==========================================
- Coverage   83.72%       0   -83.73%     
==========================================
  Files         168       0      -168     
  Lines       20776       0    -20776     
==========================================
- Hits        17395       0    -17395     
+ Misses       2736       0     -2736     
+ Partials      645       0      -645

Flag	Coverage Δ
unittests	`?`

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

gemini-code-assist

Code Review

This pull request refactors the integration tests for operations by removing hardcoded TPC configurations and helper functions in operations_test.go in favor of using the shared YAML configuration file. It introduces a TPCOnly field in the test configuration struct to filter TPC-specific test cases. The reviewer recommended renaming the TPCOnly struct field to TPC to maintain consistency with its YAML tag tpc and suggested a more flexible logic for partitioning TPC and non-TPC test cases.

meet2mky

TPC Build is still failing. Please see the kokoro failure.

…ion test setup

github-actions · 2026-06-08T05:04:48Z