A JUnit XML test report in a repository opens as its results: pass, fail and skip counts, then each failing case with its message #11076

A JUnit XML report now opens as its results instead of raw XML. bun test on the 28 related files, bun x tsc --noEmit, scripts/gate.ts and scripts/design-lint.ts all pass. I did not run the full suite: scripts/fast.ts called the diff too broad to name tests (1,577 files), so I ran the render, kinds and blob-page suites instead. I also did not try it on the running app.

What changed

• Renderer: src/web/render/junit.ts follows the shape of sarif.ts.

- The top line gives tests, failures, errors, skipped and time. - Each suite lists its failing and erroring cases first, with the name, class, time and message. The body shows its first 40 lines in a <pre>, with a note of how many more are in the raw file. - Passing and skipped cases sit in one folded <details> per suite. - Every string is escaped.

• XML reader: it lives in the same file, has no dependency and makes one forward pass over the text.

- It expands only lt, gt, amp, quot and apos, plus numeric character references. Any other &name; stays as written. - Any DOCTYPE or declaration is refused, so a DOCTYPE bomb is never expanded. Unbalanced tags, nesting past 100 levels and more than 500,000 elements are refused too. The page then shows the source with the reason.

• Caps: at most 2,000 cases are drawn, failing ones first across all suites, and the page says how many were left out. The size cap is 5 MB.
• Registry: kinds.ts adds a junit kind, and renderers.ts maps it to the renderer. A file is JUnit if it is named .junit.xml or TEST-.xml, or if it is an .xml whose first element (after the prolog and comments) is <testsuites> or <testsuite>. Any other .xml, such as a pom.xml, still opens as source.
• Docs: docs/design/areas/render.md has a short section on the new view.
• Tests: test/render-junit.test.ts covers a mixed report, malformed files, a DOCTYPE bomb, the entity rules, the cap, the depth and element bounds, escaping of a <script>, and the registry.

Left out

• The terminal workspace does not draw JUnit; .xml still shows as source there.
• Suite-level properties, system-out and system-err are not shown.
• A report over 5 MB stays as source.
• A JUnit-looking file outside the first 4 KB of its own head is only found by name, not by its root element.

Try it: open a TEST-.xml or .junit.xml file on the preview and read its failures. Run bun test test/render-junit.test.ts.

🤖 Generated with Claude Code

Closes #11072

A JUnit XML report now opens as its results instead of raw XML. bun test on the 28 related files, bun x tsc --noEmit, scripts/gate.ts and scripts/design-lint.ts all pass. I did not run the full suite: scripts/fast.ts called the diff too broad to name tests (1,577 files), so I ran the render, kinds and blob-page suites instead. I also did not try it on the running app.

What changed

• Renderer: src/web/render/junit.ts follows the shape of sarif.ts.

- The top line gives tests, failures, errors, skipped and time. - Each suite lists its failing and erroring cases first, with the name, class, time and message. The body shows its first 40 lines in a <pre>, with a note of how many more are in the raw file. - Passing and skipped cases sit in one folded <details> per suite. - Every string is escaped.

• XML reader: it lives in the same file, has no dependency and makes one forward pass over the text.

- It expands only lt, gt, amp, quot and apos, plus numeric character references. Any other &name; stays as written. - Any DOCTYPE or declaration is refused, so a DOCTYPE bomb is never expanded. Unbalanced tags, nesting past 100 levels and more than 500,000 elements are refused too. The page then shows the source with the reason.

• Caps: at most 2,000 cases are drawn, failing ones first across all suites, and the page says how many were left out. The size cap is 5 MB.
• Registry: kinds.ts adds a junit kind, and renderers.ts maps it to the renderer. A file is JUnit if it is named .junit.xml or TEST-.xml, or if it is an .xml whose first element (after the prolog and comments) is <testsuites> or <testsuite>. Any other .xml, such as a pom.xml, still opens as source.
• Docs: docs/design/areas/render.md has a short section on the new view.
• Tests: test/render-junit.test.ts covers a mixed report, malformed files, a DOCTYPE bomb, the entity rules, the cap, the depth and element bounds, escaping of a <script>, and the registry.

Left out

• The terminal workspace does not draw JUnit; .xml still shows as source there.
• Suite-level properties, system-out and system-err are not shown.
• A report over 5 MB stays as source.
• A JUnit-looking file outside the first 4 KB of its own head is only found by name, not by its root element.

Try it: open a TEST-.xml or .junit.xml file on the preview and read its failures. Run bun test test/render-junit.test.ts.

🤖 Generated with Claude Code

A repository file named TEST-.xml or .junit.xml now opens as test results: totals, failing cases with their messages, and passing cases folded. This push fixes two of the three failures from the last check. The third, in test/attention.test.ts, passes here but I haven't explained it.

• Fixed: the DOCTYPE-bomb test in test/render-junit.test.ts asserted that the refusal took under 50 ms. Two repo guards reject tight clock bounds in tests, and that line tripped both. I removed the timing check. The test still asserts that the DOCTYPE is refused and not expanded, and bun test test/render-junit.test.ts passes (10 tests); tsc is clean.
• Not fixed: "each page stays inside its first-view budget" failed in shard 57 of the check. It passes locally (2 pass, 0 fail), and the check log didn't say which page or width went over. This change only touches the file-kind and renderer code under src/web/render/, which no main page draws. That makes a flaky failure in an unrelated page the likeliest cause. If it fails again, the log's over-budget lines will say which page and metric.

I did not run scripts/design-lint.ts or scripts/gate.ts this round.

This update addresses all of juniper's points. A JUnit file now opens in the terminal workspace too, and on the page the failing cases are table rows.

What changed

• Terminal door:

- A .junit.xml, TEST-.xml, or .xml with a <testsuite>/<testsuites> root opens as a table in src/tui/screens/workspace.ts (isJunitPath, junitTable). - It uses the web's parseJunit and file-kind rule, so the two can't disagree. - The table is headed by a totals row ("N tests", "1 of 2 tests fail · 1 skipped"), then one row per failing or erroring case with its message, capped at CASE_CAP. - The status line reads "N failing cases", and s shows the source. - A file that isn't a report opens as source, with the reason "not drawn as test results: …". - Two new tests in test/tui-workspace.test.ts cover the report and the fallback.

• Principle 7: each suite's failing cases are now one .table with data-dense, with columns case, result and type, message, time. The stack-trace pre for each case follows the table. The section and h4 boxes are gone.
• Principle 1: the page opens with "This is a test report: 2 of 40 tests fail." (or "all N tests pass") before the tally. The new leadSentence is exported.
• Tests: a body over 8000 characters is cut, and failing cases are table rows rather than boxes. The old mixed-report and cap tests were updated to match the new markup.
• Docs: added docs/features/file-junit.md, and docs/design/areas/render.md now points to it.

Left out

• The terminal doesn't show a case's stack trace or passing cases; Source has them.
• In the terminal the lead line is the short "N of M tests fail", not the full sentence, because the table column truncated the longer one.

Checks tsc --noEmit, scripts/gate.ts, scripts/design-lint.ts, and the junit render, TUI workspace and renderer fuzz tests all pass locally. I did not look at a JUnit file in the preview.

I pushed a commit that clears the "pipeline first" gate rule. I did not change the pipeline.

The rule fires because the pull adds docs/features/file-junit.md without touching scripts/, src/flow/, src/nightly/, src/checks/ or forge.json. I wrote that doc because juniper required it, as file-sarif.md exists for SARIF. The commit message now carries the Direction: line the gate accepts, saying so. Nothing else in the pull changed.

bun scripts/gate.ts printed nothing and showed no error locally. I did not re-run the type check or tests, since no code changed since the last green run. The forge's check on this push will confirm.

If a person would rather this pull ship a pipeline change instead, that is their call.