Problem Statement
The cli.py file is currently completely untested, despite being the primary user interface. As we add features like headless mode and programmatic APIs, we need to ensure the wizard flow remains stable and doesn't break.
Proposed Solution
- Set up a testing framework for CLI interactions (e.g., using
click.testing.CliRunner or Rich's own verification utilities).
- Create
tests/test_cli.py.
- Implement tests that simulate user input for profile setup, agent configuration, and session controls, verifying that the correct configuration objects are created and passed to the Session.
Alternatives Considered
Manual regression testing, which is time-consuming and unreliable as the codebase grows.
Priority
Low 🟢
Additional Context
Crucial for maintaining a premium, bug-free UX as the project complexity increases.
Problem Statement
The
cli.pyfile is currently completely untested, despite being the primary user interface. As we add features like headless mode and programmatic APIs, we need to ensure the wizard flow remains stable and doesn't break.Proposed Solution
click.testing.CliRunneror Rich's own verification utilities).tests/test_cli.py.Alternatives Considered
Manual regression testing, which is time-consuming and unreliable as the codebase grows.
Priority
Low 🟢
Additional Context
Crucial for maintaining a premium, bug-free UX as the project complexity increases.