deepseek-harness/apps/web/tests/snapshots/live-interactions/retry.expected.md at f3a4833dbf2be4ebb18831dbae0bfc2c299a20e7

mirror of https://github.com/deepseek-ai/deepseek-harness synced 2026-08-15 21:04:50 +00:00

Files

Tianyi Cui ea1d8d06b3 test(web): pin every scenario end-state with an aria golden

Every spec now commits at least one golden and the interactive ones one
per distinct end-state (nine new .expected.md):

- live-interactions: cancel.expected.md (frozen partial + 已停止 marker),
  error-auth.expected.md (the prompt bubble alone — the committed artifact
  of the web-error-surface gap, the diff that flips when error rendering
  lands), retry.expected.md (indistinguishable from a clean completion —
  retries are deliberately invisible in the transcript).
- question-composer: answered.expected.md (the question resolved into its
  tool round trip plus the final reply, takeover gone) beside the existing
  waiting-state golden.
- steering: mid-steer.expected.md pins the accepted-but-INVISIBLE state
  (the loop drains steering only at the step boundary, so no interjection
  bubble exists while the question still blocks — if the client ever
  renders pending steers eagerly, this golden flips first) and
  settled.expected.md the badged bubble plus obeying reply.
- navigation-panes: waterfall.expected.md and details-open.expected.md
  (tool-name header, Input args, Output result) beside the trajectory one.
- lifecycle-chrome: reloaded.expected.md — rendering the same settled
  transcript from persistence alone IS the recovery claim.

Fixture inventories extended to the new closed sets; the Agent Note's
expected-outputs policy updated in both languages (per-end-state goldens
for interactive scenarios), pairing re-recorded.

2026-07-26 12:45:44 +08:00

1.3 KiB

Raw Blame History

banner:
- navigation "Session hierarchy":
  - button "Reply with a one-sentence description" [disabled]
  - text: · 1 turns
- tablist:
  - tab "Chat" [selected]
  - tab "Trajectory"
  - tab "Waterfall"
text: Reply with a one-sentence description of event sourcing, then stop.
button "Think The user is asking for a one-sentence description of event sourcing. This is a straightforward knowledge question that doesn't require any skill loading or tool calls.":
- img
- text: Think The user is asking for a one-sentence description of event sourcing. This is a straightforward knowledge question that doesn't require any skill loading or tool calls.
paragraph: Event sourcing is a pattern where all changes to an application's state are stored as an immutable, append-only sequence of events, rather than persisting only the current state, enabling full auditability, temporal queries, and event-driven architectures.
text: cache hit 99% · 7,869 tokens · 1 turns · 1 steps
textbox "Message the agent"
button "Add attachment":
- img
combobox "Plan mode":
- option "Plan" [selected]
- option "Agent"
combobox "Access mode":
- option "Read-only" [selected]
- option "Read-write"
combobox "Model":
- option "DeepSeek-V4-Pro High" [selected]
- option "DeepSeek-V4-Pro"
button "Send message" [disabled]

1.3 KiB Raw Blame History

1.3 KiB

Raw Blame History