studio-testing

Installation
SKILL.md

Studio Testing Strategy

Protect meaningful observable behavior and plausible regressions. Choose the fastest test that catches the failure; do not chase coverage percentages or exhaustive input permutations.

Choose coverage by behavior

Before adding a test, identify what would get worse for a user or caller if the behavior broke. Read nearby tests first so new coverage fills a real gap.

Layer Use for
Static analysis Types, invalid imports, and other guarantees the compiler or linter already checks
Unit tests Pure calculations, parsing, validation, permissions, and data transformations
Component tests Rendered behavior and consequential interactions, including simple forms that submit, mutate data, or navigate
E2E tests Critical user journeys and integration or environment differences that lower layers cannot establish
Installs
341
GitHub Stars
115.2K
First Seen
Feb 21, 2026