django-verification

Topics in the source

• Django Verification Loop
• When to Activate
• Phase 1: Environment Check
• Phase 2: Code Quality & Formatting
• Phase 3: Migrations
• Phase 4: Tests + Coverage
• Phase 5: Security Scan
• Phase 6: Django Management Commands

Run before PRs, after major changes, and pre-deploy to ensure Django application quality and security. Before opening a pull request for a Django project After major model changes, migration updates, or dependency upgrades Pre-deployment verification for staging or production Running full environment → lint → test → security → deploy readiness pipeline Validating migration safety and test coverage If environment is misconfigured, stop and fix. Common issues: Missing type hints on public functions PEP 8 formatting violations Unsorted imports Debug settings left in production configuration Report: Number of pending migrations Any migration conflicts Model changes without migrations Report: Total tests: X passed, Y failed, Z skipped Overall coverage: XX% Per-app coverage breakdown Coverage targets: | Component | Target | |-----------|--------| | Models | 90%+ | | Serializers | 85%+ | | Views | 80%+ | | Services | 90%+ | | Overall | 80%+ | Report: Vulnerable dependencies found Security configuration issues Hardcoded secrets detected DEBUG mode status (should be False in production) Report: Number of queries per page (should be < 50 for typical pages) Missing database indexes Duplicate

This is an excerpt. Refer to the complete source and its current requirements.