DreamLake

Status

Live verification surface for the Lakeshore stack. The JSON behind this page is produced by lakeshore-examples/test_runner.py and served from docs/public/test-results.json. Doc pages can also embed <TestStatus suite="..." /> inline to surface "are this feature's tests green right now?" next to the section it documents.

Unit-test suites

These are the leaf-node verifications — fast, deterministic, no infra needed. Click a suite name to jump to its concept docs.

Loading test results…

Example smoke runs

Examples from lakeshore-examples/. Most require a running control plane or external infra and are skipped by default; pass --enable-cp to attempt them against a live control plane.

Loading test results…

How to refresh

Run from the workspace checkout that holds lakeshore-examples/:

bash
uv run lakeshore-examples/test_runner.py

It writes lakeshore-examples/results.json (canonical) and copies the same payload to docs/public/test-results.json (what this page reads).

FlagEffect
--suites-onlySkip the example runs.
--examples-onlySkip the unit-test suites.
--suites <id> …Restrict to specific suite ids.
--only <id> …Restrict to specific example ids.
--enable-cpAlso attempt control-plane-dependent examples.
The runner lives outside this repo

test_runner.py ships with lakeshore-examples, which is a sibling repo — clone dreamlake-ai/lakeshore-workspace to get it alongside everything else. The docs site only consumes the JSON it emits.

Inline usage

In any doc page that documents a specific feature, surface that feature's test status next to it:

mdx
The control-plane poll handler is covered by the
`lakeshore-controlplane` suite: <TestStatus suite="lakeshore-controlplane" />