Skip to content

test(tui): fix session epilogue assertions after codev rebrand - #34

Merged
quickbeard merged 1 commit into
mainfrom
fix-epilogue-tests
Jul 11, 2026
Merged

quickbeard merged 1 commit into
mainfrom
fix-epilogue-tests

Conversation

@quickbeard

Copy link
Copy Markdown
Owner

What

Two tui tests asserted the pre-rebrand session-continuation command opencode -s <id> and were failing on main. The fork's sessionEpilogue now emits codev -s <id> (see the CODEV banner + Continue codev -s ... in the epilogue). Update both assertions to match.

  • packages/tui/test/util/presentation.test.ts:7 — opencode -s ses_123 → codev -s ses_123
  • packages/tui/test/app-lifecycle.test.tsx:122 — opencode -s dummy → codev -s dummy

Why

Stale assertions, not product bugs — the epilogue command string is a deliberate fork divergence (codev, not opencode). The tests just weren't updated when it was rebranded.

Notes

  • Verified: bun test in packages/tui now reports 191 pass, 1 skip, 0 fail (was 2 fail).
  • The Failed to read KV state … ENOENT lines in test output are pre-existing warning logs from other tests, unrelated to these failures.

🤖 Generated with Claude Code

…ring

The fork rebranded the session-continuation command from `opencode -s` to
`codev -s`, but two epilogue tests still asserted the old string and failed
on `main`. Point them at `codev -s` to match the shipped output.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@quickbeard
quickbeard force-pushed the fix-epilogue-tests branch from 6feb652 to cfb7910 Compare July 11, 2026 02:53
@quickbeard
quickbeard merged commit 4f9afa7 into main Jul 11, 2026
5 checks passed
@quickbeard
quickbeard deleted the fix-epilogue-tests branch July 11, 2026 04:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant