Skip to content

Coverage Gaps & Indicators

Ticket #107: Addition of test coverage indicators and gap identification
Type: Documentation / Quality Improvement
Affected Component: docs/tests/, docs/fr/tests/

1. Context

The automated test documentation lacked visibility into the actual state of coverage. It was difficult to quickly distinguish well-covered features from those needing urgent attention. Additionally, a deep analysis revealed several critical undocumented blind spots (gaps).

2. Objective

Make the state of quality explicit and visual directly within the documentation, and formalize the missing tests (gaps) identified during the audit.

3. Actions Taken

  • Full Test Audit: Cross-analysis of source code (tests/*.py) and documentation to identify gaps.
  • Added Gaps (To Do): Integrated new test cases with "To Do" status into existing pages:
  • Authentication: User management (Admin), E2E Scenarios, Security.
  • Pipeline: API Resilience (Timeout/500), Data Integrity (UPSERT).
  • UI/UX: Mobile responsive design.
  • Visual Indicators: Added dynamic progress bars (geps.dev) to each report page:
  • Rate by feature (e.g., Dashboard 83%).
  • Global project rate on the home page (70%).

4. Result

The documentation now provides a transparent and quantified view of quality: - Authentication: 63% - Dashboard: 83% - Pipeline: 42% - Demo: 75% - Stock Detail: 100% - GLOBAL: 70%

5. Next Steps

  • Implement the tests identified as "To Do" to increase these percentages.
  • Create a dedicated page for testing the documentation site itself (Future ticket).