The job of this console
Prove a policy change before employees feel it. Build a scenario, run a batch, compare with last time, then publish in Policy Center only if the lab is green.
HRMS · Leave
Leave Policy Test Lab
Register view for policy scenarios, batch runs, and regression compares — create/run via forms when available, or API.
Register view — create/update via forms when available, or API. Flowcharts: scenario → simulate → compare.
Dry run
Scenarios, batch runs, and regression compares
Policy Test Lab is the register for policy scenarios, batch runs, and regression compares. Create and run via forms when available, or API. It never writes a real leave request.
Admin → Policy test lab
Route
/admin/leave/policy-test-lab
HR Admin · Org Admin
Seat at the table
HR administrators and implementation partners. Employees never see the lab.
The working rhythm
Pick or create a scenario, run, read diffs, adjust policy, run again. Keep fixtures, do not point the lab at production employees as a side effect.
Moments that bring you here
Before publishing a statutory change. After a CFA mapping. A regression after upgrade. When a proof apply in runtime is too risky.
ⓘ
Simulation only
Lab runs are not leave records. Publish still happens in Global Policy Center.
Flowcharts
Each diagram auto-plays steps when it scrolls into view. Use Play / Pause, or click a step to jump.
1 — Test lab loop
Pick policy version, run scenarios, inspect results, fix rules.
flowchart TD
S[Select policy version] --> T[Define scenario]
T --> R[Run simulation]
R --> V{Pass?}
V -->|No| Fix[Adjust rules]
Fix --> T
V -->|Yes| Ready[Ready to publish]
- 1Select policy versionChoose DRAFT or published version under test.
- 2Define scenarioEmployee, leave type, dates, tenure assumptions.
- 3Run simulationResolve accrual, eligibility, and day count.
- 4Pass?Compare expected vs actual outcomes.
- 5Adjust rulesEdit accrual/eligibility JSON and retest.
- 6Ready to publishPromote version when scenarios pass.
2 — What the lab exercises
Resolver paths covered by a typical lab session.
flowchart TD
Lab[Test lab] --> Acc[Accrual]
Lab --> Elig[Eligibility]
Lab --> Days[Working days]
Lab --> Bal[Balance preview]
- 1Test labSingle console for dry-run resolve.
- 2AccrualScheduled grant amounts under version rules.
- 3EligibilityTenure, probation, type gates.
- 4Working daysDay count with calendars and overrides.
- 5Balance previewWhat the employee would see after apply.
Overview
Policy Test Lab validates Global Leave policy versions without touching live balances. Screens are primarily registers for scenarios and results; create/run via forms when available, or API. Prefer lab coverage before Publish in Policy Center.
How to use
1. Open Policy Test Lab
Admin → Leave → Policy test lab.
2. Review scenarios
Inspect the scenario register; create/update via forms when available, or API.
3. Inspect batch / regression
Review run results and compare output when seeded.
4. Publish from Policy Center
Return to Policy Center to publish when scenarios pass the gate.