The Testing Trophy and Testing Classifications
kentcdodds.comHow to interpret the testing trophy for optimal clarity
Testing software-intensive systems involves more decisions than the standard vocabulary suggests. The conventional taxonomy (unit, integration, system, …
Thierry de Pauw: consulting CTO - IT Delivery Consultant - IT Engineer - Don’t Let AI Invert The Testing Pyramid
Kent C Dodds Write tests. Not too many. Mostly integration. Making your UI tests resilient to change The Testing Trophy and Testing Classifications How to know what to test Kent C. Dodds - How to know what to test? (Youtube) No mocks allowed: A testing discussion with Kent C. Dodds Why integration tests are better than unit tests with Kent C. Dodds Effective snapshot testing : This one highlights issues like false negatives and the lack of clarity in test intention when relying on snapshots.
Property-based testing helps us write better tests, with less code, and greater coverage. This leads to more confidence in our code, and fewer bugs in our applications. But, as always, there’s a price. Property tests take more effort to write, and they take longer to run. Still, I’m convinced that the trade-off is worth it. In this article, we’ll run through an example of how to write property tests using fast-check.