Skip to content

Add unit tests for chat history in FirebaseAI #14955

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

ryanwilson
Copy link
Member

This commit introduces two new unit tests to FirebaseAI/Tests/Unit/ChatTests.swift:

  1. testChatHistory(): This test verifies the chat history functionality when starting with a pre-existing history. It ensures that new messages (both user and model) are correctly appended to the history.
  2. testChatHistoryWithEmptyInitialHistory(): This test covers the scenario where the chat starts with an empty history. It validates that the first user message and the subsequent model response correctly initialize and populate the history.

Both tests utilize MockURLProtocol to simulate network responses, ensuring reliable and isolated testing of the chat history logic.

This commit introduces two new unit tests to `FirebaseAI/Tests/Unit/ChatTests.swift`:

1.  `testChatHistory()`: This test verifies the chat history functionality when starting with a pre-existing history. It ensures that new messages (both user and model) are correctly appended to the history.
2.  `testChatHistoryWithEmptyInitialHistory()`: This test covers the scenario where the chat starts with an empty history. It validates that the first user message and the subsequent model response correctly initialize and populate the history.

Both tests utilize `MockURLProtocol` to simulate network responses, ensuring reliable and isolated testing of the chat history logic.
Copy link
Contributor

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

@google-oss-bot
Copy link

1 Warning
⚠️ Did you forget to add a changelog entry? (Add #no-changelog to the PR description to silence this warning.)

Generated by 🚫 Danger

ryanwilson and others added 2 commits June 11, 2025 12:58
The previous commit for adding chat history tests (feat/add-chat-history-tests)
resulted in a CI failure due to a type mismatch in the MockURLProtocol.requestHandler.
The handler expected an AsyncLineSequence<URL.AsyncBytes>? for the response body,
but the tests were providing [Data].

This commit corrects the issue by:
- Modifying the testChatHistory() and testChatHistoryWithEmptyInitialHistory()
  functions in FirebaseAI/Tests/Unit/ChatTests.swift.
- The mock network response data is now provided as an AsyncStream<String>.
  This aligns with the pattern used in the existing testMergingText() function,
  which uses fileURL.lines (an AsyncLineSequence<String>) and passes CI.

This change ensures that the mock data is supplied in a format that
MockURLProtocol can correctly process, resolving the type error.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants