Files
archie/ui/test/main-routing.test.js
T
sam 7414713d61 feat(webui): add the per-run task detail page
A per-task page at #/tasks/{id} with tabs for the attempt's stages and log, changed
files, configuration and a raw debug view. Reachable from the task list, deep
linkable via ?tab= and ?attempt=, and reload safe. Existing URLs (#/tasks?task=N
and #/tasks?status=...) are unchanged.

- A stage rail per attempt: name, duration, terminal status and error text, with
  unattributed events surfaced and the agent's own verdict shown separately.
- No pass/fail badge and no exit code anywhere: the backend has neither, and a stage
  that returned nil after producing a poor diff is a success. Status word, duration
  and error text are shown instead.
- The log pane filters by attempt, stage and level, states the coverage caveat for
  stage filters (agent and tool output records no stage), and keeps the three read
  outcomes distinct: no log reader in this deployment, no file for this attempt, and
  no entries matching the filter.
- Retry is labelled as a new run and its confirm says the previous attempt's commits
  are discarded, because it hard-resets the branch onto the base.
- An absent capture reads "not captured for this run" rather than implying nothing
  changed, and no elapsed-run figure is shown since only per-stage durations exist.
- The events cache is invalidated on retry (it previously kept the ended attempt's
  events) and the log cache is keyed by attempt, so two attempts cannot be conflated.
- ui/dist is rebuilt and committed: the gate runs the node tests but never rebuilds
  the bundle, so a stale one would otherwise ship behind a green gate.
- docs/prds/task-run-detail.md records the surface and its limits, and
  docs/architecture/observability.md describes it alongside the read endpoints.

Both new vocabularies are pinned by tests on each side (config schema, change
statuses) so a one-sided rename fails a test instead of silently degrading the page.
2026-09-18 18:33:03 +10:00

94 lines
4.0 KiB
JavaScript

import { test } from "node:test";
import assert from "node:assert/strict";
import { waitFor } from "@testing-library/preact";
// The router as the browser actually uses it: main.jsx is imported once (it
// starts on import), and every step below navigates by changing the hash and
// waiting for the app to follow. This is the only place the wiring between the
// route table, the matcher and the navigation highlight is exercised -- the
// matcher's own unit tests cannot see whether `show` hands the nav the section
// path or the detail path.
//
// archied is absent on purpose: every request fails, which is itself a state
// these pages must render honestly rather than blankly.
globalThis.fetch = async () => {
throw new Error("no daemon in this test");
};
// jsdom has no EventSource, and the dashboard subscribes to the daemon's event
// stream the moment it mounts. An inert stand-in keeps this test about routing
// rather than about the stream.
class InertEventSource {
close() {}
}
globalThis.EventSource = InertEventSource;
function navCurrent(path) {
return document.querySelector(`a.nav-item[href="#${path}"]`)?.getAttribute("aria-current");
}
function title() {
return document.querySelector(".page-title")?.textContent;
}
async function navigate(hash) {
location.hash = hash;
// jsdom queues its own hashchange for the assignment; waitFor lets it land.
await new Promise((resolve) => setTimeout(resolve, 0));
}
test("the app routes deep links and keeps the navigation highlight honest", async (t) => {
document.body.innerHTML = '<div id="app"></div>';
location.hash = "#/tasks/42";
await import("../src/main.jsx");
await waitFor(() => assert.equal(title(), "Task #42"));
await t.test("a per-task route renders the run page and keeps Tasks current", () => {
assert.equal(title(), "Task #42");
assert.ok(document.querySelector(".run-restart"), "the run controls should render");
assert.equal(
navCurrent("/tasks"),
"page",
"W9: a detail route must hand the nav its section, or Tasks silently loses aria-current",
);
});
await t.test("the tasks list route still works", async () => {
await navigate("#/tasks");
await waitFor(() => assert.equal(title(), "Tasks"));
assert.equal(navCurrent("/tasks"), "page");
assert.equal(document.querySelector(".tab-bar"), null, "the run page is no longer mounted");
});
// W10: #/tasks?task=N and #/tasks?status=... are pinned deep links. The steps
// below enter this route from the run page on purpose: the query string is an
// entry state, so a navigation that only changes the query of the page already
// mounted keeps the operator's own filter selection instead.
await t.test("a tab and attempt in the query string open that panel", async () => {
await navigate("#/tasks/7?tab=log&attempt=1");
await waitFor(() => assert.equal(title(), "Task #7"));
const selected = [...document.querySelectorAll('[role="tab"]')].find(
(tab) => tab.getAttribute("aria-selected") === "true",
);
assert.equal(selected.textContent, "Log");
// The panels read one attempt, and this deployment answered no reads at
// all -- so the panel says that rather than claiming there is no attempt.
await waitFor(() => assert.match(document.body.textContent, /Could not load this task's attempts/));
assert.equal(navCurrent("/tasks"), "page");
});
await t.test("the existing task deep links keep working", async () => {
await navigate("#/tasks?task=7&status=needs_you");
await waitFor(() => assert.equal(title(), "Tasks"));
assert.equal(document.querySelector(".task-filter").value, "needs_you");
assert.equal(navCurrent("/tasks"), "page");
});
await t.test("an unmatched path falls back to the dashboard", async () => {
await navigate("#/nope/deep");
await waitFor(() => assert.ok(document.querySelector(".hero-title"), "the dashboard should render"));
assert.equal(document.querySelector(".tab-bar"), null);
assert.equal(navCurrent("/"), "page");
});
});