summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/next-tests.md11
-rw-r--r--docs/typ/building.typ7
2 files changed, 14 insertions, 4 deletions
diff --git a/docs/next-tests.md b/docs/next-tests.md
index a16a7cf9..b05e9352 100644
--- a/docs/next-tests.md
+++ b/docs/next-tests.md
@@ -48,7 +48,8 @@ agent's survey. The `e2e` line (kbdin, mousein) is its first step.
new_pane, execute).
- **agent_session_test.py is kept,** run by hand: it tests the
agent_session.py tool.
- - **Still Python in the build:** gui_monkey.py (monkey-gui, for T4).
+ - **No Python left in the build:** gui_monkey.py and gui_golden.py are
+ test/process/window.zig's two cases (T4, below).
Each backend's own (2026-11-04, the user: an effect's test is the
backend's):
@@ -108,7 +109,13 @@ agent's survey. The `e2e` line (kbdin, mousein) is its first step.
The window (T4): its core is the one T1 drives, so a behaviour the cells
show is tested at T1; T4 is for what only pixels show (scene effects,
-images, fonts, edges). test/gui_golden.py's 17 frame hashes
+images, fonts, edges). Built (2026-11-04): test/process/window.zig's
+monkey (a smoke run in process-test, all 40 Motion x Lift x Bloom with
+`zig build monkey-gui -Dplatform=gui`) drives the window's own input
+(Detached.typeKeys and mouse: its pty and OSC 777) and checks it settles,
+alive, with no crash record; its goldens (`zig build gui-golden
+-Dplatform=gui`, PARDES_GUI_GOLDEN=update to rewrite) hash 17 scenes'
+frames from Detached.capture. The old notes: test/gui_golden.py's 17 frame hashes
(test/gui-goldens.txt) are an exact gate for one machine, never a CI one,
and move to the Zig runner with T2. gui.zig's own tests: 19 M, 17 B, 47 U.
diff --git a/docs/typ/building.typ b/docs/typ/building.typ
index 24229f08..99a83589 100644
--- a/docs/typ/building.typ
+++ b/docs/typ/building.typ
@@ -80,7 +80,10 @@ zig build kitty-harness kitty graphics through a pane end to end (a fake kitt
zig build syntax-test tree-sitter tests without building the editor
zig build syntax deterministic per-byte highlighting snapshots
zig build behaviour-test behaviour through the 9P tree, in process (test/behaviour/)
-zig build process-test real sessions over their sockets: mounts, flags, shells (test/process/)
+zig build process-test real sessions over their sockets: mounts, flags, shells (test/process/);
+ -Dplatform=gui runs each case on the hidden window instead
+zig build monkey-gui random input to the hidden window, every effect setting (-Dplatform=gui)
+zig build gui-golden the hidden window's scenes against this machine's goldens (-Dplatform=gui)
zig build monkey-session random in-process 9P requests checking the documented rules
zig build 9p-test freestanding protocol tests
zig build 9p-io-test native 9P transports and client
@@ -128,7 +131,7 @@ zig build cheatsheet render the cheatsheet PDF (needs typst)
A release passes all of these first: `unit-test` with `-Dplatform=tui` and
with `-Dplatform=gui`, `core-test`, `behaviour-test`, `process-test`, `snap`, the GUI goldens
-(`python3 -B test/gui_golden.py <a Debug pardes-gui>`, a hidden window),
+(`zig build gui-golden -Dplatform=gui`, a hidden window; `PARDES_GUI_GOLDEN=update` rewrites them),
`web`, and the ReleaseSafe tui and ReleaseFast gui builds. The committed
`docs/typ/cheatsheet-a4.pdf` is rendered again when the docs change.