0 Fork 0

mirror of https://github.com/firebase/firebase-ios-sdk synced 2026-11-11 22:55:59 +05:45

Files

T

Andrew Heard c2186eaa52 fix(ai): attach signature-only reasoning to a part with data (#16886 )

Gemini 3.x models return the thought signature of a text response on a
trailing empty text part. The executor records this as a signature-only
`.reasoning` transcript entry, which `GeminiTranscriptTranslator` then
round-tripped on the next turn as a stand-alone `Part` containing only
`thought` and `thoughtSignature` and no `data`.

The Gemini Developer API tolerates a part with no data, but the Gemini
Enterprise Agent Platform rejects it nondeterministically with
`400 INVALID_ARGUMENT` ("Request contains an invalid argument."),
making any multi-turn session that follows a completed text response
flaky on that backend (e.g. `sessionRespondSequentialToolCalls`).

Never emit a signature-only reasoning entry as a data-less part:

- A signature preceding a response is attached to the response's text
  part.
- A signature following a response is attached to the last part of the
  current model turn, mirroring how the server originally sent it.
- If there is no model part to attach to, fall back to a thought part
  with empty text so the `data` oneof is always populated.

Replace the unit test that asserted the data-less shape with coverage
for all three cases.

2026-10-09 21:51:04 -07:00

IntegrationTests

refactor(ai): revert renaming to Gemini Enterprise API (#16846 )

2026-10-05 23:54:12 +00:00

GeminiErrorMapperTests.swift

feat(ai): add GeminiLanguageModel (#16601 )

2026-09-04 18:05:45 -04:00

GeminiLanguageModelTests.swift

feat(ai): use VALIDATED function calling mode in GLM (#16649 )

2026-09-17 17:51:18 -04:00

GeminiRequestTranslatorTests.swift

feat(ai): use VALIDATED function calling mode in GLM (#16649 )

2026-09-17 17:51:18 -04:00

GeminiTranscriptTranslatorTests.swift

fix(ai): attach signature-only reasoning to a part with data (#16886 )

2026-10-09 21:51:04 -07:00

GenerationSchema+GeminiTests.swift

feat(ai): add GeminiLanguageModel guided generation support (#16619 )

2026-09-08 12:01:29 -04:00

IntegrationTestingBackendTests.swift

refactor(ai): revert renaming to Gemini Enterprise API (#16846 )

2026-10-05 23:54:12 +00:00

README.md

feat(ai): add GeminiLanguageModel tool calling (#16620 )

2026-09-08 18:19:18 -04:00

README.md

GeminiLanguageModel Tests

Unit and integration test suites validating GeminiLanguageModel protocol conformance, streaming response generation, transcript translation, error mapping, and backend integration.

Quick Start

# Run all unit tests (fast, ~0.04s, skips integration tests)
swift test --skip Integration

# Run all tests in this target (including integration tests)
swift test --filter GeminiLanguageModelTests

Test Suites

Suite / File	Scope	Strategy
`GeminiLanguageModelTests.swift`	Protocol conformance, single/multi-turn responses, streaming, tool calling	Unit (`MockHTTPURLProtocol`)
`GenerationSchema+GeminiTests.swift`	JSON Schema encoding and property ordering conversion	Unit (pure transformation)
`GeminiRequestTranslatorTests.swift`	Request, generation config, tool declarations, and tool mode mapping	Unit (pure transformation)
`GeminiTranscriptTranslatorTests.swift`	Apple `Transcript` <-> Gemini payload mapping (tools, reasoning, prompts)	Unit (pure transformation)
`GeminiErrorMapperTests.swift`	HTTP and API error mapping to `LanguageModelError`	Unit (exhaustive mapping)
`IntegrationTestingBackendTests.swift`	Endpoint resolution and credential discovery	Unit / Infrastructure
`IntegrationTests/`	End-to-end Gemini and Firebase AI Logic integration tests	Integration (see `IntegrationTests/README.md`)

Testing Architecture

This target separates tests into two distinct tiers:

Unit Tests (Default):
- Use MockHTTPURLProtocol for deterministic, zero-network, sub-second execution.
- Run cleanly in offline, CI, and local development environments without any credentials or background daemons.
Integration Tests (IntegrationTests/):
- Tagged with .tags(.integration) and gated by .requireIntegrationTestingBackend.
- Exercise endpoints on Google Cloud and Firebase using configured credentials.
- Isolated in the IntegrationTests/ subfolder so unit test runs are never slowed down by network timeouts or external dependencies.

Tip

For details on configuring credentials and parameterizing integration tests, see the Integration Tests Guide.