nanook-test-flowlisted
Install: claude install-skill xhubio/nanook-skill
# Nanook Test Flow — From Data Tables to a Test Sequence
Nanook's decision and matrix tables describe **what a thing is** and **what it becomes**
(`create-equivalence-class-table`). A running suite executes each case in isolation
(`nanook-app-runner`). What neither covers is the **sequence**: create a customer, save,
open it, check it; create three bookings, book them, run the VAT return, compare. This
skill describes the third table kind — the **flow table** — and the runner that drives it.
| Question | Skill |
|---|---|
| How do I write decision / matrix / specification tables? | `create-equivalence-class-table` |
| How do the generated cases become a running suite for an app? | `nanook-app-runner` |
| How do I chain cases from several tables into one test? | **this one** |
🔴 Nanook itself (`@xhubio/nanook-table`) does **not** know flow tables. Its processor
handles `<DECISION_TABLE>` and `<MATRIX_TABLE>`; on a `<FLOW_TABLE>` it throws *"There is
no parser for the table type"* — and since a processor loads all workbooks of a folder
together, one flow sheet in the data folder breaks the whole build. Flow tables live in
their **own folder** and have their **own reader** (`references/flow-reader.ts`; the reference
resolver shared with the matrix runner is `references/fall-referenz.ts`).
```
testdata-definition/
├── data/ — decision and matrix tables (nanook reads them → suites/*.json)
└── flow/ — flow tables (the flow reader reads them → the flow r