From 54f3ce0443f46f0bfe7565d6a31fb906beadf3b9 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Wed, 4 Nov 2026 10:39:39 -0300 Subject: docs/next-tests.md: one process runner for the snap scripts, the process tests and the window's (the user's), in place of 9P verbs for the snap runner; the in-build Python suites to move onto it or Session Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_016Y9MNAtZenFv4weoMD3cge --- docs/next-tests.md | 23 ++++++++++++++++++----- 1 file changed, 18 insertions(+), 5 deletions(-) diff --git a/docs/next-tests.md b/docs/next-tests.md index 3f85e030..4cf2c1fb 100644 --- a/docs/next-tests.md +++ b/docs/next-tests.md @@ -15,11 +15,24 @@ agent's survey. The `e2e` line (kbdin, mousein) is its first step. - **T1, in-process 9P, is the main tier.** The core is driven only through `serveFs` (src/ninep/testing.zig's `call`, `rd`, `wr`): as behavioural as a client on a socket, and milliseconds a case. -- **Process-level tests (T2) get a Zig runner, not Python:** test/snapshot.zig, - the `.snap` runner, which already forks the app in a pty and has a 9P - client (`snap9p`), grows 9P verbs (`9pwrite`, `9pexpect`, `signal`). The - Python suites (test/fs.py and the rest) stay as examples of scripting a - session and are not grown. +- **One process runner, not Python (the user, 2026-11-04):** test/process.zig's + `Process` starts `pardes` detached (over its socket), in a pty, or as the + hidden window, in a throwaway root, and talks 9P to it with Session's + method names (`read`, `write`, `refused`, `keys`, `click`, `screen`, + `focused`), plus `signal`, the exit code, pty bytes and captured frames + by mode. It is mostly test/snapshot.zig's launching and 9P client moved + out: + - **the `.snap` scripts** become one user of it (the interpreter and the + goldens stay in snapshot.zig); + - **process tests (T2)** are plain Zig tests in test/process/