new-feature-checklist

To ensure test coverage for a new feature, verify backend unit, integration, and edge cases alongside frontend unit and role-based E2E flows. This process enforces quality standards across all layers and prompts documentation updates for new user flows.

You need a fake-data refresh after implementing changes that affect models, foreign keys, M2M relationships, serializers, forms, or domain logic. This refresh workflow prevents existing test data from becoming incoherent with updated business rules and validations.

The correct execution order for running tests requires executing new tests first, followed by regression tests. This specific sequence ensures newly implemented logic is validated before verifying that existing application behaviors remain unaffected.

To generate valid fake data aligned to business rules, update factories and fixtures to exercise model validations, constraints, and foreign key dependencies. This ensures generated scenarios are coherent and properly reflect realistic domain logic.

Yes, this test coverage checklist works with Vue and Django law-firm management app changes. It specifically targets factories, serializers, model fields, status transitions, and frontend E2E role-based flows within this technology stack.