test: sequence the advisor mock with ordered handlers - #64
Merged
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe mid-turn advisor test replaces call-counter state with explicit ChangesMid-turn advisor test
Estimated code review effort: 1 (Trivial) | ~5 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
packages/agent-core/test/session/session-advisor.test.tsemitted twovitest(no-conditional-in-test)warnings from a call-counter mock that branched on whichrawGeneratecall it was handling.A reviewer raised this on #59 and I declined it incorrectly, citing an
oxlint --quietrun as evidence the rule did not fire. That flag suppresses warnings, so the evidence was an artifact of the command rather than a fact about the code. This is the follow-up.Approach
The three-call sequence is now expressed with ordered
mockImplementationOncehandlers plus a trailing default, so an unexpected fourth call falls through to the real implementation instead of returningundefined.No production code and no assertions changed.
Test plan
pnpm --filter @pythoughts/agent-core exec vitest run test/session/session-advisor.test.ts— all pass.npx oxlint packages/agent-core/test/session/session-advisor.test.ts(no--quiet) — 2 warnings before, 0 after.#deliverPending()call insession-advisor.tsfails the test withexpected 1 to be +0oncallsWhileActive.[skip changeset] — tests-only change under
packages/agent-core/test/. No production source is touched and nothing enters the CLI bundle, so per the repo's changeset rules there is no user-visible change to record.Summary by CodeRabbit