Skip to content

[Refactor] Reuse shared Responses client mock in X.AI tests - #1182

Draft
zoomote[bot] wants to merge 1 commit into
mainfrom
refactor/xai-test-utils-0l3imnen4dykb
Draft

[Refactor] Reuse shared Responses client mock in X.AI tests#1182
zoomote[bot] wants to merge 1 commit into
mainfrom
refactor/xai-test-utils-0l3imnen4dykb

Conversation

@zoomote

@zoomote zoomote Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

Created by Roomote. Follow up by mentioning @roomote, in the web UI, or in Discord.

What changed

  • Reused the shared mockOpenAiResponsesClient factory in the X.AI provider spec.
  • Preserved the X.AI-specific Responses API payloads, stream fixtures, reasoning cases, tool assertions, and error handling tests.

Why this change was made

This continues the incremental test-utils rollout after the shared helper foundations and provider batches. It removes repeated Responses client mock construction while preserving the clarity of the X.AI-specific tests.

Impact

Test-only refactor. X.AI behavior is unchanged, and future Responses API provider tests have a shared, Vitest-hoisting-safe client mock.

@codecov

codecov Bot commented Aug 7, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant