Leave Smoke Testing

Summary

The repository includes a Leave smoke script for direct service flows, compatibility paths, synchronization, dependency behavior, and gateway routing.

Audience

QA, DevOps/SRE, backend developers, support, and release approvers.

Overview

Use the script only in an approved non-production or explicitly authorized safe environment with synthetic tenant/employee data and separately managed credentials. Do not publish invocation values.

Confirmed source inspection shows coverage for service availability and representative Leave behavior, including direct/compatibility concerns, Attendance conflict validation, employee synchronization, optional Workflow paths, and gateway routing where prerequisites are enabled. Exact exercised branches depend on available environment capabilities.

Expected evidence is pass/fail output, safe correlation data, resulting non-sensitive statuses, and relevant service signals. The script does not prove browser behavior, production readiness, full authorization parity, all policy fields, consumer completion, or data reconciliation at scale.

Escalate by the failing boundary: Leave, gateway, Employee, Attendance, Workflow, messaging, or database owner.

Source References

• microservices/scripts/smoke-leave.ps1
• microservices/src/gateway-api/Program.cs
• microservices/src/leave-service/Api/LeaveEndpoints.cs

Related Articles

• Leave Operations
• Leave technical documentation

See Also

• Leave events
• Leave troubleshooting

Keywords

• Leave operations
• Leave Smoke Testing
• Service support

Revision Information

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