web_probe_test: BeadsPageNoWorkspaceProbeTests assumes no shared bd workspace exists — false since Amendment A1 (#1126) nf-apw ← Beads

open priority 2 task unassigned

Twinned from https://github.com/cfsh/ninefold/issues/1138 by tools/beads/import_github.py's reconcile pass.

tools/web_frontend/web_probe_test.py's BeadsPageNoWorkspaceProbeTests.test_beads_page_renders_the_warning_banner_not_a_crash_or_blank_page asserts the beads dashboard page renders a "bd call(s) failed while loading this page" warning banner — presumably simulating a box with no bd workspace. Since design 011 Amendment A1 (#1122/#1126) landed, ~/nf/beads is a real, populated shared workspace on nf-dev-sg, so the page now renders real content successfully instead of hitting the warning path, and the test fails.

Reproduced on bare rebased main (7234ce0, no working-tree changes) — not caused by any in-flight chunk's edits:

``` python3 -m unittest web_frontend.web_probe_test.BeadsPageNoWorkspaceProbeTests.test_beads_page_renders_the_warning_banner_not_a_crash_or_blank_page ```

Whatever this test's own fixture/mocking relies on to simulate "no workspace" (an absent .beads/ dir, presumably) needs to force that condition explicitly now that a real one exists on the box by default — rather than relying on the ambient absence that Amendment A1 removed.

Filed unclaimed; not part of design 011 T6 (tools/pr/digest.py) or T5-amendment (tools/nflib/bd.py) — this is tools/web_frontend/'s (T4's) territory.

Dependencies

None.

Comments

No comments.

Add a comment