Skip to content

[P3.2] Test-trust cleanup: re-enable/fix stale-skipped suites and no-op assertions — batch fix #773

Description

@frankbria

Severity: low | Category: test-trust | Phase: P3.2

Problem

WebSocket subscription/integration + serve/dashboard suites are excluded/skipped with stale "server is a stub" reasons though the server ships; terminal-WS security tests assert only "an exception raised" (a full auth bypass would pass); proof-run tests are shape-only (hiding P1.1); a parallel test never asserts concurrency; a blocker test is timezone-dependent; a lifecycle assertion downgrades to skip on CLI failure.

Evidence

tests/ui/conftest.py:27 (WS excluded), tests/cli/test_serve_command.py:14, tests/ui/test_terminal_ws.py:43 (assert-only), tests/ui/test_proof_v2.py:306 (shape-only), tests/core/test_conductor.py:1138 (no concurrency assert), tests/blockers/test_blocker_expiration_minimal.py:68 (timezone), tests/lifecycle/test_cli_lifecycle.py:76 (skip-on-failure)

Acceptance criteria

Passing WS/serve suites re-collected; security tests assert exact close codes; proof-run tests assert real gate execution; parallel test asserts interleaving; blocker test uses UTC; lifecycle test fails (not skips) on Golden-Path command failure.

Dependencies

blocked by #728 ([P1.1])


Filed from the SaaS launch-readiness audit. Atomic: one developer, one session. Work order: strictly P0.1 → P3.12 (no forward dependencies).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions