test-fixtures

Unit test fixtures should be organized into resource directories under test/unit/resources, sanitized to remove PII by substituting realistic placeholder values, and formatted with 2-space JSON indentation to ensure reliable and maintainable tests.

Mocking HTTP requests with nock involves loading sanitized JSON fixtures from your test/unit/resources directory and configuring nock interceptors to return those fixtures as mock API responses during unit tests.

The best way to structure test fixtures for backend services is grouping files by resource under test/unit/resources, enforcing mockResponse*.json and mockError*.json naming conventions, and validating data shapes to accurately reflect real API responses.

Validating data shapes in API mock responses involves checking loaded JSON fixtures against expected schemas, ensuring the sanitized test fixtures maintain the correct structure required for reliable fixture-driven unit tests.

Yes, you can use existing JSON files with nock-based mocks by loading them from the test/unit/resources directory, ensuring they follow the mockResponse*.json naming convention, and passing the data directly into nock interceptors.

Unit tests fail when API fixtures contain PII because sensitive data breaks sanitization requirements. Sanitizing fixtures by replacing PII with realistic placeholder values ensures tests remain reliable and compliant.