Skip to content

14.3 Performance Validation

Sprint: Sprint 14 - Testing and Hardening
Feature ID: 14.3
Subtasks: 14.3.1, 14.3.2

Objective

Deliver "Performance Validation" within Sprint 14 - Testing and Hardening.

Dependencies

Aggregated from the subtasks below (prerequisite task IDs and enablers):

  • 13.3.2
  • 11.3.2

Subtasks

14.3.1 API latency load test (NFR-01)

  • ID: 14.3.1
  • Title: Validate p95 API latency < 300ms under load
  • Description: A load test (k6/Gatling) exercising representative read/write endpoints through the gateway, asserting p95 < 300ms at the target concurrency (NFR-01).
  • Business Purpose: Meet the latency SLO (NFR-01).
  • Inputs: NFR-01.
  • Outputs: Load test scripts + report.
  • Acceptance Criteria:
  • p95 latency for the tested endpoints is < 300ms at target load; results are recorded in the dashboard.
  • Dependencies: 13.3.2
  • Complexity: M

14.3.2 Bill-run throughput test (NFR-02)

  • ID: 14.3.2
  • Title: Validate bill-run for 100K subscribers < 30 minutes
  • Description: Seed 100K active postpaid subscribers and measure a full bill-run, tuning batching/ parallelism to meet the target (NFR-02).
  • Business Purpose: Meet the bill-run throughput SLO (NFR-02).
  • Inputs: NFR-02, 11.3.2.
  • Outputs: Seed harness + bill-run performance report.
  • Acceptance Criteria:
  • A 100K-subscriber bill-run completes in under 30 minutes with no duplicate invoices.
  • Dependencies: 11.3.2
  • Complexity: L

Acceptance Criteria

Each subtask above carries its own objective, testable acceptance criteria. This feature is complete when every subtask's acceptance criteria are met.

Deliverables

  • Load test scripts + report.
  • Seed harness + bill-run performance report.

Definition of Done

  • All subtasks (14.3.1, 14.3.2) completed and their acceptance criteria verified.
  • All listed dependencies satisfied.
  • Build and tests green per the global conventions in ../README.md (Section 3).