Skip to content

Missing end-to-end tests for all commands #4

@micheledicosmo

Description

@micheledicosmo

Description

According to CLAUDE.md task rules, all new and changed functionalities must be tested automatically via end-to-end tests that run in non-interactive mode, but no e2e tests exist.

Current Issue

  • No end-to-end tests for any commands
  • Only basic test setup exists in tests directory
  • Cannot verify commands work in non-interactive mode
  • No automated testing of core functionality

Expected Behavior

According to CLAUDE.md:

  • All new and changed functionalities must be tested automatically via end-to-end tests
  • Tests must run the code in non-interactive mode
  • Full coverage of command functionality

Tasks

  • Set up e2e test framework (Jest with proper CLI testing utilities)
  • Create e2e tests for claim-key command
  • Create e2e tests for simple-organization-setup command
  • Create e2e tests for chat command
  • Create e2e tests for list command
  • Create e2e tests for conversations command
  • Create e2e tests for interactive mode flows
  • Add test utilities for mocking API responses
  • Set up CI to run e2e tests
  • Add test data fixtures
  • Ensure all tests run in non-interactive mode with --non-interactive flag

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions