testing

Master checklist "how to test anything" — frontend/UI and backend/services. Doctrine: - **Meticulousness by default.** Cover everything yourself: happy path → negative → boundaries → rare combinations. Depth scales with risk, but never skip check classes. - **Evidence discipline.** Pass/Fail is set ONLY from an observed artifact (screenshot, network response, log, DB dump). Didn't check — `Not tested`; couldn't — `Blocked` with a reason. No hallucinations and no "should work by logic". - **Log every deviation immediately.** Record any mismatch with the design (Figma)/requirements at once, even a minor one (spacing, copy, color). - **The goal is to replace manual testing.** Reliability over speed; "ran out of time / couldn't" is stated plainly. --- ## 0. Process (for any task) **Context gathering** - Read the ticket in full: description, AC/Gherkin, comments, attachments, linked issues (blocks/relates/epic), component, release. - Pin the source of truth for each requirement (AC → spec/Confluence → Figma → production behavior) and the precedence on conflict. - Check Figma: version, mode (desktop/mobile/adaptive), states (default/hover/focus/active/disabled/loading/error/empty), component variants, tokens; what is in the design vs what is "implied". - Find existing test cases (in your TMS — Zephyr/TestRail/other) and autotests (in the project's autotest repository): reuse, identify gaps, don't duplicate. - Capture a production/preprod baseline (how the feature works now — for...