Skip to content

test: automated integration tests for the CLI wizard #18

@rosspeili

Description

@rosspeili

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

  1. Set up a testing framework for CLI interactions (e.g., using click.testing.CliRunner or Rich's own verification utilities).
  2. Create tests/test_cli.py.
  3. 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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    cliImprovements to the interactive wizard or terminal output.enhancementNew feature or requesttestingNew tests or improvements to the testing suite.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions