qa-excel-importlisted
Install: claude install-skill th3r-dev/th3-skills
# QA an Excel template import
**In:** the template (`.xlsx` with its hidden dropdown sheet) + the documents to import, and an
**adapter** that knows your importer (`scripts/adapter_example.py` is the contract).
**Out:** a test matrix with expected verdicts, one `.xlsx` per case, a run log with actual
verdicts, and the created document ids checked in the database — all in one `report.xlsx`.
## 0. The contract lives in code — read it before designing
Find the importer's validator (the service behind the validate endpoint) and read it from the
branch the portal runs, not the local checkout. Note which functions decide the verdicts
(header parsing, required columns, grouping, the master lookups, the allowed-pairs check) and
encode them in the adapter's `check()`. The portal's own build (login footer / about page) may be
older than `develop`; **a mismatch between preflight and web is a finding, not noise.**
## 1. Derive the test dimensions from the dropdowns, not from imagination
Cross the template's dropdown columns with the database's allowed-pairs table and write the
decision table down (`references/test-design.md` has the method and the equivalence classes).
Three lists fall out of it and go first in the report: dropdown values that never pass, pairs
that pass but are missing from the dropdown, and pairs the importer refuses that real documents
already carry.
## 2. Minimum set — one file per verdict class, one row per pair
Two facts usually shrink the set:
- **One file