Leave Testing Architecture

Summary

A comprehensive Leave smoke script exists, but no formal Leave-specific .NET test project was found.

Audience

Developers, QA, architects, and release engineers.

Overview

The smoke script covers direct and compatibility lifecycles, calendar and balance behavior, Attendance conflicts, Employee profile synchronization, optional Workflow integration, shadow/toggle categories, and rollback route evidence. It is validation tooling, not a substitute for automated unit/integration suites.

Recommended tests not confirmed as existing:

• LeaveDayCalculator unit cases for date order, exclusions, and half day
• Aggregate transition and event tests
• Balance transition/invariant tests
• Repository, tenant-filter, and local transaction integration tests
• Attendance unavailability/conflict contract tests
• Workflow start, managed-decision, callback, duplicate, and stale-state tests
• Outbox mapping/publication and Employee consumer idempotency/staleness tests
• Payroll/Notification consumer contract tests
• Gateway direct/compatibility/shadow tests
• Carry-forward/encashment foundation tests that prevent accidental claims of completeness

Test data must be synthetic and tenant-isolated.

Source References

• microservices/scripts/smoke-leave.ps1
• microservices/src/leave-service/Domain/Leave/LeaveDayCalculator.cs
• microservices/src/leave-service/Domain/Leave/LeaveRequest.cs

Related Articles

• Technical overview
• Known limitations

See Also

• Leave business documentation
• Leave overview

Keywords

• Leave Service
• Leave Testing Architecture
• Technical architecture

Revision Information

• Status: Draft
• Last reviewed: 2026-07-15
• Review cycle: Quarterly