Performance Integration Testing Guide
Summary
The existing smoke script covers lifecycle outbox evidence, Workflow duplication, Notification resolution/dispatch evidence, compatibility, gateway coexistence, and backfill/parity. No dedicated Performance test project, request collection, or broker-specific contract suite was found.
| Layer | Safe coverage |
|---|---|
| Unit | Event creation and verified absence |
| Persistence | Mapping, atomicity, schema/context |
| Contract | Serialization and additive compatibility |
| Broker integration | Isolated publication failure/recovery |
| Consumer | Duplicate, staleness, missing recipient |
| Workflow | Separate start/callback and duplicate callback |
| Notification | Seven resolver mappings and failure outcomes |
| Compatibility/backfill | Event absence, dry-run, resume, parity |
| End-to-end/smoke | Eventual propagation in non-production |
Recommended assertions include seven mappings, zero unmapped events, rollback atomicity, version 1, duplicate suppression, compatibility absence, and recorded failures. Current correlation tests should assert its verified absence. Replay/cutover coverage remains recommended, not implemented.
Requires confirmation
Operational ownership, service objectives, reconciliation, replay, and future consumer governance require confirmation where not explicitly implemented.
Source References
microservices/scripts/smoke-performance.ps1microservices/src/performance-service/Infrastructure/PerformanceDbContext.csmicroservices/src/notification-service/Application/EventNotificationResolver.cs
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly