Test changes with confidence as the product evolves #39
Description
What a user wants to achieve
To make changes (features, fixing bugs, refactors) to BlockNote confidently without introducing regressions, and without testing becoming a bottleneck.
Developers and maintainers want a testing system that is easy to understand, consistent to maintain, and aligned with how the product actually behaves.
What success looks like
- The testing strategy is coherent and easy to navigate
- Tests are organized in a way that makes ownership and intent clear
- High-value end-to-end flows are covered and remain reliable over time
- Component-level behavior can be validated without relying solely on full end-to-end runs
- Regressions are caught early and consistently across common workflows
- The test suite supports iteration speed rather than slowing it down