Update Test & Coverage Strategy Wiki — Document M7 Implementation

[CaganIslam]

Description

Update the existing Test and Coverage Strategy wiki page to reflect how the strategy was actually implemented in M7.

What to Add

• Summary of original test strategy (unit, integration, API, UI, mock data)
• How each layer was implemented in practice:
  • Backend: Django manage.py test + coverage.py (not pytest as originally planned)
  • Frontend: Jest + React Testing Library (as planned)
  • Mobile: Jest + React Native Testing Library (new — not in original doc)
  • E2E: Manual cross-platform checklist (Cypress/Playwright not adopted)
• Updated tool table with actual tools used vs originally planned
• Coverage results per layer (backend, frontend, mobile) with percentages
• How mock data strategy was implemented (seed_canonical command, MSW for frontend isolation)
• New acceptance criteria for M7 features (map discovery, explore/events, messaging, cultural content, onboarding personalization)
• Link to related M7 issues: Backend Unit Test Coverage — Gap Analysis & New Tests #530, Frontend Unit Test Coverage — Complete Missing Tests #531, Mobile Test Infrastructure Setup — Jest + React Native Testing Library #532, Mobile Unit Tests — Screen, Service, Component, Utility #533, Coverage Reporting — CI Pipeline + Wiki Documentation #534, Full Integration Test — API Contract + Cross-Platform E2E Verification #535, Test Results Report & Coverage Wiki Page #536

References

• Original wiki page: Test and Coverage Strategy
• M7 test issues: Backend Unit Test Coverage — Gap Analysis & New Tests #530–Test Results Report & Coverage Wiki Page #536

[CaganIslam]

added reports to the wikipage @laternis can you check