Angular
Component Testing Strategies That Survive Refactors
Most brittle Angular tests fail because they test implementation, not behavior. A look at TestBed patterns that stay green through real refactors.
2 min read
Tag
5 articles
Most brittle Angular tests fail because they test implementation, not behavior. A look at TestBed patterns that stay green through real refactors.
Testing Library's core rule — the more your tests resemble how software is used, the more confidence they give you — changes what a good React test looks like.
The testing pyramid was always a proxy for a cost trade-off — here's the trade-off itself, and when the pyramid's shape doesn't apply.
Characterization tests pin down what legacy code actually does, bugs included, so you can refactor safely without a real specification.
How Spring Boot's test slice annotations work, where they save real time, and the point at which reaching for @SpringBootTest is the better call.