Files
deepseek-harness/apps/web/tests/expected/fork-mid-turn/ui.expected.md
T
Tianyi Cui bc710ac726 test(web): await the settled branch action in fork snapshots
The merged performance/usage preference hides elapsed-time controls by
default. The release-only mid-turn fork scenario still waited for
"Ran for", so its ARIA check timed out despite a completed child turn.

Wait for the visible, enabled branch action belonging to live turn 2.
That action requires the settled turn tail and directly exercises the
fork affordance this scenario owns. Preserve the existing exact-cut,
synthetic closer, resume-header, completed-turn, and streaming checks.
Keep the default preference rather than enabling unrelated timing UI.

Refresh only the obsolete elapsed-time button in the ARIA expected
output. Session JSONL inputs, historical generations, snapshot versions,
and production code remain unchanged. The former wait failed locally;
the four-case scenario passes in ordinary comparison mode after this fix.
2026-09-18 19:02:10 +08:00

1.5 KiB

  • button "System prompt"
  • text: "Use the read tool twice in one assistant message: read a.txt and b.txt. Then reply with the single word DONE and stop. {{clock}}"
  • button "Copy"
  • button "Think The user wants me to read a.txt and b.txt, then reply with "DONE". Let me do both reads in parallel."
  • text: Failed
  • 'button "Read The history inherited by this branch records this tool call starting but does not include its result. The parent session may have completed it after the fork point. Decide whether to retry from the tool semantics: retry only if the operation is read-only or idempotent; if it may have side effects, first verify external state or ask the user. Do not retry blindly."'
  • text: Failed
  • 'button "Tool call The history inherited by this branch has no record of this tool call starting. The parent session may have executed it after the fork point. Decide whether to retry from the tool semantics: retry only if the operation is read-only or idempotent; if it may have side effects, first verify external state or ask the user. Do not retry blindly."'
  • button "System prompt"
  • text: FORK_BRANCH_USER Summarize what this branch knows about the reads. {{clock}}
  • button "Copy"
  • button "Thought for a while"
  • paragraph: FORK_BRANCH_FIRST this branch has no read results, so I would check what the parent completed before retrying. FORK_BRANCH_DONE.
  • button "Copy"
  • button "Good response"
  • button "Bad response"
  • button "Branch into a new conversation"
  • text: {{clock}}