test: test history and TASK_STATE_INPUT_REQUIRED in test_end_to_end.py#745
test: test history and TASK_STATE_INPUT_REQUIRED in test_end_to_end.py#745
Conversation
Summary of ChangesHello, 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 significantly improves the robustness of the integration test suite by adding detailed assertions for task history at various stages of task execution. It also introduces a critical new test case to ensure the correct handling and resumption of tasks that require user input, enhancing the reliability of the agent's state management. Highlights
Changelog
Activity
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request adds tests for task history and the TASK_STATE_INPUT_REQUIRED state. The changes to the MockAgentExecutor are appropriate for enabling these tests. However, many of the new assertions related to task.history seem to be incorrect. They consistently misrepresent the expected length and content of the task history, especially regarding the inclusion of user messages and the cumulative nature of history across multiple interactions. I've added specific comments pointing out these discrepancies in the tests.
958486e to
0a889c5
Compare
0a889c5 to
74ce553
Compare
Add
task.historyassertions and testTASK_STATE_INPUT_REQUIRED.Note: tests use
get_taskAPI call in non-blocking tests for assertions astaskreturned fromClientand maintained byClientTaskManagercan't be trusted and handles history in a different way compared to the server (see #734).