Skip to content

M10-06 Regression Testing & Defect Remediation Post-Beta

Milestone: M10 — Deployment / Go-Live and Handover SOW Reference: SOW "End User Beta Programme and Final Acceptance" section Requirement Clarity: ✅ Clear Dev Status: ⚪ Not started

Overview

Following any remedial release during the Beta Programme, Curo has 5 Business Days to run regression testing to confirm defects were fixed and nothing new broke. Repeat as needed.

Tasks

  • Support Curo's regression testing window after each remedial release
  • Promptly remedy any further Critical/High-Priority defects found during regression and provide an updated release

Dependencies

Acceptance Criteria

  • Successful completion of all agreed regression testing (per SOW, "End User Beta Programme and Final Acceptance")

Existing Reference Material

  • SOW, "End User Beta Programme and Final Acceptance" section

Blockers & Risks

  • Note: given the current near-total absence of automated test coverage across the codebase, this manual regression cycle could take longer than planned — worth investing in automated regression tests well before this point (ideally starting at M3, per the general testing gap noted throughout).