12.6 Tests¶
Sprint: Sprint 12 - Notifications and Ticketing
Feature ID: 12.6
Subtasks: 12.6.1
Objective¶
Deliver "Tests" within Sprint 12 - Notifications and Ticketing.
Dependencies¶
Aggregated from the subtasks below (prerequisite task IDs and enablers):
- 12.3.1
- 12.5.3
- 12.5.4
Subtasks¶
12.6.1 Notification and ticket integration tests¶
- ID: 12.6.1
- Title: Add notification/ticket integration tests (Testcontainers)
- Description: Testcontainers (MongoDB + Postgres for notification, Postgres for ticket, Kafka) tests covering event-to-notification dispatch with preference suppression and idempotency, template rendering, ticket open/assign/resolve with events, and SLA breach. Verify AC-01 welcome SMS, AC-02 invoice email, and AC-03 threshold SMS now dispatch.
- Business Purpose: Verify engagement and support domains (NFR-17).
- Inputs: 12.3, 12.5.
- Outputs: Integration test suites for both services.
- Acceptance Criteria:
- FR-28..33 flows pass; opted-out users are suppressed; ticket open notifies the customer; the AC-01/02/03 notification steps are confirmed dispatched.
- Dependencies: 12.3.1, 12.5.3, 12.5.4
- 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¶
- Integration test suites for both services.
Definition of Done¶
- All subtasks (12.6.1) completed and their acceptance criteria verified.
- All listed dependencies satisfied.
- Build and tests green per the global conventions in ../README.md (Section 3).