mirror of
https://github.com/ksyasuda/SubMiner.git
synced 2026-02-27 18:22:41 -08:00
sudacode
10b94ce889
Collapse src/config/resolve.ts into an orchestrated pipeline over domain modules, wire launcher regression coverage into test scripts, and sync backlog/subagent tracking artifacts for completed TASK-74/TASK-96/TASK-98 follow-up planning.
1.5 KiB
1.5 KiB
id, title, status, assignee, created_date, updated_date, labels, dependencies, priority
| id | title | status | assignee | created_date | updated_date | labels | dependencies | priority | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| TASK-74 | Add launcher regression tests for config discovery and command branching | Done | 2026-02-18 11:35 | 2026-02-21 20:21 |
|
|
medium |
Description
Launcher currently has no direct test coverage for config discovery behavior and key command branching paths. This leaves wrapper flows vulnerable to regressions when refactoring config or process-control logic.
Action Steps
- Add launcher-focused test harness (unit/integration-lite) under existing project test runner.
- Cover config discovery matrix:
XDG_CONFIG_HOMEoverridesSubMinervssubminer.jsoncvs.jsonpreference
- Cover CLI branch behavior (
doctor,config path/show,mpv status/socket, jellyfin command routing). - Mock fs/process/spawn boundaries to keep tests deterministic.
- Wire tests into existing
test:core:distor dedicated launcher test command.
Acceptance Criteria
- #1 Launcher config discovery paths are regression-tested
- #2 Core launcher command branches are regression-tested
- #3 Tests run in CI/local test gate without external process dependencies
Definition of Done
- #1 Launcher tests included in standard test workflow
- #2 Documented how to run launcher tests locally