Skip to content

M2-14 Test Evidence (D4a)

Milestone: M2 — Platform and Client Admin SOW Reference: Deliverable D4a Requirement Clarity: ✅ Clear Dev Status: ❌ Not started — the earlier codebase review found only one backend unit-test file in the entire repository and zero frontend tests

Overview

Produce the Test Evidence deliverable for M2's scope: test results, logs, and defect summary, sufficient to demonstrate the Appendix 3 Testing Approach (Unit Testing, Integration Testing) was actually carried out.

Tasks

  • Write unit tests for M2 services (KYB, Registrar integration, branding, user management, RBAC)
  • Write integration tests for the Velocity Registrar API integration
  • Produce test summary/logs and a defect log per Appendix 3

Dependencies

  • Runs alongside all M2 build tasks, not after — per Appendix 6 Development Standards, "Implement automated unit and integration testing" is a delivery standard, not a one-off milestone task.

Acceptance Criteria

  • Test evidence complete and traceable to scope (per SOW Appendix 3, D4a — Test summary/logs, reviewed by Curo)

Existing Reference Material

None — confirmed gap in the current codebase (near-zero automated test coverage as of the last review).

Blockers & Risks

  • Risk: given the current near-total absence of test coverage, this deliverable requires a real investment of effort, not just documentation of tests that already exist.