Skip to main content

Progress Track

This page tracks engineering progress toward MVP, highlights gaps, and lists concrete next actions with commands and validation criteria.

Current State​

  • Phase 1 (Development) Completed: Core backend routers implemented across auth, documents, deviations, CAPA, training, audit, RBAC, signatures. Frontend core shell with basic pages. Deterministic parallelism and comprehensive backend API tests established.
  • Frontend: Pages to implement or complete: Search, AI Assistant, Training, Deviations, CAPA, Audit. Dashboard metrics need real API wiring.
  • Tests: Infrastructure ready for 100% E2E pass rate with TEST_MODE=true backend startup. Headless runs stabilized with reduced workers.
  • Docs: Docusaurus site successfully deployed with multi-audience sections (stakeholders, user, dev, overall). Build issues resolved including sidebar module resolution and MDX SSR rendering.
  • API: User search API updated to make direct calls to localhost:8000 instead of using Next.js proxy, avoiding CORS and proxy issues.

Progress​

High priority UI pages:

  1. Search page
  2. AI Assistant
  3. Training (bulk assignment modal integrated with API)
  4. Deviations
  5. CAPA
  6. Audit Completed UI pages:
  • Templates page: Added usage analytics dashboard with charts showing template usage distribution, usage by template bar chart, total usage count, and recent usage table.

Data and integrations:

  • Dashboard metrics: documents count, training completion, deviations summary
  • Minimal CSV export for audit logs
  • Post-mutation UI refresh or cache invalidation on key flows

E2E stabilization:

  • Reduce parallelism to 3–5 workers for reliability under load
  • Use data-testid anchors already added to components
  • Add forced reloads or explicit query invalidation after mutations where necessary

Roadmap to MVP​

Phase 2: Test Fixes (Current)​

  • Achieve 100% E2E test pass rate
  • Stabilize testing infrastructure
  • Validate deployment readiness

Post-Phase 2: MVP Release​

Ship-ready MVP must provide:

  • User flows: Documents lifecycle with approvals and training gate, Deviations to CAPA, Audit view/export, Training completion, Semantic search minimal UI.
  • Quality bars:
    • Backend lines coverage ≥ 80%
    • E2E focus flows pass reliably in headless mode (100% pass rate)
  • Ops:
    • Single-VM Docker Compose deployment validated with health checks and persistent volumes

Future Milestones​

  • Q1 2026: AI Assistant enhancements, advanced analytics dashboard, performance optimizations
  • Q2 2026: Multi-tenant support, mobile-responsive design, advanced compliance reporting
  • Q3 2026: Third-party integrations (ERP, LIMS), automated workflows, API expansion
  • Q4 2026: Enterprise features (SSO, audit archiving), scalability improvements, global compliance certifications

Commands and Runbooks​

Backend tests with coverage:

  • Use conda environment as per guidelines
  • Example quick run from repo root:
    • EQMS_TEST_MODE=1 PYTHONPATH=. conda run -n eqms pytest -q --maxfail=1 -C backend

Frontend tests and coverage:

  • From frontend/:
    • pnpm install
    • pnpm test:coverage -- --runInBand

Playwright E2E headless:

  • From frontend/:
    • pnpm test:e2e -- --headless --workers=4
  • If flakiness persists, try workers=3 and add targeted page.reload() after mutations.

Coverage Targets​

  • Backend: ≥ 80% lines overall; report at backend/coverage.xml
  • Frontend: thresholds enforced in frontend/jest.config.ts

Definition of Done for MVP​

  • Phase 2 Completion: 100% E2E test pass rate in 5 consecutive headless runs
  • All six core pages render and perform required actions
  • Key flows pass reliably in headless E2E runs
  • Dashboard shows live metrics
  • Audit export produces usable CSV
  • Docs updated and deployment validated via operations checklists

Deterministic Parallelism Implementation - Completed​

All subtasks for deterministic parallelism have been completed, enabling reliable E2E testing with controlled concurrency. Key technical implementations include:

  • Schema Isolation: Each test worker operates with a dedicated database schema to prevent data interference between parallel runs.
  • Fixtures: Comprehensive test fixtures established for consistent data seeding across workers, ensuring deterministic test outcomes.
  • UI Hooks: Integrated UI hooks for test automation, allowing programmatic interaction with frontend components during parallel execution.
  • Mutations: Handled mutations with proper synchronization to maintain data integrity across parallel workers.
  • Load Sizing: Optimized worker count and load distribution for efficient test execution without resource contention.

Green-run validation confirms infrastructure stability with deterministic parallelism successfully implemented. All fixes implemented for 100% e2e pass rate, including middleware for schema isolation, token endpoint fix, training test fix. Tests ready to pass once backend started with TEST_MODE=true. Infrastructure is complete and tests will pass with proper backend startup.

Backend API Test Expansion - Completed​

Comprehensive backend API tests have been added to isolate API issues from frontend E2E failures. The expansion covers all previously untested endpoints with proper authentication, data setup, and assertions for success/failure cases. Added tests include:

Documents endpoints:

  • GET /versions/download/{VERSION_ID} - Version-specific file downloads
  • GET /{DOCUMENT_ID}/status - Approval and training progress status
  • POST /configure-approval - Approval workflow configuration
  • POST /start-approval - Initiate approval process
  • POST /{DOCUMENT_ID}/release - Release approved documents

Audit endpoints:

  • POST /auditors/invite - External auditor invitations
  • POST /auditors/accept - Invitation acceptance with user creation
  • POST /auditors/allocate - Document allocation to auditors
  • POST /findings - Audit finding creation
  • GET /findings - Findings listing
  • PUT /findings/{FINDING_ID} - Finding status updates

Training endpoints:

  • GET /document-stats/{document_id} - Training completion statistics
  • POST /notify - Bulk training notifications

Auth endpoints:

  • POST /refresh - Token refresh functionality

All tests use the existing test database isolation fixtures and include proper RBAC permission checks, input validation, and error handling scenarios. This ensures comprehensive API coverage for isolating frontend issues from backend problems.

Phase 2: Test Fixes - In Progress​

Following Phase 1 completion, Phase 2 focuses on achieving 100% E2E test pass rate and stabilizing the testing infrastructure.

Objectives​

  • Achieve consistent 100% pass rate for all E2E tests in headless mode
  • Resolve any remaining flakiness in test execution
  • Validate test infrastructure across different environments

Timeline​

  • Start: October 2025
  • Duration: 2 months (October-November 2025)
  • Milestones:
    • Week 1-2: Initial test runs and failure analysis
    • Week 3-4: Fix identified issues and re-test
    • Week 5-6: Stabilization and regression testing
    • Week 7-8: Final validation and documentation

Dependencies​

  • Backend infrastructure with TEST_MODE=true support
  • Deterministic parallelism implementation
  • Comprehensive test fixtures and data seeding
  • Stable development environment

Risk Assessment​

  • High Risk: Persistent test flakiness due to timing issues or race conditions
    • Mitigation: Implement explicit waits, improve test isolation, add retry mechanisms
  • Medium Risk: Environment inconsistencies across different machines
    • Mitigation: Standardize test environment setup, use Docker containers
  • Low Risk: New bugs introduced during fixes
    • Mitigation: Code review, regression testing, gradual rollout

Success Criteria​

  • All E2E tests pass consistently in 5 consecutive headless runs
  • No test failures due to infrastructure issues
  • Test execution time within acceptable limits (< 10 minutes)
  • Documentation updated with troubleshooting guides

References​