dexter/BTerminal
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
BTerminal/.claude/rules/54-testing-gate.md
Hibryda ee198a2fdb chore: reorganize rules files — consolidate duplicates 
Migrates legacy rule numbering (18, 20) to standardized sequence (53, 54) and adds new 18-preexisting-issues.md for handling pre-existing issues during development. This consolidates duplicate rule coverage across the old and new numbering schemes.

Files changed:
- Removed: 18-relative-units.md (moved to 53-relative-units.md)
- Removed: 20-testing-gate.md (moved to 54-testing-gate.md)
- Added: 18-preexisting-issues.md (new)
- Added: 53-relative-units.md (renamed from 18)
- Added: 54-testing-gate.md (renamed from 20)
2026-03-12 06:47:47 +01:00

1.1 KiB
Raw Blame History

Testing Gate (Post-Implementation)

Run the full test suite after every major change before considering work complete.

What Counts as a Major Change

  • New feature or component
  • Refactoring that touches 3+ files
  • Store, adapter, or bridge modifications
  • Rust backend changes (commands, SQLite, sidecar)
  • Build or CI configuration changes

Required Command

cd v2 && npm run test:all

This runs vitest (frontend) + cargo test (backend). For changes touching E2E-relevant UI or interaction flows, also run:

cd v2 && npm run test:all:e2e

Rules

  • Do NOT skip tests to save time. A broken test suite is a blocking issue.
  • If tests fail, fix them before moving on. Do not defer test fixes to a follow-up.
  • If a change breaks existing tests, that's signal — investigate whether the change or the test is wrong.
  • When adding new logic, add tests in the same commit (TDD preferred, see rule 06).
  • After fixing test failures, re-run the full suite to confirm no cascading breakage.
  • Report test results to the user: pass count, fail count, skip count.