Skip to content

Native smoke test in CI (start daemon, run CLI, verify) #26

@mark-e-deyoung

Description

@mark-e-deyoung

Problem

All tests use FakeBackend — no test starts a real daemon process, connects a real CLI client, and verifies end-to-end behavior. Win32 API integration, pipe/TCP transport, auth handshake, and session lifecycle are never exercised by CI.

Proposed Solution

Add a smoke test step to ci.yml that:

  1. Starts build\Release\wininspectd.exe --headless
  2. Runs wininspect.exe health, capabilities, top, ps
  3. Verifies each returns valid JSON with expected fields
  4. Kills the daemon

This is a CI-hosted equivalent of scripts/smoke.sh without needing Docker/WineBot.

References

  • Testing audit item 2

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions