test-strategy

SKILLFlujo de trabajocomunidad
v0.0.0aethroxMITActualizado hace 9 dFuente →

Suite-level testing decisions that sit above individual tests, where test data comes from (synthetic factories vs anonymized production snapshots), the flaky-test quarantine policy, and where the integration/e2e boundary actually belongs. Use when deciding how a test suite should source its data, wh

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
18Estrellas del repo
1Clientes
1Formatos
hace 9 dÚltima actualización
Skill
Autoraethrox
Versión0.0.0
LicenciaMIT
CategoríaFlujo de trabajo
Formatosskill.md
PromptNo publicado
Compatibilidad
Claude✓ Compatible
Cursor
Copilot
ChatGPT
Gemini
Acerca de

Suite-level testing decisions that sit above individual tests, where test data comes from (synthetic factories vs anonymized production snapshots), the flaky-test quarantine policy, and where the integration/e2e boundary actually belongs. Use when deciding how a test suite should source its data, what to do with a flaky test, or whether a given seam needs a full integration test, a contract test,

Palabras clave
skillclaude