tui: unit & integration test suite #46

New issue

Closed

opened 2026-04-11 13:07:21 +00:00 by charles · 0 comments

charles commented

2026-04-11 13:07:21 +00:00

Owner

User story

As a developer, I want automated unit and integration tests for every screen and subsystem, so that regressions are caught before merging.

Acceptance criteria

Unit tests

Coverage targets (enforced as part of PR review, not hard CI gate):
- Image renderer protocol auto-detection logic (mock terminal capability matrix)
- Kitty chunking and base64 framing
- Half-block renderer deterministic output
- Event loop routing and overlay stack
- KeyCombo parsing / round-trip and chord handling
- Command palette action registry & fuzzy ranking
- Gallery grid column calculation
- LoomTuiConfig load/save round-trip
- Notification queue auto-dismiss with fake clock

Integration tests

One test per screen simulating a sequence of key events and asserting the resulting screen state (using a headless ratatui::backend::TestBackend)
Scenarios: Generate → run → queue; Gallery search/filter/sort; Entity create → inject; Presets apply; Settings edit + persist

CI

cargo test -p loom-tui runs and passes in the Forgejo qa job
cargo clippy -p loom-tui -- -D warnings runs and passes
loom-core tests remain passing (spec §9 no-regression requirement)

Out of scope

End-to-end tests against a live diffusion backend (impractical in CI)
Performance benchmarks

References

Spec §9 "Testing Requirements"

## User story As a developer, I want automated unit and integration tests for every screen and subsystem, so that regressions are caught before merging. ## Acceptance criteria ### Unit tests - [ ] Coverage targets (enforced as part of PR review, not hard CI gate): - Image renderer protocol auto-detection logic (mock terminal capability matrix) - Kitty chunking and base64 framing - Half-block renderer deterministic output - Event loop routing and overlay stack - `KeyCombo` parsing / round-trip and chord handling - Command palette action registry & fuzzy ranking - Gallery grid column calculation - `LoomTuiConfig` load/save round-trip - Notification queue auto-dismiss with fake clock ### Integration tests - [ ] One test per screen simulating a sequence of key events and asserting the resulting screen state (using a headless `ratatui::backend::TestBackend`) - [ ] Scenarios: Generate → run → queue; Gallery search/filter/sort; Entity create → inject; Presets apply; Settings edit + persist ### CI - [ ] `cargo test -p loom-tui` runs and passes in the Forgejo `qa` job - [ ] `cargo clippy -p loom-tui -- -D warnings` runs and passes - [ ] `loom-core` tests remain passing (spec §9 no-regression requirement) ## Out of scope - End-to-end tests against a live diffusion backend (impractical in CI) - Performance benchmarks ## References - Spec §9 "Testing Requirements"

charles added this to the loom-tui v0.1.0 milestone

2026-04-11 13:07:21 +00:00

charles added the

area:test

type:user-story

labels

2026-04-11 13:07:21 +00:00

charles referenced this issue

2026-04-11 13:07:50 +00:00

tui: tracking — loom-tui v0.1.0 roadmap & implementation order #47

charles referenced this issue

2026-04-11 15:22:44 +00:00