Testing Best Practices Rules

testingquality

Testing conventions and quality guidelines covering unit tests, integration tests, and test architecture patterns.

Целевые файлы

Файл	Формат
.cursorrules	plaintext
CLAUDE.md	markdown

Содержимое

Test framework: ${test_framework}. Run tests before every commit. Never merge code with failing tests. Follow the AAA pattern: Arrange (set up data), Act (execute the code under test), Assert (verify the result). One logical assertion per test. Name tests descriptively: "should return 404 when user is not found" — not "test1" or "works correctly". Test behavior, not implementation. Avoid asserting on internal state or private methods. Refactoring should not break tests. Use factories or builders for test data instead of hardcoded literals. Share setup via beforeEach/fixtures, not copy-paste. Mock external dependencies (HTTP APIs, databases, file system) at the boundary. Prefer dependency injection over monkey-patching. Aim for meaningful coverage, not 100%. Focus tests on business logic, edge cases, and error paths. Skip trivial getters/setters. Keep tests fast: unit tests under 50ms each. Isolate slow integration tests into a separate suite that runs in CI.

Переменные

ID	Метка	По умолчанию	Варианты
test_framework	Test Framework	vitest	vitestjestpytest

CLI

npx mindaxis apply testing-rules --target cursor --scope project

Используется в паках

MCP Server Developer Kit

Build your own MCP servers