test-data-factory

Register a custom Faker provider for healthcare fields like NPI numbers and clinical notes, then build factories that extend existing model factories. Composite scenario classes chain providers, clients, appointments, and payments into complete test fixtures.

Import existing factories from each app's tests conftest module and extend them rather than duplicating definitions. Use scenario classes like CompletedSessionScenario or BookingFunnelScenario to create full relationship chains in one call.

Yes, a custom Faker BaseProvider can generate NPI numbers that pass Luhn validation using the 80840 prefix per the CMS standard. Type 1 covers individual providers and type 2 covers organizational providers.

The PaymentMethodFactory is broken because it targets a TextChoices enum instead of a database model and references fields that do not exist on it. Do not use it; create StripeUserFactory records instead for payment-related test data.

Use safe provider methods that generate only @example.com emails, 555-prefix phone numbers, ocean coordinates, and clearly fake addresses. Run the seed data safety validation afterward to assert no real-looking values exist in the database.