deer-flow/backend/tests/monocle/test_deerflow.py
Mohammed Ansari 867235389d
Add trace-based behavioral tests with Monocle Test Tools (#4025)
* Add Monocle behavioral test suite

Trace-based tests under tests/monocle/ asserting against the agent's Monocle execution traces: 4 offline tests load a recorded trace by file (with_trace_source), one per curated question, plus 1 live end-to-end test. Fluent structural asserts (agent, tools, input/output, token/duration budget); additive only, no app-code changes.

* Address review: restructure suite, move under backend/tests/monocle/

Responds to the review on this PR.

Behavioural coverage is now the live tests, not frozen fixtures. Keep one
offline test as a worked example of the fluent assertion API (loads a recorded
trace by file, no keys), and add two live tests that drive the agent end-to-end
through DeerFlowClient and assert on the trace the real run emits (web-research
and sandbox paths). The live tests skip without OPENAI_API_KEY or the app.

Other review fixes:
- Move the suite under backend/tests/monocle/ so backend pytest collects it.
- Split helpers into _helpers.py; conftest is fixtures-only (run_agent), with
  Monocle setup owned by the validator and .env load scoped to the live path.
- Resolve the model from config.yaml instead of hardcoding gpt-4o; skip the
  live tests when config.yaml is absent.
- Keep one trace with a stable name (web_research_ev_battery.json); drop the
  other three (removes ~2,200 lines of fixture blobs).
- Drop the flaky wall-clock duration bound on live runs.
- Keep monocle_test_tools in a standalone requirements.txt rather than the
  backend dev group: it hard-depends on the ML eval stack (torch, transformers,
  sentence-transformers, ~48 packages, +950 lines in uv.lock), so isolating it
  keeps the app's locked deps clean. importorskip skips the suite when absent.

* docs(monocle tests): explain the golden-trace workflow

Add a "How this is meant to be used" section: capture a run you are happy with
as a golden, labelled trace, turn it into assertions (the offline example), then
point the same assertions at the live agent so every later run has to reproduce
that behaviour.

* Address review: fix docstring pytest paths, state the suite is not run in CI

The docstring commands now use the backend/tests/monocle/ form (matching
the README, which also gains the backend-dir uv variant), and the README
states explicitly that the suite is skipped in CI and run on demand.

* Address review: document the committed trace, pin assertions context

- README: new section on the committed trace. It is a full, unmodified
  real-run recording (system prompt of the recording date + fetched web
  content, no credentials), committed whole so the offline example parses a
  genuine trace. The offline assertions are pinned to this trace and the
  monocle_apptrace 0.8.8 span shapes; re-record when prompt, tools, or model
  change.
- README: note that the monocle_trace_asserter fixture comes from
  monocle_test_tools' auto-registered pytest plugin (pytest11 entry point).
- test_deerflow.py: comment why web_fetch asserts min_count=2 rather than the
  recorded exact count of 5 (fetch counts vary run to run; keep it a floor).
- requirements.txt: loose pin python-dotenv>=1.0.

* Address review: make live tests explicit opt-in, drop OpenAI-only gate

Two execution-gating fixes from review:

- Live tests are now opt-in via MONOCLE_LIVE_TESTS=1 (default off). Previously
  the documented offline command collected the live tests too, and on a
  configured checkout (.env + config.yaml present) they would run for real,
  spending model tokens and hitting the network. Now the plain
  `pytest backend/tests/monocle/` run cannot go live regardless of what
  credentials are present; test_live_gate_defaults_off pins the gate.
- The run_agent fixture no longer requires OPENAI_API_KEY. config.yaml resolves
  the model, which may be any provider (Anthropic, Gemini, Volcengine, ...), so
  a hard-coded OpenAI gate skipped valid configurations and passed invalid
  ones. Credentials are validated by the configured model itself.

README and docstrings updated to match: offline command is offline by
construction, live is MONOCLE_LIVE_TESTS=1, credentials described as the
configured model's rather than OpenAI's.

Verified both modes: default run is 2 passed 2 skipped with no network; opted
in, all 4 pass with real end-to-end runs.

---------

Co-authored-by: Willem Jiang <willem.jiang@gmail.com>
2026-07-19 18:26:26 +08:00

114 lines
5.5 KiB
Python

"""Trace-based behavioural tests for DeerFlow, using Monocle Test Tools.
Two layers:
* One **offline example** (``test_assertion_api_example``) loads a recorded
trace from file and shows the full fluent vocabulary in one place. It needs no
keys and no network, but because it asserts against frozen JSON it guards the
trace format and the asserter wiring, not DeerFlow's behaviour. Treat it as the
worked example for writing your own assertions.
* Two **live tests** drive the agent end-to-end through ``run_agent`` and assert
on the trace the real run emits. These are the behavioural guards: a change
that alters routing, tool selection, or token cost is caught here. They are
**explicit opt-in** via ``MONOCLE_LIVE_TESTS=1`` (default off, so a plain run
never spends tokens or hits the network) and need the DeerFlow app plus the
configured model's credentials.
The whole module is skipped when ``monocle_test_tools`` is not installed (see the
``importorskip`` below), so a plain backend venv collects it without error.
pytest backend/tests/monocle/ # offline only
MONOCLE_LIVE_TESTS=1 pytest backend/tests/monocle/ # + live tests
See ``README.md`` for how to add your own.
"""
from pathlib import Path
import pytest
# monocle_test_tools hard-depends on the ML eval stack (torch, transformers,
# sentence-transformers), so it is a standalone requirements.txt install rather
# than a backend dependency. Skip the whole module when it is not present (e.g.
# a plain backend CI venv) instead of erroring at collection.
pytest.importorskip("monocle_test_tools", reason="pip install -r tests/monocle/requirements.txt")
from _helpers import live_tests_enabled # noqa: E402
from monocle_test_tools import TraceAssertion # noqa: E402
TRACES = Path(__file__).resolve().parent / "traces"
EXAMPLE_TRACE = str(TRACES / "web_research_ev_battery.json")
def test_live_gate_defaults_off(monkeypatch):
"""The live tests must be opt-in: gate closed by default, open only on the flag.
This is what keeps the plain ``pytest backend/tests/monocle/`` run incapable
of model calls, web requests, or sandbox writes, even on a checkout where
credentials and ``config.yaml`` are present.
"""
monkeypatch.delenv("MONOCLE_LIVE_TESTS", raising=False)
assert live_tests_enabled() is False
monkeypatch.setenv("MONOCLE_LIVE_TESTS", "1")
assert live_tests_enabled() is True
monkeypatch.setenv("MONOCLE_LIVE_TESTS", "0")
assert live_tests_enabled() is False
# --- Offline example: the full assertion vocabulary against a recorded trace ---
def test_assertion_api_example(monocle_trace_asserter: TraceAssertion):
"""Worked example: every fluent assertion this suite uses, in one place.
Loads a recorded web-research run (solid-state EV battery briefing) and
asserts which agent ran, what it was asked and produced, which tools it
called (and did not), and its token/duration budget. Copy this shape when
writing a behavioural test — then point it at a live run (see the live tests
below) so it actually guards behaviour.
"""
monocle_trace_asserter.with_trace_source("file", trace_path=EXAMPLE_TRACE)
monocle_trace_asserter.called_agent("LangGraph").contains_input("solid-state EV batteries")
monocle_trace_asserter.contains_any_output("solid-state", "battery", "batteries", "EV")
monocle_trace_asserter.called_tool("web_search", "LangGraph")
# The recorded run made 5 web_fetch calls, but the intent is "researched by
# fetching at least a couple of sources". Fetch counts genuinely vary run to
# run, so keep this a floor rather than tightening it to the exact count.
monocle_trace_asserter.called_tool("web_fetch", "LangGraph", min_count=2)
monocle_trace_asserter.does_not_call_tool("image_search", "LangGraph")
monocle_trace_asserter.under_token_limit(100_000)
monocle_trace_asserter.under_duration(60, span_type="workflow")
# --- Live: drive the agent and assert on the trace the real run emits ----------
# Output text varies run to run, so these assert structure + a lenient token
# budget only. Duration is omitted: a live run doing LLM calls and network I/O
# is inherently variable and would flake a wall-clock bound.
def test_web_research_live(monocle_trace_asserter: TraceAssertion, run_agent):
"""Live web-research path: the agent researches and uses ``web_search``."""
monocle_trace_asserter.validator.test_workflow(
run_agent,
{"test_input": ("Research the current state of solid-state EV batteries in 2025 and write a 1-page markdown briefing with sources.",)},
)
monocle_trace_asserter.called_agent("LangGraph").contains_input("solid-state EV batteries")
monocle_trace_asserter.contains_any_output("solid-state", "battery", "batteries", "EV")
monocle_trace_asserter.called_tool("web_search", "LangGraph")
monocle_trace_asserter.under_token_limit(200_000)
def test_sandbox_write_file_live(monocle_trace_asserter: TraceAssertion, run_agent):
"""Live sandbox path: the agent authors a file with ``write_file`` and stays off the web."""
monocle_trace_asserter.validator.test_workflow(
run_agent,
{"test_input": ("Write a Python script that prints the first 10 Fibonacci numbers and save it to a file named fib.py in the sandbox.",)},
)
monocle_trace_asserter.called_agent("LangGraph").contains_input("Fibonacci")
monocle_trace_asserter.called_tool("write_file")
monocle_trace_asserter.does_not_call_tool("web_search", "LangGraph")
monocle_trace_asserter.under_token_limit(100_000)