Add unit tests for frontend TypeScript modules#23
Merged
gauthierpiarrette merged 1 commit intomainfrom Feb 19, 2026
Merged
Conversation
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
1 participant
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.
What
Add unit tests for the frontend's pure TypeScript modules (ws.ts, ui.ts) and extract
describeReloadDiff from App.svelte into its own tested module. This brings frontend
test count from 29 to 60 with no new dependencies.
Why
The frontend had only one test file (schema.test.ts). The WebSocket client, reload
diffing logic, and clipboard utility had zero coverage. The .gitignore also had a
bug where
lib/was ignoring allfrontend/src/lib/files, preventing new filesfrom being tracked.
How to test
Run
cd frontend && npm testand verify all 60 tests pass.Checklist
uv run task checkpasses (lint + format + tests)