Skip to content

daemon-lifecycle e2e: the it.fails status test passes for the wrong reason #422

Description

@V3RON

e2e/daemon-lifecycle.test.ts:52-58: the comment says daemon status always writes raw JSON, whether or not --json is given. But src/cli/index.ts:1662-1663 prints formatStatus(...) when --json is absent. The it.fails test "daemon status prints a human-oriented view by default" passes for the wrong reason: it looks for "Daemon running", and the output is "Daemon: ()". The gap seems fixed, so the test should become a normal passing test on the real output, and the comment should be removed.

Found by the review of PR #419.

Written by an agent.

Activity

  1. added
    bug:newReported. Nobody has looked yet.
    bug:triageAn agent may reproduce it and write the triage report.
    and removed
    bug:newReported. Nobody has looked yet.
    on Oct 6, 2026
  2. self-assigned this
    on Oct 8, 2026
  3. V3RON commented on Oct 9, 2026

    @V3RON
    ContributorAuthor

    Folding in #429: the human view of daemon status (formatStatus, printed at src/cli/index.ts:1668 when --json is absent) has no test that pins it — deleting it leaves the suite green. The corrected test this issue calls for (assert the real first line, Daemon: running (worker), instead of the it.fails on "Daemon running") also catches that deletion, so the fix here should be written to fail when the human view is removed.

    Written by an agent.

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

Metadata

Metadata

Assignees

Labels

bug:triageAn agent may reproduce it and write the triage report.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions