# Shaman client test record — blank manual form **Uncompleted template, not evidence or a passing result.** Leave actual values blank and unperformed outcomes `NOT_RUN`. Use the class checklist, the exact generated macro case list and the repository validation matrix. No source export date/build, cast result or reviewer decision is supplied by this form. ## Planned subject and actual session - Planned class: Shaman - Report ID / tester reference: ____________________ - Actual start timestamp / UTC offset / named timezone: ____________________ - Actual end timestamp / UTC offset / named timezone: ____________________ - Actual client version / build / interface: ____________________ - Actual beta / release / accepted-RC / unknown channel: ____________________ - Channel evidence / explicit RC acceptance if relevant: ____________________ - Locale / active installation or ruleset: ____________________ - Build capture method and evidence ID: ____________________ - Collector version / scan ID if used: ____________________ - Importer version / diagnostic receipt if used: ____________________ Collector scans and import receipts describe environment or import outcomes, not macro execution. Missing API values remain unknown. ## Actual character and controlled conditions - Actual class / level / race / faction: ____________________ - Actual talents / ranks / legal allocation evidence: ____________________ - Actual Legacy allocation / Talented rank / evidence: ____________________ - Learned spell names / ranks / IDs where observable / acquisition evidence: ____________________ - Pet family / living-control state / actual trained abilities if relevant: ____________________ - Weapon / shield / gear / reagents / consumables: ____________________ - Macro button / key chord / binding and modifier conflicts: ____________________ - Self-cast / focus-cast settings / button-down or button-up action setting: ____________________ - Loaded addons / bar-binding owners / control setup: ____________________ - Starting target / mouseover / combat / form-stance / stealth / auras: ____________________ - Starting attack / health-resource / cooldown-GCD / range-LOS / facing states: ____________________ - Other conditions affecting interpretation: ____________________ ## Exact canonical identity and native readback - Canonical ID / version / in-game name: ____________________ - Canonical pack / source revision: ____________________ - Canonical UTF-8 body SHA-256 / byte count: ____________________ - Newline representation / documented comparison normalization: ____________________ Canonical text actually selected for this session: ```text ``` Native macro-editor text actually read back: ```text ``` - Exact-text comparison result: NOT_RUN - Native readback evidence / comparison method: ____________________ - Readback after reload result: NOT_RUN - Reload readback evidence: ____________________ - Readback after normal restart result: NOT_RUN - Restart readback evidence if performed: ____________________ Identify a mismatch before attributing execution to the canonical body. Personal edits are different subjects. Import/readback is not a gameplay pass. ## Claimed scope and actual observations - Claimed supported branches / actual character-target conditions: ____________________ - Explicit unsupported / unverified / excluded branches and reasons: ____________________ - Historical acquisition or exploratory diagnostics only: ____________________ - Ordinary spellbook control and its observed outcome: ____________________ Write expectations before execution. Use one deliberate input, reset stated conditions and record two observations for each required case under the plan's maintainer rule. Duplicate blank row pairs as needed. Missing prerequisites are blocked coverage, not passes or N/A. | Case ID / repeat | Reset and state before press | Expected recipient/action/rank and side effects | Observed recipient/action/rank | Error and other side effects | Evidence ID and timestamp/timecode | Result | | --- | --- | --- | --- | --- | --- | --- | | ______ / 1 | | | | | | NOT_RUN | | ______ / 2 | | | | | | NOT_RUN | Use PASS for an observed matching positive case, EXPECTED_FAILURE for an intended predeclared negative failure, FAIL for a mismatch, BLOCKED for unavailable required conditions, NOT_RUN for no observation, or NA only with a genuine irrelevance reason. An expected failure does not prove the positive action. ## Evidence retention and coverage review - Private original evidence IDs / SHA-256 hashes: ____________________ - Private retention reference: ____________________ - Redacted report/capture references / hashes: ____________________ - Observation-to-evidence mapping / timecode index: ____________________ - Applicable case inventory / completed repeat pairs / incomplete coverage: ____________________ - Failures / blocked cases / missing repeats / contradictions: ____________________ - Corrections / narrower supported claims / next session: ____________________ - Optional full final-release repeat session / actual build / evidence: ____________________ Preserve originals privately, such as ignored research/captures/private/. Do not execute captured Lua, publish account/character dumps or upload raw evidence through this record editor. Publish only separately reviewed redacted material. ## Maintainer decision — leave unchecked until separately reviewed - [ ] Exact ID/version/body hash and native text identify the subject. - [ ] Actual build/channel/locale/character conditions have evidence. - [ ] Applicable claimed branches and negative/special cases were reviewed. - [ ] Required reset/repeat observations and justified exclusions were reviewed. - [ ] No unresolved failure or blocked advertised branch counts as a pass. - [ ] Private originals and redacted report references/hashes are retained. - [ ] Limitations and supported scope match the observations. - [ ] Any canonical metadata edit has a separate review and required checks. - Reviewer / actual review timestamp / timezone: ____________________ - Decision / exact supported scope / reasons: ____________________ - Proposed existing status / actual fully tested builds: ____________________ - Later canonical edit / changelog review reference: ____________________ This blank form changes no status. Beta-tested needs actual beta evidence; release-ready needs the release or accepted-RC retest and maintainer gates. Historical actions stay deprecated pending separate review. Partial results do not justify a new tested_builds entry; never invent a generic tested status or custom canonical evidence fields. Validators do not enforce this form's complete evidence requirements.