sumo-qa-finding-test-datalisted

# Finding test data **Announce at start:** *"Finding test data — validated fresh."* ## Output discipline (mandatory) Inherits the global discipline from `using-sumo-qa`: **output discipline** (never surface internal taxonomy labels — say *"behaviour change in pricing"*, not *"Classification: business_logic_change"*), **output economy** (spend output on findings not framing; no preamble or self-narration; one question per turn; no closing pleasantries), knowledge authority hierarchy, internal scaffolding stays internal, and specialty-tool fit. ## The Iron Law **STALE IS A DEFECT. NEVER INVENT ENTRIES NOT IN THE CATALOGUE.** A catalogued entry not re-validated against the source system in this turn is no better than an invented one — validation is the proof, not ceremony. **find_test_data MUST be immediately followed by validate_test_data against the returned record IN THE SAME TURN before the record is considered usable.** ## When to Use User intents that trigger this skill: - "what test data do I need for X" - "find me a known-good record for X" - "is this record / account / fixture still valid" - "save this as known-good test data" - "I need a locked account for the failed-login test" - "I need a pending invoice for the due-date boundary test" ## Checklist Track these as an ordered work list (use the host's task primitive if available, otherwise a numbered inline tracker) and complete in order. Steps 1–2 are AI-only homework (route the request, gather inputs from