Why Testing Library is not unit testing
Testing Library is useful, but rendering components and testing them through the DOM is integration testing, not unit testing.
Testing Posts
Testing strategy, test design, and feedback loops for reliable software.
-
-
Why you should not ship test IDs to production
React Testing Library works best with semantic queries like role and label. Shipping data-testid to production hides accessibility problems and turns test-only markup into an accidental contract.
-
High coverage is not enough: mutation testing in TypeScript with Stryker
Code coverage shows what your tests execute. Mutation testing shows whether your tests fail when the code is wrong, and where Stryker fits.
-
Why your unit tests feel fragile
Unit tests do not feel fragile because testing is hard. They feel fragile because our design mixes business logic and side effects.