MediaMetz/gemini-cli
1
0
Fork 0
mirror of https://github.com/google-gemini/gemini-cli.git synced 2026-03-18 01:51:20 -07:00
Code Issues Packages Projects Releases Wiki Activity

chore: remove cot style comments (#15735)

Browse Source
This commit is contained in:
Abhi
2025-12-30 16:43:33 -05:00
committed by GitHub
parent de1233b8ca
commit 0eb84f5133
1 changed files with 2 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
integration-tests/hooks-agent-flow.test.ts
View File

@@ -107,19 +107,6 @@ describe('Hooks Agent Flow', () => {
const input = fs.readFileSync(0, 'utf-8');
console.error('DEBUG: AfterAgent hook input received');
process.stdout.write("Received Input: " + input);
// Ensure separation between the echo and the JSON output if they were to run together (though relying on separate console calls usually separates by newline)
// usage of process.stdout.write does NOT add newline.
// But here we want strictly the output "Received Input..." to be present.
// We also need to output the JSON decision for the hook runner to consider it successful?
// Actually HookRunner parses the *last* valid JSON block or treats text as system message.
// If we output mixed text and JSON, HookRunner might get confused if we don't handle it right.
// Existing test expects "Received Input" in stdout. And "Hello World".
// It DOES NOT parse the decision?
// Wait, HookRunner logic:
// "if (exitCode === EXIT_CODE_SUCCESS && stdout.trim()) ... JSON.parse ..."
// If JSON.parse fails: "Not JSON, convert plain text to structured output"
// So if we output formatted text, it becomes "systemMessage".
// That is fine for this test as we don't check the decision, just the stdout content.
} catch (err) {
console.error('Hook Failed:', err);
process.exit(1);
@@ -161,7 +148,8 @@ describe('Hooks Agent Flow', () => {
);
expect(afterAgentLog).toBeDefined();
// Verify the hook stdout contains the input we echoed which proves the hook received the prompt and response
// Verify the hook stdout contains the input we echoed which proves the
// hook received the prompt and response
expect(afterAgentLog?.hookCall.stdout).toContain('Received Input');
expect(afterAgentLog?.hookCall.stdout).toContain('Hello validation');
// The fake response contains "Hello World"
@@ -220,16 +208,10 @@ describe('Hooks Agent Flow', () => {
(log) => log.hookCall.hook_event_name === 'AfterAgent',
);
// Should ensure BeforeAgent fired once
expect(beforeAgentLogs).toHaveLength(1);
// Should ensure AfterAgent fired once
// Note: If the tool call itself triggered BeforeTool/AfterTool, that's fine,
// but BeforeAgent/AfterAgent should only wrap the *entire* turn (User Request -> Final Answer).
expect(afterAgentLogs).toHaveLength(1);
// Verify the output log content to ensure we actually got the final answer
// (This implies the loop completed successfully)
const afterAgentLog = afterAgentLogs[0];
expect(afterAgentLog).toBeDefined();
expect(afterAgentLog?.hookCall.stdout).toContain('AfterAgent Fired');