WindsurftestingTesting

Testing Windsurf Rules

Windsurf rules for testing: test-driven development, test organization, coverage, and CI testing strategy.

.windsurfrules

- Write tests before fixing bugs: a failing test proves the bug, passing proves the fix
- Organize tests to mirror the source directory structure
- Use snapshot testing for UI components; update snapshots intentionally
- Run tests in watch mode locally; full suite only in CI for speed
- Use coverage thresholds as a floor, not a target; 100% coverage can still hide bugs
- Apply contract testing (Pact) for microservice API compatibility
- Use chaos engineering tools (chaos-monkey, gremlin) for resilience testing
- Implement synthetic monitoring in production to catch regressions post-deploy

How to use with Windsurf

Create a `.windsurfrules` file in your project root. Windsurf's Cascade AI applies these rules automatically.

← All Windsurf rules All testing rules →

#testing#windsurf#tdd#coverage#coding-rules

Related Rules

TypeScript Windsurf Rules

WindsurfTypeScript

Windsurf rules for TypeScript: strict type safety, functional patterns, and modern TypeScript conventions.

Code Style

typescript · windsurfCopy Ready

React Windsurf Rules

WindsurfReact

Windsurf rules for React: modern patterns, performance, and scalable React architecture.

Architecture

react · windsurfCopy Ready

Go Windsurf Rules

WindsurfGo

Windsurf rules for Go: hexagonal architecture, clean code, observability, and production Go patterns.

Architecture

go · windsurfCopy Ready

Rust Windsurf Rules

WindsurfRust

Windsurf rules for Rust: async Rust, WASM, systems programming, and production Rust patterns.

Architecture

rust · windsurfCopy Ready