using-tests
Working with Tests
Testing strategy and workflow. Tests run in parallel with isolated data per suite. Prioritize Playwright for UI, integration tests for APIs, unit tests for logic.
Testing Strategy
Follow this hierarchy when deciding what kind of test to write:
- Playwright tests (browser) - Preferred for most features
- Integration tests (API) - When Playwright is not practical
- Unit tests (pure functions) - Only for complex isolated logic
When to Use Each Test Type
Playwright Tests (Default Choice)
Write Playwright tests when the feature involves:
More from andrelandgraf/fullstackrecipes
ralph-loop
Complete setup for automated agent-driven development. Define features as user stories with testable acceptance criteria, then run AI agents in a loop until all stories pass.
2.5Kobservability-monitoring
Complete observability stack with structured logging, error tracking, and web analytics.
279stripe-subscriptions
Complete subscription billing system with Stripe integration, feature flags for plan gating, webhook handling, and billing portal.
207nextjs-on-vercel
Create a Next.js app running on Bun, configure the development environment, and deploy to Vercel with automatic deployments on push.
137ai-chat
Build a complete AI chat application with database persistence, chat list management, and automatic title generation.
126pino-logging-setup
Configure structured logging with Pino. Outputs human-readable colorized logs in development and structured JSON in production for log aggregation services.
126