test: add frontend testing baseline#56
Draft
r0liveir wants to merge 1 commit into
Draft
Conversation
Add a Vitest and React Testing Library baseline for the current frontend implementation. Configure jsdom setup, shared render helpers, frontend test scripts, and a combined check script for future CI use. Cover the current stable seams with unit and component tests: Zustand session state updates, class merging, timer controls and countdown behavior, top bar topic rendering, delegation map quorum summaries, and motion sorting. Keep the first suite intentionally unit/component focused. E2E should come later with Playwright, starting with mocked route smoke tests and then a small real-backend Docker Compose smoke path once frontend-backend wiring is less hardcoded. Make npm run check the expected CI frontend gate: lint, TypeScript/Vite build, then Vitest. Adjust narrow lint/type blockers so that gate passes without introducing coverage thresholds yet. Co-authored-by: Codex <codex@openai.com>
r0liveir
requested review from
Extroias,
Le-frances13,
Rafael-Lombardi and
milena-depaula
Rafael-Lombardi
approved these changes
Jul 2, 2026
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
2 participants
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.
Add a Vitest and React Testing Library baseline for the current frontend implementation. Configure jsdom setup, shared render helpers, frontend test scripts, and a combined check script for future CI use.
Cover the current stable seams with unit and component tests: Zustand session state updates, class merging, timer controls and countdown behavior, top bar topic rendering, delegation map quorum summaries, and motion sorting.
Keep the first suite intentionally unit/component focused. E2E should come later with Playwright, starting with mocked route smoke tests and then a small real-backend Docker Compose smoke path once frontend-backend wiring is less hardcoded.
Make npm run check the expected CI frontend gate: lint, TypeScript/Vite build, then Vitest. Adjust narrow lint/type blockers so that gate passes without introducing coverage thresholds yet.