web-testing
Web Testing Skill
Version: 1.0 Stack: React Testing Library + Jest + Prisma
The wrong testing strategy wastes more time than no tests at all. Tests that test implementation break every time you refactor. Tests that share state flake randomly. Tests without error cases give false confidence — your suite is green but your app crashes on the first unexpected input. You write tests, they break for the wrong reasons, and the team stops trusting them.
Behavior-focused tests survive refactoring. Isolated tests never flake. The testing pyramid keeps the suite fast enough that people actually run it. These patterns produce tests you can trust.
Core Principles
- Test Behavior, Not Implementation — Test what users see and do, not internal details.
- Pyramid Structure — Many unit tests, fewer integration, minimal E2E.
- Fast Feedback — Tests should run in seconds, not minutes.
- Deterministic — Same input = same output. No flaky tests.
- Isolated — Tests don't depend on each other or external state.
More from alexanderstephenthompson/claude-hub
unity-csharp
C# patterns for Unity - MonoBehaviour, async, architecture, and VR/mobile performance optimization
50design
Design and UI standards for accessibility, semantic HTML, and responsive layouts
36architecture
Architecture principles, module boundaries, folder structure, and project type profiles
34vrc-udon
VRChat Udon and UdonSharp patterns - networking, sync, interactions
33data-python
Python patterns for data processing - pandas, polars, pyspark
33web-performance
Performance patterns for Apollo caching, Redis, and CloudFront optimization
33