Rules Hub
Coding Rules Library
← Back to all rules
Rule priority, scope & exceptions
Use this to align rules with the senior-level structure (P0/P1/P2, scope, exceptions/tradeoffs).
fullstack ruleP2universalStack: javascript
testingnamingreadabilityclarity
Write test descriptions that clearly state the expected behavior
Phrase it/test titles as readable behavior statements (e.g. 'should not render buttons'), avoiding grammatically broken or ambiguous descriptions.
PR: frontpage-web · org-mining-hist-2026-06Created: Jun 18, 2026
Bad example
Old codejavascript
| 1 | it('should buttons exists', () => { /* ... */ }); |
Explanation (EN)
Objašnjenje (HR)
Good example
New codejavascript
| 1 | it('should render the buttons', () => { /* ... */ }); |
Explanation (EN)
Objašnjenje (HR)