# Behavioural tests: free to rewrite the code > I think we need a larger project to turn most of the tests into > behavioural ones so that we are free to rewrite the code. Planned 2026-11-03 by the user and the coordinator, from an inventory agent's survey. The `e2e` line (kbdin, mousein) is its first step. ## Decided by the user - **A test goes in and comes out through public surfaces only:** the 9P tree (pane files, `ctl`, `look`/`exec`, `log`, `/screen`, `kbdin`, `mousein`), the process (flags, daemon, attach, signals, terminal bytes), and files on disk and effects. A rewrite that keeps those keeps its tests. - **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. - **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** became its tty cases (2026-11-09, below: The suites), their goldens kept in test/snapshots/; - **process tests (T2)** are plain Zig tests in test/process/