Przejdź do treści
Biblioteka skilli
Programowanie · Testowanie

sumo-qa-finding-test-data

/sumo-qa-finding-test-data

Pomaga w danych testowych: dobiera dane do testowania funkcji, znajduje wzorcowe rekordy, sprawdza wpisy i rejestruje nowe dane.

Repozytorium
sumo-qa ↗
Licencja
Apache-2.0
Ostatnia zmiana repozytorium
22.10.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 22.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co robi i kiedy

Pomaga w danych testowych: dobiera dane do testowania funkcji, znajduje wzorcowe rekordy, sprawdza wpisy i rejestruje nowe dane.

Oryginalny opis (EN)

Use after sumo-qa-deciding-approach routes here, when the user asks about test data — what data to test X, find a known-good record, validate an entry, register new known-good data. Routes between the explain, find, validate and register test-data tools.

Jak działa

  1. Output discipline (mandatory)
  2. The Iron Law
  3. When to Use
  4. Checklist
  5. Process Flow
  6. Red Flags
  7. Examples
  8. Next skill in the chain
Sekcje z nagłówków SKILL.md, w oryginale · 82 linii, 921 słów
Podgląd SKILL.md
---
name: sumo-qa-finding-test-data
description: Use after sumo-qa-deciding-approach routes here, when the user asks about test data — what data to test X, find a known-good record, validate an entry, register new known-good data. Routes between the explain, find, validate and register test-data tools.
---

# Finding test data

## 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 prior conversation). The user's confirmation gate only applies to **register** (step 5b) — writing to the shared catalogue is a side effect that should always pause for confirmation.

1. **Pick the route** *(no user question — derive from intent)*. The four routes are internal dispatch data, NOT a label to echo at the user:
   - **Explain requirements:** "what data do I need" → `sumo_qa_explain_test_data_requirements`
   - **Find:** "find me a record" → `sumo_qa_find_test_data`
   - **Validate:** "is this still valid" → `sumo_qa_validate_test_data`
   - **Register:** "save this as known-good" → `sumo_qa_register_known_good_test_data`
2. **Gather inputs from intent + prior conversation** *(no user question if the conversation has them)*. Question, environment, domain, criteria, entry path — pull from what's already been said. Only ask if a genuinely required field is missing, and ask ONCE.
3. **For explain:** call the tool. Return the requirements as text in natural English.
4. **For find:** call the tool with the gathered criteria. If matches: pipe each into validate (step 5a). If no matches: say so explicitly — do NOT invent and do NOT silently broaden the criteria.
5. **For validate:**
   - **5a (from find or direct):** call `sumo_qa_validate_test_data` against the source system in this turn. A cached or memorised result is not fresh. Report state with timestamp + the validation evidence.
   - **5b (register):** confirm with the user before writing to the catalogue. Show the entry, the validation evidence, and ask: *"Register this as known-good?"* Only write on explicit yes. **Arg shape:** call `sumo_qa_register_known_good_test_data(entry={...})` with `entry` as a literal dict (id, environment, domain, scenario_tags, known_valid_for, constraints, owner, last_validated_at, confidence, source, notes). Not a YAML string. The tool docstring has a complete example.
6. **If an entry fails validation:** mark it stale, surface the failure to the user, do NOT silently substitute another entry. The user decides whether to find an alternative or register a new one.

## Process Flow

See the Checklist above — that's the flow.

## Red Flags

| Thought | Reality |
|---|---|
| "I'll just make up a SKU that probably works" | Iron Law violated. Catalogue entries only. |
| "Validation is expensive — assume it's still good" | Stale is a defect. Always validate against the source system in this turn, especially for shared catalogues. |
| "User said 'find me one' — I'll skip validation" | Validate. The whole point of the catalogue is freshness. |
| "I'll just use the find result without validating" | Snapshots go stale within minutes in shared staging. Validate every find before quoting the record as test data. |
| "Register this as known-good without testing it first" | Don't. Register only after the user has confirmed the entry was used successfully — and confirm again before writing to the catalogue. |
| "If no entry matches, I'll fabricate one" | Surface the gap. The user might need to register a new entry — let them decide. |
| "Found entry failed validation — let me silently grab the next one" | No. Surface the failure to the user with the entry that went stale; let them pick the alternative. Silent substitution hides drift in the catalogue. |
| "The data I need is a CLI/API's output — I'll hand-write a plausible fixture" | No. `real-capture fixtures for external-output matchers` (`sumo_qa_load_techniques`): capture the tool's REAL output first (run it, redirect to a file). An invented fixture validates your assumption, not the real contract. |

## Examples

### Good (find → validate → surface)

> **User:** *"find me a refund-eligible order for the refund-flow test."*
>
> **AI (user-facing):** *"Found `ORD-77821` — refund-eligible, validated against staging just now (2026-05-12 09:14). `ORD-77900` is in the catalogue too but is now stale (already refunded on 2026-05-10); flagging it so we can register a replacement later."*

The user sees the result + freshness evidence, not the dispatch labels.

### Bad (inventing)

> **User:** *"find me a refund-eligible order."*
>
> **AI:** *"Try `ORD-12345` — that should work for refund testing."*

Inventing an entry. Iron Law violated.

## Next skill in the chain

Terminal skill — no next-skill handoff. Returns the data (with freshness evidence) to the caller, which is usually a TDD / review / strengthening flow already mid-conversation.

Wersje

W bazie nie ma innych skilli o nazwie sumo-qa-finding-test-data.

Migawka bazy z 13.11.2026 · wersja paczki 55f20803fd57 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100sumo-qa-preparing-for-work
    Planuje QA dla historyjki lub zgłoszenia przed kodowaniem, w lekkiej formie, bez formalnych kryteriów wejścia i wyjścia.
  • 100sumo-qa-creating-test-plan
    Przygotowuje formalny plan testów dla zadania: kryteria wejścia i wyjścia oraz fazowe podejście QA, gdy praca jest śledzona i recenzowana.
  • 100matlab-cosimulate-sumo-simulink
    Buduje modele Simulink współsymulujące z symulatorem ruchu Eclipse SUMO przez TraCI: serwer i klient, bloki Reader, Writer i Actor, losowy ruch, sterowanie pojazdem ego oraz walidacja scenariuszy ADAS.
  • 100test-data-builder
    Prawdopodobnie pomaga budować dane testowe wzorcem Test Data Builder w automatyzacji testów.
  • 100create-test
    Zamienia uwagi człowieka na deterministyczny test w katalogu tests i rejestruje go przy egzekwowanej regule.
  • 100validate-test-coverage
    Sprawdza pokrycie testami względem kryteriów akceptacji: czy testy odpowiadają wymaganiom, czy zestaw jest kompletny i jak user stories mają się do przypadków testowych.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.