rical · Sep 21, 2026 · Sep 21, 2026
diff --git a/test/9pm b/test/9pm
diff --git a/test/9pm-proj.yaml b/test/9pm-proj.yaml
@@ -2,3 +2,6 @@
   PROJECT-NAME: "Infix"
   PROJECT-ROOT: "../../"
   PROJECT-TOPDOC: "../case/"
+  AGENT-HINTS: |
+    Read test/infix-test-skill.md first, it explains how the tests work
+    and where to look.
diff --git a/test/infix-test-skill.md b/test/infix-test-skill.md
@@ -0,0 +1,17 @@
+# Infix test skill
+
+Info about the Infix regression tests.
+
+- Tests live under `test/case/`, are written in Python and use the infamy
+  framework in `test/infamy/`.
+- A test is a chain of `test.step()` blocks that configure one or more DUTs
+  over NETCONF or RESTCONF and verify the result with real traffic. The step
+  text in the failing TAP line is where to start reading.
+- DUTs run Infix, either as virtual machines (Qeneth, `test/virt/`) or as real
+  hardware. The fault is often in the product rather than the test. Device code
+  is in `src/`, YANG models in `src/confd/yang/`.
+- Each test has a logical `topology.dot` with names like `target:data`. Infamy
+  maps it onto the physical topology the test was given, honouring `requires`
+  and `provides` attributes, and prints the mapping in the log. A test is
+  skipped when no mapping fits.
+- Logs: `test/.log/<log id>/output/`. Full guide: `doc/testing.md`.
+105 −34		9pm.py
+1 −0		README.md
+1 −0		etc/9pm-proj.yaml
+3 −0		self_test/cases/crash.sh
+2 −0		self_test/configs/proj-test1.yaml
+28 −0		self_test/run.py