webapp-testing

Webapp integration tests should focus on testing use cases and functional aspects rather than implementation details. You should follow standard file naming patterns and use established libraries like `testSelector` to find elements, ensuring your tests remain robust and maintainable.

The best way to mock API calls in frontend testing is by implementing smart mocks using the `msw` library. This approach allows you to effectively intercept and simulate network requests, ensuring your integration tests run reliably without hitting actual backend endpoints.

You should prefer `findBy` over `waitFor` in Jest tests because `findBy` queries automatically wait for elements to appear in the DOM. Adhering to this critical testing rule prevents flaky tests and simplifies asynchronous DOM testing logic.

Unit tests isolate and verify individual functions or components, while integration tests evaluate multiple parts working together, such as a component interacting with the DOM. Both testing layers are essential, and you should use standard naming conventions to distinguish them.

Yes, webapp testing guidance covers snapshot testing alongside unit and integration tests. It provides best practices for configuring these tests to ensure they capture meaningful UI changes without becoming brittle or requiring constant manual updates.