Skip to content

14.1 Acceptance and End-to-End Testing

Sprint: Sprint 14 - Testing and Hardening
Feature ID: 14.1
Subtasks: 14.1.1, 14.1.2, 14.1.3

Objective

Deliver "Acceptance and End-to-End Testing" within Sprint 14 - Testing and Hardening.

Dependencies

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

  • 9.5.2
  • 10.7.1
  • 11.6.1
  • 12.6.1
  • 3.3.2
  • Sprints 06-12
  • 1.4.1

Subtasks

14.1.1 Full acceptance suite (AC-01, AC-02, AC-03)

  • ID: 14.1.1
  • Title: Build a cross-service acceptance test suite
  • Description: An automated end-to-end suite (Testcontainers or compose-based) running all three acceptance scenarios against the full service set through the gateway, including failure/ compensation variants.
  • Business Purpose: Prove the MVP delivers its committed business outcomes (AC-01/02/03).
  • Inputs: requirements Section 5 (AC-01/02/03), Sprints 09/10/11/12.
  • Outputs: Acceptance test suite + CI stage.
  • Acceptance Criteria:
  • AC-01, AC-02, AC-03 all pass through the gateway end to end, including AC-01 compensation; the suite runs in CI.
  • Dependencies: 9.5.2, 10.7.1, 11.6.1, 12.6.1
  • Complexity: L

14.1.2 Contract tests for events and APIs

  • ID: 14.1.2
  • Title: Add event-schema and API contract tests
  • Description: Producer/consumer contract tests for each Avro event (schema-registry backward compatibility, required fields) and API contract tests for cross-service Feign calls, preventing breaking changes (NFR-16).
  • Business Purpose: Lock service boundaries against accidental breakage (NFR-16).
  • Inputs: ADR-019, NFR-16, event-catalog.
  • Outputs: Contract test suite.
  • Acceptance Criteria:
  • A breaking event/API change fails a contract test; all current contracts pass.
  • Dependencies: 3.3.2, Sprints 06-12
  • Complexity: M

14.1.3 Coverage gate

  • ID: 14.1.3
  • Title: Enforce minimum test coverage in CI
  • Description: Configure JaCoCo coverage thresholds per module bound to CI; merges blocked below the agreed threshold (NFR-17).
  • Business Purpose: Sustained test discipline (NFR-17).
  • Inputs: ADR-013, NFR-17.
  • Outputs: Coverage config + CI gate.
  • Acceptance Criteria:
  • CI fails a PR that drops a module below its coverage threshold.
  • Dependencies: 1.4.1
  • Complexity: S

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

  • Acceptance test suite + CI stage.
  • Contract test suite.
  • Coverage config + CI gate.

Definition of Done

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