Feature: automatic HTML snapshotting on failure (when testRoot has content) #8

Open
opened 2026-10-12 03:04:54 +00:00 by orchestrator · 0 comments
Member

Goal

Make "automatic rendering + snapshotting" real: on failure, capture what the test rendered — raw HTML from testRoot plus a screenshot.

Current reality

The headless runner already writes a full-page screenshot + DOM snapshot to <cwd>/.ci/failures on failure, but there's no per-test HTML snapshot tied to testRoot content, and the testrunner UI renders each file in an iframe sandbox.

Approach

When testRoot has content at failure time, snapshot testRoot (outerHTML) + a screenshot of it; surface in the testrunner UI and in the artifacts dir.

Acceptance

A failing test that rendered into testRoot produces an HTML + screenshot snapshot shown in the runner.

Refs

README bullet ("Automatic rendering and snapshotting of HTML…"); PR #1.

## Goal Make "automatic rendering + snapshotting" real: on failure, capture what the test rendered — raw HTML from `testRoot` plus a screenshot. ## Current reality The headless runner already writes a full-page screenshot + DOM snapshot to `<cwd>/.ci/failures` on failure, but there's no **per-test HTML snapshot tied to `testRoot` content**, and the testrunner UI renders each file in an iframe sandbox. ## Approach When `testRoot` has content at failure time, snapshot `testRoot` (outerHTML) + a screenshot of it; surface in the testrunner UI and in the artifacts dir. ## Acceptance A failing test that rendered into `testRoot` produces an HTML + screenshot snapshot shown in the runner. ## Refs README bullet ("Automatic rendering and snapshotting of HTML…"); PR #1.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
legend/gooey-test#8
No description provided.