feat(tui): expand unit & integration test coverage #82
No reviewers
Labels
No labels
area:agents
area:ai
area:config
area:dashboard
area:design
area:design-review
area:devtools
area:entities
area:gallery
area:generate
area:image
area:infra
area:meta
area:model-browser
area:navigation
area:presets
area:security
area:sessions
area:settings
area:sharing
area:test
area:ux
area:webhook
area:workdir
type:bug
type:chore
type:meta
type:user-story
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
charles/loom!82
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "tui/tests-46"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Stacks on #81. Closes charles/loom#46.
Adds 4 cross-cutting tests covering the app→config→screens seams that weren't caught by the per-ticket unit tests:
AppAction::Navigaterouted via the unbounded channelcompute_layoutstays valid on a 40×10 minimum terminal with both sidebar and notification row visibleLoomTuiConfig::default() → build_key_map → App::with_configruns without the terminal113 total tests, all passing under
cargo test -p loom-tuiand green undercargo clippy -p loom-tui --all-targets -- -D warnings.Out of scope
TestBackendsnapshot-style integration tests for each screen. Those need either alib.rsor[lib]section on the crate so integration tests can see the private types, and are best done after the glue PR wiresPluginBridge/EventBusthroughAppCtx— otherwise most screens have nothing to snapshot but the stub placeholder