deer-flow/backend/tests/_replay_fixture.py
Xinmin Zeng 88759015e4
test(e2e): deterministic record/replay front-back contract verification (#3365)
* test(e2e): record/replay front-back contract verification

Guards the front-back contract with a deterministic, key-free record/replay
harness (mirrors open-design's golden-trace approach):

- ReplayChatModel (tests/replay_provider.py): replays recorded LLM turns by a
  normalized hash of the model input. Strips <system-reminder>/date/uuid/tmp-path
  so one fixture replays across days and from both the browser and direct-POST
  paths; a miss raises loudly (no silent divergence).
- Recording is record-through-browser (scripts/record_gateway.py +
  build_fixture_from_jsonl.py + frontend/tests/e2e-record): a real run is driven
  through the real frontend so captured inputs match exactly what the browser
  sends; fixtures contain no API key.
- Layer 1 — backend golden (tests/test_replay_golden.py): replay through the real
  gateway, assert the SSE event sequence == committed golden.
- Layer 2 — full-stack render (frontend/tests/e2e-real-backend): real Next.js +
  real gateway (replay model) + Chromium; assert the replayed auto-title and
  follow-up suggestions render. DOM assertions are the gate; visual regression is
  a local dev gate (CI uploads the render as an artifact).
- CI (.github/workflows/replay-e2e.yml): both layers, triggered on EITHER side of
  the contract (frontend/** or backend gateway/harness/fixtures).

* test(e2e): multi-run render-order cross-stack scenario (#3352)

Guards the dangerous front-back class where a backend ordering change
silently breaks a frontend assumption while both sides' unit tests stay
green. Reproduces issue #3352: backend list_by_thread returns runs
newest-first (#2932) and the frontend prepended per-run pages, inverting
chronological order once the checkpoint no longer held the older messages.

- tests/seed_runs_router.py: test-only seeder, mounted on the replay
  gateway only when DEERFLOW_ENABLE_TEST_SEED=1 (never in the production
  app). Seeds a thread with >=2 runs + per-run message events and no
  checkpoint -- the #3352 precondition -- so the frontend per-run reload
  path is the sole source of truth and the prepend inversion is observable.
- frontend/tests/e2e-real-backend/multi-run-order.spec.ts: drives the real
  frontend against the real gateway, asserts the first run renders above
  the second. Reverting the #3354 fix turns it red.
- replay-e2e.yml: trigger on the new replay test-infra paths.
- docs: REPLAY_E2E.md cross-stack scenario section.

* test(e2e): address Copilot review on the replay harness

- Fix stale recorder references (scripts/record_traces.py ->
  scripts/record_gateway.py + scripts/build_fixture_from_jsonl.py) in
  replay_provider.py, test_replay_golden.py, _replay_fixture.py.
- MODE_CONTEXT['ultra']: thinking_enabled False -> True, mirroring the
  frontend's `context.mode !== 'flash'` (hooks.ts). It did not affect the
  hashed input (Layer 1 golden still green), but the table now matches the
  real frontend context it claims to mirror.
- replay_provider.py docstring: stop claiming memory is recorded-enabled;
  the replay config disables memory/summarization for determinism (title
  stays, as an in-graph deterministic call).
- record_gateway.py / run_replay_gateway.py: override DEER_FLOW_HOME instead
  of setdefault, so an outer value can't leak into the hermetic harness.
- record_gateway.py: clear error when DEERFLOW_RECORD_OUT is unset (was a
  bare KeyError).
- playwright.record.config.ts: forward OPENAI_*/DEERFLOW_RECORD_OUT only when
  set, so the gateway raises a clear 'missing env' error instead of getting ''.

* test(e2e): address Copilot review round 2

- seed_runs_router.py: constrain SeedMessage.role to Literal['human','ai']
  so a bad value is a clean 422 at the boundary instead of a 500
  (KeyError on _EVENT_TYPE).
- record-write-read-file.spec.ts: waitForCaptureStable now throws on
  timeout instead of returning the last count, so a truncated/partial
  recording can't pass silently.
- real-backend-render.spec.ts: guard the suggestions JSON.parse; a
  bracket-prefixed non-JSON turn falls back to '' so the existing
  not.toBe('') assertion fails clearly instead of a generic parse throw.
2026-06-08 12:35:03 +08:00

164 lines
6.0 KiB
Python

"""Shared config + gateway-drive helpers for the record/replay e2e.
Record (``scripts/record_gateway.py`` + ``scripts/build_fixture_from_jsonl.py``)
and replay (``tests/test_replay_golden.py``)
MUST drive the gateway through an identical, prompt-affecting config — otherwise
the system prompt differs and the recorded input hashes never match on replay.
Centralising the config builder + drive loop here makes that identity hold by
construction; only the ``models[].use`` block differs (real model vs
``ReplayChatModel``).
"""
from __future__ import annotations
import json
import uuid
from pathlib import Path
# mode -> (thinking_enabled, is_plan_mode, subagent_enabled). Mirrors the
# frontend mapping in core/threads/hooks.ts.
MODE_CONTEXT: dict[str, tuple[bool, bool, bool]] = {
"flash": (False, False, False),
"thinking": (True, False, False),
"pro": (True, True, False),
# thinking_enabled mirrors the frontend `context.mode !== "flash"` (hooks.ts),
# so ultra is thinking-enabled too.
"ultra": (True, True, True),
}
# The replay model block: same model NAME as recording (so nothing in the prompt
# shifts), only ``use`` swapped to the deterministic replay provider.
REPLAY_MODEL_BLOCK = """\
- name: scenario-model
display_name: Scenario Model
use: replay_provider:ReplayChatModel
model: replay"""
def real_model_block(model: str) -> str:
return f"""\
- name: scenario-model
display_name: Scenario Model
use: langchain_openai:ChatOpenAI
model: {model}
api_key: $OPENAI_API_KEY
base_url: $OPENAI_API_BASE"""
def build_config_yaml(*, model_block: str, home: Path) -> str:
"""Full gateway config. Only ``model_block`` varies between record/replay.
Everything that shapes the system prompt is pinned so record, replay, and CI
produce byte-identical prompts regardless of the machine:
- sandbox / tool_groups / tools — fixed here
- skills — pointed at an empty ``<home>/skills`` so filesystem skills (incl.
gitignored custom skills present only on a dev box) never leak into the
prompt. Pair with an empty ``extensions_config.json`` (no MCP) via
:func:`prepare_hermetic_extras`.
- memory / summarization — disabled (background, non-deterministic timing)
"""
return f"""\
log_level: warning
models:
{model_block}
sandbox:
use: deerflow.sandbox.local:LocalSandboxProvider
skills:
path: {home / "skills"}
container_path: /mnt/skills
tool_groups:
- name: file:read
- name: file:write
tools:
- name: ls
group: file:read
use: deerflow.sandbox.tools:ls_tool
- name: read_file
group: file:read
use: deerflow.sandbox.tools:read_file_tool
- name: write_file
group: file:write
use: deerflow.sandbox.tools:write_file_tool
# Memory + summarization make background / debounced model calls whose timing is
# non-deterministic; disable them so record and replay see the same model-call
# set. (Title stays — it is an in-graph, deterministic call we record.)
memory:
enabled: false
injection_enabled: false
summarization:
enabled: false
agents_api:
enabled: true
database:
backend: sqlite
sqlite_dir: {home / "db"}
"""
def prepare_hermetic_extras(home: Path) -> Path:
"""Create the empty skills tree + an empty extensions_config.json so the
system prompt has no environment-dependent skills/MCP content.
Returns the extensions-config path; the caller must point
``DEER_FLOW_EXTENSIONS_CONFIG_PATH`` at it. Call before starting the gateway.
"""
(home / "skills" / "public").mkdir(parents=True, exist_ok=True)
(home / "skills" / "custom").mkdir(parents=True, exist_ok=True)
extensions = home / "extensions_config.json"
extensions.write_text(json.dumps({"mcpServers": {}, "skills": {}}), encoding="utf-8")
return extensions
def sse_event_shapes(resp) -> list[dict]:
"""Reduce an SSE stream to (event name, sorted top-level data keys).
Snapshots the *shape* of the stream, not volatile values, so the golden is
stable across runs while still catching event-sequence / payload-shape drift.
"""
events: list[dict] = []
current: str | None = None
for line in resp.iter_lines():
if line.startswith("event:"):
current = line[len("event:") :].strip()
elif line.startswith("data:"):
raw = line[len("data:") :].strip()
try:
data = json.loads(raw) if raw else {}
except json.JSONDecodeError:
data = {"_raw": raw[:200]}
events.append({"event": current, "keys": sorted(data.keys()) if isinstance(data, dict) else None})
return events
def drive_gateway(app, *, prompt: str, context: dict) -> list[dict]:
"""Register -> create thread -> POST /runs/stream; return SSE event shapes.
This is the exact wire path the React frontend uses (LangGraph SDK), driven
in-process via Starlette's TestClient with the real auth flow.
"""
from starlette.testclient import TestClient
with TestClient(app) as client:
reg = client.post(
"/api/v1/auth/register",
json={"email": f"e2e-{uuid.uuid4().hex[:8]}@example.com", "password": "very-strong-password-123"},
)
assert reg.status_code == 201, reg.text
csrf = client.cookies.get("csrf_token")
assert csrf, "register must set csrf_token cookie"
thread_id = str(uuid.uuid4())
created = client.post("/api/threads", json={"thread_id": thread_id, "metadata": {}}, headers={"X-CSRF-Token": csrf})
assert created.status_code == 200, created.text
body = {
"assistant_id": "lead_agent",
"input": {"messages": [{"role": "user", "content": prompt}]},
"config": {"recursion_limit": 50},
"context": context,
"stream_mode": ["values"],
}
with client.stream("POST", f"/api/threads/{thread_id}/runs/stream", json=body, headers={"X-CSRF-Token": csrf}) as resp:
assert resp.status_code == 200, resp.read().decode()
return sse_event_shapes(resp)