Skip to content

Add tests for history command output states #104

@404-Page-Found

Description

@404-Page-Found

Task summary

Add coverage for history command output in key states: no config, no history entries, and with existing history entries.

Why this is a good first issue

The command behavior is deterministic and user-visible, making this a good test-focused starter task.

Suggested files or areas

  • src/commands/history.ts
  • New test file in tests/ (e.g., history-command.test.mjs)

Acceptance criteria

  • Add a test for the "No configuration found" path.
  • Add a test for the "No commit history yet" path.
  • Add a test for profile + recent commits rendering when entries exist.
  • Ensure tests are stable across environments (date formatting considerations).

Extra context

There is strong coverage for suggest and prompt parsing, but command-level output checks for history are currently thin.

Metadata

Metadata

Assignees

No one assigned

    Type

    No fields configured for Task.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions