frontend-testing-best-practices

E2E tests should be preferred over unit tests when validating most user flows or when complex mocking is needed. This approach minimizes mocking and ensures you validate real user behavior rather than internal implementation details.

Avoid direct testing of React components and instead test them through E2E flows using proper selectors. This validates the behavior users see and interact with, rather than relying on internal implementation details that cause brittle tests.

Minimize mocking whenever possible, especially when complex mocks are needed, and favor E2E tests instead. This ensures you validate actual user behavior and avoid the inconsistencies and flakiness that heavy mocking introduces.

An E2E-first strategy applies to most user flows to validate real behavior, but it specifies decision rules for when to use E2E versus unit tests. It provides structured guidance for test organization and selector usage to handle various scenarios.

Organize tested files using a specified e2e/tests directory structure. This rule-based approach provides clear guidance for test structure and selector usage, ensuring consistency across your frontend testing strategy.