Event Testing

Summary

This page records the verified Workforce Scheduling event boundary and its adjacent Attendance integration behavior.

Audience

Developers, integration engineers, QA engineers, operators, and solution architects.

Reference Content

No source test was found that names the Attendance lifecycle contracts, Attendance outbox relay, shared outbox processor, Integration dispatcher, or scheduling-event absence. No verified replay, ordering, duplicate-delivery, broker smoke, or scheduling notification test was found.

Implemented versus recommended

Implemented evidence	Recommended, not implemented
Typed contracts and persistence mappings	Contract serialization snapshots
Runtime outbox and consumer code	Transactional outbox integration tests
Integration idempotency store	Duplicate and crash-window tests
Retry/dead-letter code	Exhaustion, replay, and broker-unavailable tests
No scheduling event code	Explicit tests if scheduling contracts are introduced

Recommendations are documentation guidance only and must not be read as current behavior.

Source References

• microservices/src/contracts/Events/AttendanceLifecycleEvents.cs
• microservices/src/attendance-service/Infrastructure/AttendanceDbContext.cs
• microservices/src/shared-kernel/Messaging/OutboxProcessor.cs
• microservices/src/integration-service/Orchestration/EventDispatcher.cs
• microservices/src/notification-service/Application/EventNotificationResolver.cs

Related Articles

• Events overview
• Event limitations
• Event source map

See Also

• Technical documentation
• API documentation
• Database documentation

Keywords

• Workforce Scheduling events
• Attendance integration contracts
• Transactional outbox

Revision Information

• Status: Draft
• Last reviewed: 2026-07-20
• Next review: 2026-10-20