testing-guide

Unit tests validate isolated utility functions, integration tests check component interactions, and E2E tests execute critical user flows. You should select the appropriate test type using decision tree criteria to balance execution speed and reliability across the test pyramid.

To write an E2E test for a user login flow with Playwright, you should follow practical patterns and best practices that simulate user interactions. This ensures your critical user paths are validated reliably across different test scenarios.

Best practices for Vitest and Testing Library involve implementing practical testing patterns and utilizing data factories. You should evaluate test effectiveness and adhere to specific guidelines on what not to test to maintain code quality and reliability.

When implementing software testing strategies, you should not test implementation details or redundant framework internals. The guide specifically addresses what not to test, ensuring you focus your testing efforts on meaningful behavior and avoid brittle, low-value test suites.

Data factories improve integration testing by providing structured, reusable test data generation patterns. They help ensure code quality and reliability by isolating test scenarios from external data dependencies, allowing consistent and predictable test evaluation.