Skip to content

docs: update unit tests execute command#2074

Merged
averikitsch merged 3 commits into
mainfrom
developer-update
Dec 9, 2025
Merged

docs: update unit tests execute command#2074
averikitsch merged 3 commits into
mainfrom
developer-update

Conversation

@gRedHeadphone

@gRedHeadphone gRedHeadphone commented Nov 28, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

Description

update unit tests execute command in DEVELOPER.md to exclude integration tests

PR Checklist

  • Make sure you reviewed
    CONTRIBUTING.md
  • Make sure to open an issue as a
    bug/issue
    before writing your code! That way we can discuss the change, evaluate
    designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)
  • Make sure to add ! if this involve a breaking change

@gRedHeadphone gRedHeadphone requested a review from a team November 28, 2025 07:16
@gemini-code-assist

gemini-code-assist Bot commented Nov 28, 2025

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @gRedHeadphone, 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 refines the documentation for running unit tests by updating the command to execute tests specifically within the cmd and internal directories. This change aims to provide a more precise and potentially faster testing experience for developers working on these core components.

Highlights

  • Unit Test Command Update: The command for executing unit tests locally in the DEVELOPER.md file has been updated to be more specific, targeting only the cmd and internal directories.
  • Improved Test Scope: The previous command go test -race -v ./... which tested all packages, has been refined to go test -race -v ./cmd/... ./internal/... to focus testing on relevant application and internal logic.
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 Nov 28, 2025
View reviewed changes

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

Copy link
Copy Markdown
Contributor

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 updates the command for running unit tests to be more specific, targeting only the cmd/ and internal/ directories. This is a good change to prevent accidentally running integration tests, which might require special setup.

I've added one comment with a suggestion to consider a more maintainable long-term solution using build tags, which would automatically include new directories with unit tests in the future.

Overall, the change is a positive improvement to the developer documentation.

Comment thread DEVELOPER.md
@averikitsch averikitsch enabled auto-merge (squash) December 9, 2025 23:34
@averikitsch averikitsch merged commit ea9e2d1 into main Dec 9, 2025
11 checks passed
@averikitsch averikitsch deleted the developer-update branch December 9, 2025 23:48
rahulpinto19 pushed a commit that referenced this pull request Dec 10, 2025
@gRedHeadphone @averikitsch @rahulpinto19
docs: update unit tests execute command (#2074)
6405e26 
## Description

update unit tests execute command in DEVELOPER.md to exclude integration
tests

## PR Checklist

- [x] Make sure you reviewed

[CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md)
- [ ] Make sure to open an issue as a

[bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose)
  before writing your code! That way we can discuss the change, evaluate
  designs, and agree on the general idea
- [x] Ensure the tests and linter pass
- [x] Code coverage does not decrease (if any source code was changed)
- [x] Appropriate docs were updated (if necessary)
- [x] Make sure to add `!` if this involve a breaking change

Co-authored-by: Averi Kitsch <akitsch@google.com>
rahulpinto19 pushed a commit that referenced this pull request Dec 17, 2025
@gRedHeadphone @averikitsch @rahulpinto19
docs: update unit tests execute command (#2074)
3f69160 
## Description

update unit tests execute command in DEVELOPER.md to exclude integration
tests

## PR Checklist

- [x] Make sure you reviewed

[CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md)
- [ ] Make sure to open an issue as a

[bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose)
  before writing your code! That way we can discuss the change, evaluate
  designs, and agree on the general idea
- [x] Ensure the tests and linter pass
- [x] Code coverage does not decrease (if any source code was changed)
- [x] Appropriate docs were updated (if necessary)
- [x] Make sure to add `!` if this involve a breaking change

Co-authored-by: Averi Kitsch <akitsch@google.com>
vinodhinic pushed a commit to vinodhinic/genai-toolbox that referenced this pull request Jan 14, 2026
@gRedHeadphone @averikitsch @vinodhinic-google
docs: update unit tests execute command (googleapis#2074)
8bd7e98 
## Description

update unit tests execute command in DEVELOPER.md to exclude integration
tests

## PR Checklist

- [x] Make sure you reviewed

[CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md)
- [ ] Make sure to open an issue as a

[bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose)
  before writing your code! That way we can discuss the change, evaluate
  designs, and agree on the general idea
- [x] Ensure the tests and linter pass
- [x] Code coverage does not decrease (if any source code was changed)
- [x] Appropriate docs were updated (if necessary)
- [x] Make sure to add `!` if this involve a breaking change

Co-authored-by: Averi Kitsch <akitsch@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@averikitsch averikitsch averikitsch 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

@averikitsch averikitsch

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@gRedHeadphone @averikitsch @duwenxin99