Skip to content

Expand test coverage for daemon components #12

Description

@jeanmachuca

What

Only 1 test file exists (298 lines) for a ~1700 line daemon. Untested packages:

  • socket.go (Unix socket listener and protocol)
  • handlers.go (message dispatch)
  • mcp_lifecycle.go (MCP server spawn/discover/invoke/kill)
  • audit.go (hardware audit loop)
  • wide_client.go (HTTP client to inference engine)
  • config.go (configuration parsing)

Why

The daemon is the core runtime component. Low coverage means high risk of regressions in state management, message routing, and MCP lifecycle.

How

  • Add unit tests for each untested file
  • Add an integration test that: starts the daemon, connects via Unix socket, sends messages, and verifies responses

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesttestingTest coverage and quality

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions