# Paladin client test record — blank manual form **Uncompleted template, not evidence or a passing test result.** Copy this form for a real session. Leave unobserved fields blank and results `NOT_RUN`. Follow the [client test plan](../PALADIN_CLIENT_TEST_PLAN.md) and [macro cases](../PALADIN_MACRO_TEST_CASES.md). Do not copy dates, builds or results from research exports. ## Session and actual client - Report ID / tester reference: ____________________ - Actual start timestamp, UTC offset and named timezone: ____________________ - Actual end timestamp, UTC offset and named timezone: ____________________ - Client version / build number / interface number: ____________________ - Actual channel (release, beta, accepted release candidate, or unknown): ____________________ - Evidence establishing channel / any explicit release-candidate acceptance: ____________________ - Locale / selected installation or ruleset: ____________________ - Build capture method and evidence reference: ____________________ - Collector version and scan ID, if used: ____________________ - Importer version and diagnostic receipt ID, if used: ____________________ Collector scans describe environment and visible availability. `/asm status` and import receipts describe environment/import outcomes. Neither records successful macro execution. Missing APIs or unknown values stay unknown. ## Character and controlled setup - Class / level / race / faction: ____________________ - Actual talent allocation, ranks and evidence; legal-allocation check: ____________________ - Actual Legacy allocation / Talented rank / supporting evidence: ____________________ - Learned spell names, exact ranks/IDs where observable, acquisition evidence: ____________________ - Equipped weapon(s), shield, relevant gear and consumables/reagents: ____________________ - Macro button and key chord; modifier bindings and conflicts checked: ____________________ - Auto self-cast / self-cast modifier / focus-cast modifier settings: ____________________ - Button-down versus button-up action setting: ____________________ - Target, mouseover, focus, combat, aura, attack, resource and cooldown starting states: ____________________ - Loaded addons and versions, including bar/binding owners; disabled-addon control if performed: ____________________ - Other settings, latency or setup conditions affecting interpretation: ____________________ ## Exact macro identity and readback - Canonical macro ID / version / in-game name: ____________________ - Canonical pack path and source revision: ____________________ - Canonical body SHA-256 / UTF-8 byte count: ____________________ - Newline representation and any explicitly documented comparison normalization: ____________________ Canonical text actually selected for this session: ```text ``` Native `/macro` editor text actually read back after creation/import: ```text ``` - Native editor readback evidence / comparison method: ____________________ - Exact-text comparison result: `NOT_RUN`; explanation: ____________________ - Readback after `/reload`: `NOT_RUN`; evidence: ____________________ - Readback after normal exit and restart, if performed: `NOT_RUN`; evidence: ____________________ Stop and identify a mismatch before treating any execution result as evidence for the canonical body. Personal edits are a different test subject. Import/readback persistence is separate from gameplay behavior. ## Claimed scope and case observations - Claimed supported branches and character/target conditions: ____________________ - Explicitly unsupported, unverified or excluded branches and reasons: ____________________ - Historical-record or exploratory diagnostics only: ____________________ Write each case's expectation **before** pressing the button. Record one press and its recipient, action, rank, errors and side effects. Include the ordinary spell-button comparison where required. Copy row pairs for every applicable case. Reset the stated conditions between observations. The plan's practical evidence gate asks for two repeat observations after reset; this is a maintainer rule, not an existing validator check. If a repeat cannot be completed safely or meaningfully, record the reason and leave that coverage incomplete for review. | 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 + timestamp/timecode | Result / reason | | --- | --- | --- | --- | --- | --- | --- | | ______ / 1 | | | | | | NOT_RUN | | ______ / 2 | | | | | | NOT_RUN | | ______ / 1 | | | | | | NOT_RUN | | ______ / 2 | | | | | | NOT_RUN | Results: `PASS` = observed behavior matches the stated positive case; `EXPECTED_FAILURE` = the predeclared negative case fails as intended; `FAIL` = mismatch; `BLOCKED` = required conditions unavailable; `NOT_RUN` = unperformed; `NA` = genuinely irrelevant to this exact body, with a reason. Expected failure does not prove a successful cast branch. Missing talents, ranks, reagents or recipients are blocked coverage, not N/A. ## Evidence and coverage review - Private original capture IDs and SHA-256 hashes: ____________________ - Private storage/retention reference: ____________________ - Redacted report/capture references and hashes: ____________________ - Observation-to-evidence mapping or timecode index: ____________________ - Applicable case inventory and count; completed twice / incomplete: ____________________ - Failures, blocked cases, omitted repeats and unresolved contradictions: ____________________ - Required corrections, narrower claims or next session: ____________________ - Optional full final-release repeat session ID, actual build and evidence: ____________________ Keep raw originals in ignored `research/captures/private/` or another private archive. Collector files can contain character names and realms. Preserve originals; publish only reviewed, redacted material and non-identifying evidence references. Do not execute saved Lua or place private captures in `public/`. ## Maintainer decision — leave unchecked until reviewed - [ ] Exact ID/version/body hash and native editor readback match the test subject. - [ ] Actual build, channel, locale and character conditions are evidenced. - [ ] Every applicable claimed branch and negative case has adequate observations; N/A reasons and incomplete coverage were reviewed. - [ ] Required reset/repeat observations are complete for the claimed scope. - [ ] No unresolved failure or blocked advertised branch is being counted as a pass. - [ ] Private originals and redacted evidence/report references are retained. - [ ] Limitations and claim scope match the observations; diagnostics are not advertised as supported behavior. - [ ] Any proposed canonical metadata change has separate maintainer review and required repository checks. - Reviewer reference / actual review timestamp and timezone: ____________________ - Decision, exact supported scope and reasons: ____________________ - Proposed existing status, if any, and actual fully tested build(s): ____________________ - Canonical edit/changelog review reference, if later performed: ____________________ This form changes no status. Partial results do not justify adding a new `tested_builds` entry. `beta-tested` requires actual beta evidence; release testing must satisfy the scoped `release-ready` retest gate on release or an explicitly accepted release candidate. Historical macros stay deprecated pending a separate content decision. Never use a generic `tested` status or add custom evidence fields to canonical JSON; use the existing fields and a separately reviewed report. Current validators do not enforce this form's evidence requirements.