Expense UI Testing Guide

Summary

No dedicated automated Expense frontend test file is confirmed. Existing evidence is source inspection plus backend smoke/parity automation.

Existing evidence and safe test scope

Area	Existing evidence	Gap
ESS list/create	Implemented component and gateway endpoints	No dedicated component/E2E test
Compatibility list/approve/reject	Implemented shared page	No Expense-specific frontend automation
Loading/empty/error	Source-defined states	Visual and accessibility assertions absent
Receipts	Disabled controls	No UI flow
Paid/details/history	No screen	Not testable as UI
Backend lifecycle	Expense smoke script	Does not exercise browser UI
Compatibility	Parity script	Does not prove navigation/permissions

Manual verification should use synthetic claims, approved test environments, and supported APIs. Verify navigation visibility, direct-route outcome, list/create states, pending decisions, error display, and that unsupported actions are absent. Do not use production data or receipt content.

Requires confirmation

Frontend test framework ownership, browser matrix, accessibility tooling, visual-regression policy, and release gates require confirmation.

Source References

• UI/salary-ui/apps/client-hrms-portal/src/ess/EssPages.tsx
• UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx
• UI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsx
• microservices/scripts/smoke-expense.ps1
• microservices/scripts/compare-expense-parity.ps1

Related Articles

• Expense UI documentation
• Expense business documentation
• Expense API documentation

See Also

• Expense technical documentation
• Expense module

Keywords

• Expense UI
• UI Testing Guide

Revision Information

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