test(google-genai): Move google-genai integration tests to use a real client#21909
Merged
Conversation
Replaces the hand-written MockGoogleGenerativeAI classes in the truncation and system-instructions scenarios with the real @google/genai SDK driven by an express mock server, matching the rest of the suite. The auto integration already wraps clients via the same instrumentGoogleGenAIClient the fakes used, so dropping the manual wrap is behavior-preserving. Adds the express-server transaction filter to instrument-no-truncation.mjs (the fakes made no HTTP calls, so it wasn't needed before). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
nicohrubec
changed the title
nicohrubec
requested review from
JPeer264,
andreiborza and
mydea
and removed request for
a team
JPeer264
approved these changes
Jul 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
similar to #21906
Using a real client should generally be more useful as this is what we instrument and also allows us to reuse the integration suites for our orchestrion ports since orchestrion injects the channels only in the real client.