Leave UI Testing Guide

Summary

Testing should cover both employee ESS and legacy/admin renderings and verify gateway parity without assuming extracted-service ownership.

Audience

QA engineers, frontend/backend developers, support, and implementation partners.

Overview

Verify route access and deep links; employee request/history; legacy request listing, filters, details, application, conflict checks, decisions, cancellation, and balances; holiday and weekly-off maintenance; API failures; and unauthorized/module-unavailable states.

Also test date-order and joining-date validation, server-side day calculation, Attendance conflict outcomes, Workflow-enabled behavior where configured, gateway compatibility parity, narrow layouts, keyboard operation, modal focus, labels, and error announcement.

No dedicated Leave frontend test file was found by source inventory. The backend smoke script covers integration behavior rather than browser rendering. Automated UI coverage is therefore Foundation / Requires confirmation.

Use sanitized test tenants and synthetic records only. Capture route, client rendering selected, safe correlation evidence, expected/actual state, and browser viewport. Do not capture personal Leave reasons or balances.

Source References

• UI/salary-ui/apps/client-hrms-portal/src/App.tsx
• UI/salary-ui/apps/client-hrms-portal/src/pages/hr/PayrollFeaturePages.tsx
• UI/salary-ui/apps/client-hrms-portal/src/ess/EssPages.tsx
• microservices/scripts/smoke-leave.ps1

Related Articles

• Leave UI
• Leave API

See Also

• Leave business documentation
• Leave technical documentation

Keywords

• Leave UI
• Leave UI Testing Guide
• Workforce management

Revision Information

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