test(scenarios): cover active view agent surface trajectory - #11610
Conversation
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…red the coverage classification gate (#11753) deterministic-active-view-agent-surface (added by #11610) declares its RESPONSE_HANDLER/ACTION_PLANNER fixtures via the harness stage1ResponseHandlerFixture builder imported directly from @elizaos/test-harness, which the strict-spec source scan didn't follow — so the scenario fit neither classification bucket and the 'every deterministic message scenario is classified' gate has been red on develop since that merge. - register it in STRICT_LLM_ROUTING_SCENARIOS (VIEWS, 2 message turns) - follow direct stage1ResponseHandlerFixture imports into the harness source for the fixture-literal checks, same as the registerStrictActionRouteFixtures re-export path 17/17 green (was 16/17). Co-authored-by: Shaw <shawgotbags@gmail.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
…ecognize fixture-template imports in the coverage guard #11610 added deterministic-active-view-agent-surface without classifying it in the deterministic-action-coverage guard, leaving the suite red on develop. Classify it as strict-routed (VIEWS, 2 message turns) and teach the guard's fixture-literal check to read the canonical @elizaos/test-harness template when a scenario builds fixtures from it directly (stage1ResponseHandlerFixture) rather than only via registerStrictActionRouteFixtures. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
LifeOps Benchmark —
|
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
1 participant
Refs #11355
Summary
Evidence
bun run --cwd packages/agent test -- src/runtime/conversation-compactor-runtime.test.tspassed after rebase: 1 file, 43 tests.SCENARIO_USE_LLM_PROXY=1 SCENARIO_LLM_PROXY_STRICT=1 bun --conditions eliza-source --tsconfig-override ../../tsconfig.json src/cli.ts run test/scenarios --scenario deterministic-active-view-agent-surface --lane pr-deterministic --report ../../.github/issue-evidence/11355-active-view-agent-surface/report.json --report-dir ../../.github/issue-evidence/11355-active-view-agent-surface/viewer --run-dir ../../.github/issue-evidence/11355-active-view-agent-surface/run --export-native ../../.github/issue-evidence/11355-active-view-agent-surface/native.jsonlpassed after rebase: 1 scenario, 0 failures..github/issue-evidence/11355-active-view-agent-surface/README.md.Evidence N/A
Notes
directory mismatchwarning after completion, but exits 0 and writes passing artifacts.