Locator-healing playground

HRMS releases designed to break selectors without breaking workflows.

Each version simulates a fresh deployment of the same HRMS product. Screen hierarchy, labels, wrappers, and component arrangements change over time while the core workflows stay recognizable.

Build goals
Version-prefixed routes from `/v0/...` through `/v4/...`.
Delta-only release definitions so newer versions inherit prior screens.
Consistent product workflows with intentionally shifting locators.
A realistic enough shell for automation practice and demonstrations.
V0

Baseline operations suite

The original release uses straightforward headings, conventional navigation names, and stable card layouts.

Treat this release as the golden reference for selectors, semantics, and screen structure.

V1

Polished release candidate

This deployment keeps the same flows but introduces fresher wording, denser summaries, and more productized navigation cues.

Expect CTA and section naming changes while the route paths and workflow intent stay stable.

V2

Adaptive workspace refresh

The second follow-up deployment shifts the IA slightly, reframes employee content as people operations, and compresses descriptive copy.

Good candidate for navigation-label healing because multiple modules now use alternate naming.

V3

Locator-stress deployment

This release deliberately intensifies semantic and structural drift by regrouping content and using a punchier product voice.

Expected to break brittle selectors that depend on exact headings, action labels, or rigid card groupings.

V4

Mature multi-release simulator

The latest version sharpens the shell further, introduces more compact wording, and pushes the same workflows through a more modern product veneer.

Use this release as the strongest healing challenge before changing underlying data or APIs.

Module surface

The sample app spans the full HRMS navigation.

DashboardLoginEmployee ManagementDepartmentsLeave ManagementAttendancePayrollPerformance ReviewsDocumentsNotificationsSettingsAdmin

Suggested path

1. Start in `v0/dashboard`

Capture the baseline labels, headings, and component hierarchy.

2. Replay the same path in `v2`

Observe renamed navigation items and reorganized content blocks.

3. Stress-test on `v4`

Validate locator healing against stronger visual and structural drift.