17 lines
850 B
Plaintext
17 lines
850 B
Plaintext
---
|
|
description: Testing and quality expectations for Mixmaker
|
|
alwaysApply: true
|
|
---
|
|
|
|
# Testing And Quality
|
|
|
|
- Keep changes scoped and aligned with `memory_bank/`.
|
|
- After substantive edits, run the narrowest useful checks available.
|
|
- Backend domain rules and use cases must be unit-testable without PostgreSQL.
|
|
- Add focused tests for balancing constraints, draft transitions, role limits, and repeated-ban rules.
|
|
- Repository and migration behavior should use integration tests once the database layer exists.
|
|
- Critical frontend flows should receive component or end-to-end coverage as the UI stabilizes.
|
|
- Test concurrent or repeated draft commands for idempotency and version conflicts.
|
|
- Do not add broad abstractions until repeated behavior proves they are needed.
|
|
- Prefer explicit domain invariants over compatibility with unfinished code.
|