feat(Dashboard): add Deductions block to the Job and Pay tab#1872
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds deductions management to the Employee Dashboard’s Job and Pay tab and wires it into the existing dashboard flow/state machine.
Changes:
- Adds dashboard deductions listing, add/edit/delete actions, delete confirmation, and success alerts.
- Introduces dashboard state transitions and contextual form mounting for deduction create/edit.
- Updates related i18n strings/types and adjusts the standalone deductions empty-state layout wrapper.
Reviewed changes
Copilot reviewed 11 out of 12 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
src/types/i18next.d.ts |
Adds typed dashboard and deductions translation keys. |
src/i18n/en/Employee.Deductions.json |
Adds delete dialog copy. |
src/i18n/en/Employee.Dashboard.json |
Adds dashboard deduction labels and success alerts. |
src/components/Employee/Deductions/shared/useDeleteDeduction.ts |
Adds pending-delete helper hook. |
src/components/Employee/Deductions/shared/index.ts |
Exports new shared deduction delete utilities. |
src/components/Employee/Deductions/shared/DeleteDeductionDialog.tsx |
Adds confirmation dialog for deleting deductions. |
src/components/Employee/Deductions/deductionsContextualComponents.tsx |
Wraps include step in BaseLayout for layout consistency. |
src/components/Employee/Dashboard/JobAndPayView.tsx |
Adds deductions fetching, rendering, actions, and delete dialog to Job and Pay. |
src/components/Employee/Dashboard/hooks/useEmployeeCompensation.tsx |
Removes garnishments from compensation hook data. |
src/components/Employee/Dashboard/dashboardStateMachine.ts |
Adds deduction form state and dashboard deduction transitions. |
src/components/Employee/Dashboard/DashboardComponents.tsx |
Adds dashboard deduction form contextual component and alerts. |
src/components/Employee/Dashboard/Dashboard.tsx |
Wires deduction add/edit handlers into Job and Pay view. |
Comment on lines
+155
to
+157
| transition( | ||
| componentEvents.EMPLOYEE_DEDUCTION_ADD, | ||
| 'deductionForm', |
|
Outdated Review:Fresh Eyes ReviewFound 1 issue in this PR. Info (1)
Download findings.json — drag the file into Claude or use Please 👍🏽 👎🏽 if you found this useful. Generated by Fresh Eyes Reviewer. Get help in #ai-code-reviews |
jeffredodd
approved these changes
May 20, 2026
The empty-state CTA rendered into a ~200px column even though the
parent had 1189px of available width. Verified via Playwright against
the SDK dev app at /employee/Deductions.
Root cause: Flow's outer Flex is flex-direction:row (default) with one
child column-flex. Without a child that declares width:100%, the
column-flex sizes to its content's intrinsic width — which for the
empty-state's narrow text means every word wraps to its own line.
DocumentSigner doesn't show this bug because DocumentList wraps its
content in <BaseComponent>, which renders <BaseLayout>/<FadeIn
width:100%>. That FadeIn is the width anchor. The list and form
contextuals here already use <BaseLayout>; the include contextual
didn't because it has no per-view errors to surface. Adding it now —
the FadeIn anchor matters more than the error display.
Verified in browser: the heading, description, empty-state box, and
buttons all render at full content width. Form view ("Add deduction"
radio + garnishment-type picker) also renders correctly. Test suite
green.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Replaces the bare garnishments DataView in JobAndPayView with a fully
interactive Deductions block mirroring the PaymentMethod pattern: row-
level HamburgerMenu (Edit / Delete), a confirmation dialog backed by a
new useDeleteDeduction helper, and a DeleteDeductionDialog component.
The block sources its data from useDeductionsList (the existing hook —
its soft-delete action + remainingActiveCount return are reused as-is),
so the consumer drops the legacy garnishments fetch in
useEmployeeCompensation and JobAndPayView no longer takes a
garnishments prop.
Add / Edit / Delete events flow through the dashboardStateMachine the
same way the bank-account ones do:
- EMPLOYEE_DEDUCTION_ADD on the index state → deductionForm with no
editingDeductionId (create mode).
- EMPLOYEE_DEDUCTION_EDIT on the index state → deductionForm with
editingDeductionId set from the event payload (the DeductionsForm
picker pre-populates from the loaded row via the dedup-ed list
query).
- EMPLOYEE_DEDUCTION_DELETED on the index state → index with
successAlert: 'deductionDeleted'.
- EMPLOYEE_DEDUCTION_CREATED / UPDATED on deductionForm → index with
'deductionAdded' / 'deductionUpdated'.
- EMPLOYEE_DEDUCTION_CANCEL / CANCEL on deductionForm → index.
DeductionFormContextual mounts the DeductionsForm picker (chooses
between StandardDeductionForm and ChildSupportFormView) so the
Dashboard surfaces support both custom deductions and any
court-ordered garnishment type.
Also fixes a pre-existing rendering bug in the withheld column:
`amount` is a string per the API but the old branch checked
`typeof === 'number'` (never true) and fell back to printing
annualMaximum with a hardcoded '%'. The new column matches the legacy
DeductionsList — currency / percent via `deductAsPercentage`, with the
"{value} per paycheck" suffix for recurring rows.
Errors from both paymentMethodList and deductionsList are merged with
composeErrorHandler so the existing JobAndPayView BaseLayout surfaces
either hook's failure.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
When `useDeductionsList` (or `usePaymentMethodList`) fails before first
paint, the hook returns `isLoading: true` with populated `errorHandling.errors`.
The early `<Loading />` swallowed those errors, leaving the Job and Pay
tab in a permanent skeleton state instead of showing a retry alert.
Replace with `<BaseLayout isLoading error={errorHandling.errors} />` so
the existing error surface handles the failure.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…d tests Pulls the currency/percent/per-paycheck branching that lived in both JobAndPayView.tsx and DeductionsList.tsx into a single `formatDeductionAmount` helper, exported from `Deductions/shared/`. The per-paycheck suffix is injected as a `formatPerPaycheck` callback so each caller keeps its own i18n namespace (`Employee.Dashboard` vs `Employee.Deductions`). Adds: - `formatDeductionAmount.test.ts` — table-driven unit coverage of the one-time / recurring × fixed / percent matrix plus missing/non-numeric amounts. - Job-and-pay Deductions integration tests in `Dashboard.test.tsx`: row rendering, EMPLOYEE_DEDUCTION_ADD, EMPLOYEE_DEDUCTION_EDIT, and a full confirm-delete flow asserting the PUT body and EMPLOYEE_DEDUCTION_DELETED payload. Fixes the `useContainerBreakpoints` mock to expose both the named and default exports — the previous mock broke as soon as a test navigated into the Job and Pay tab. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
cursor Bot
pushed a commit
that referenced
this pull request
May 20, 2026
* fix(Deductions): un-squash the IncludeDeductions view inside Flow
The empty-state CTA rendered into a ~200px column even though the
parent had 1189px of available width. Verified via Playwright against
the SDK dev app at /employee/Deductions.
Root cause: Flow's outer Flex is flex-direction:row (default) with one
child column-flex. Without a child that declares width:100%, the
column-flex sizes to its content's intrinsic width — which for the
empty-state's narrow text means every word wraps to its own line.
DocumentSigner doesn't show this bug because DocumentList wraps its
content in <BaseComponent>, which renders <BaseLayout>/<FadeIn
width:100%>. That FadeIn is the width anchor. The list and form
contextuals here already use <BaseLayout>; the include contextual
didn't because it has no per-view errors to surface. Adding it now —
the FadeIn anchor matters more than the error display.
Verified in browser: the heading, description, empty-state box, and
buttons all render at full content width. Form view ("Add deduction"
radio + garnishment-type picker) also renders correctly. Test suite
green.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(Dashboard): wire Deductions block into JobAndPayView
Replaces the bare garnishments DataView in JobAndPayView with a fully
interactive Deductions block mirroring the PaymentMethod pattern: row-
level HamburgerMenu (Edit / Delete), a confirmation dialog backed by a
new useDeleteDeduction helper, and a DeleteDeductionDialog component.
The block sources its data from useDeductionsList (the existing hook —
its soft-delete action + remainingActiveCount return are reused as-is),
so the consumer drops the legacy garnishments fetch in
useEmployeeCompensation and JobAndPayView no longer takes a
garnishments prop.
Add / Edit / Delete events flow through the dashboardStateMachine the
same way the bank-account ones do:
- EMPLOYEE_DEDUCTION_ADD on the index state → deductionForm with no
editingDeductionId (create mode).
- EMPLOYEE_DEDUCTION_EDIT on the index state → deductionForm with
editingDeductionId set from the event payload (the DeductionsForm
picker pre-populates from the loaded row via the dedup-ed list
query).
- EMPLOYEE_DEDUCTION_DELETED on the index state → index with
successAlert: 'deductionDeleted'.
- EMPLOYEE_DEDUCTION_CREATED / UPDATED on deductionForm → index with
'deductionAdded' / 'deductionUpdated'.
- EMPLOYEE_DEDUCTION_CANCEL / CANCEL on deductionForm → index.
DeductionFormContextual mounts the DeductionsForm picker (chooses
between StandardDeductionForm and ChildSupportFormView) so the
Dashboard surfaces support both custom deductions and any
court-ordered garnishment type.
Also fixes a pre-existing rendering bug in the withheld column:
`amount` is a string per the API but the old branch checked
`typeof === 'number'` (never true) and fell back to printing
annualMaximum with a hardcoded '%'. The new column matches the legacy
DeductionsList — currency / percent via `deductAsPercentage`, with the
"{value} per paycheck" suffix for recurring rows.
Errors from both paymentMethodList and deductionsList are merged with
composeErrorHandler so the existing JobAndPayView BaseLayout surfaces
either hook's failure.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(Dashboard): surface deductions errors through the loading gate
When `useDeductionsList` (or `usePaymentMethodList`) fails before first
paint, the hook returns `isLoading: true` with populated `errorHandling.errors`.
The early `<Loading />` swallowed those errors, leaving the Job and Pay
tab in a permanent skeleton state instead of showing a retry alert.
Replace with `<BaseLayout isLoading error={errorHandling.errors} />` so
the existing error surface handles the failure.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* refactor(Deductions): extract shared formatDeductionAmount + dashboard tests
Pulls the currency/percent/per-paycheck branching that lived in both
JobAndPayView.tsx and DeductionsList.tsx into a single
`formatDeductionAmount` helper, exported from `Deductions/shared/`. The
per-paycheck suffix is injected as a `formatPerPaycheck` callback so each
caller keeps its own i18n namespace (`Employee.Dashboard` vs
`Employee.Deductions`).
Adds:
- `formatDeductionAmount.test.ts` — table-driven unit coverage of the
one-time / recurring × fixed / percent matrix plus missing/non-numeric
amounts.
- Job-and-pay Deductions integration tests in `Dashboard.test.tsx`:
row rendering, EMPLOYEE_DEDUCTION_ADD, EMPLOYEE_DEDUCTION_EDIT, and a
full confirm-delete flow asserting the PUT body and
EMPLOYEE_DEDUCTION_DELETED payload.
Fixes the `useContainerBreakpoints` mock to expose both the named and
default exports — the previous mock broke as soon as a test navigated
into the Job and Pay tab.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
jeffredodd
added a commit
that referenced
this pull request
May 21, 2026
* feat(e2e): add scenario JSON schema, fragments, and validator
Foundation for the per-domain scenario-driven E2E rebuild.
- e2e/scenarios/schema/scenario.schema.json — full scenario definition
covering locations, employees, contractors, paySchedule, payrolls;
fragment refs with overrides; templated strings
- e2e/scenarios/schema/scenario.types.ts — generated TS types via
json-schema-to-typescript
- e2e/scenarios/fragments/ — w2-salaried, w2-hourly, contractor-1099
- e2e/scenarios/payroll/example-minimal.json — loader reference fixture
- e2e/scenarios/scripts/validate.mjs — ajv-based standalone validator
- npm scripts: scenarios:types (codegen), scenarios:validate
Implements Notion tasks #007-#010 (Phase A foundation). First PR in the
16-PR draft stack for the E2E overhaul + API upgrade initiative.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(e2e): scenario loader — $ref resolution, overrides, templates
Implements Phase A tasks #011-#014: the deterministic loader that turns a
scenario JSON file into a provisioning-ready Scenario object.
- e2e/scenario/loader.ts — public API: resolveScenario (fragments + overrides,
templates intact, used as the hash input) and loadScenario (full pipeline:
resolve + applyTemplates + ajv schema-validate)
- Deep merge semantics: arrays REPLACE, objects merge recursively. \$ref
sibling fields and \`overrides\` both layer onto the resolved fragment;
overrides win. Cycle detection via \$ref stack.
- Template grammar: {{ts}} (injectable timestamp; defaults to Date.now())
and {{relative:+Nd[:DayName]}} (UTC date arithmetic; optional next-weekday
advance). Unknown tokens throw rather than silently passing through.
- e2e/scenario/loader.test.ts — 12 cases: deepMerge rules, template grammar,
resolution against the committed example-minimal.json, synthesized cycle
+ override + bad-schema fixtures via mkdtempSync.
- vitest.scenario.config.ts + package.json: scenario tests run via
\`npm run test:scenarios\` (separate from the main vitest run, which still
excludes e2e/**). Node environment, no globals.
Second PR in the 16-PR stack for the E2E overhaul + API upgrade initiative.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(e2e): scenario structural hash via canonical JSON + SHA-256
Implements Phase A task #015: the cache-key function that gives each
scenario a stable identity independent of object key ordering and
template substitution.
- e2e/scenario/hash.ts — canonicalize() sorts object keys recursively
(arrays preserve order since array order is semantically meaningful in
the scenario schema); hashScenarioStructure() SHA-256-hex over the
canonical form.
- Input is meant to be the output of resolveScenario (refs + overrides
applied, {{ts}}/templates intact). Hashing pre-substitution keeps the
hash stable across runs while still invalidating when an author edits
a referenced fragment.
- e2e/scenario/hash.test.ts — 6 cases pinning canonicalization rules,
key-order insensitivity, value-change sensitivity, array-order
significance, and the 64-char hex output shape.
Third PR in the 16-PR stack for the E2E overhaul + API upgrade
initiative. Sets up the cache key used by the next PR (cache).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(e2e): scenario infrastructure — cache, runner, decorations, fixture, reporter, scripts
Complete E2E scenario infrastructure for per-domain testing:
- Cache layer (e2e/scenario/cache.ts): atomic R/W, token validation, hit/miss logic
- Runner (e2e/scenario/runner.ts): provision demos, decorate entities (locations,
employees, addresses, jobs, compensation, onboarding, contractors, pay schedules,
payroll processing), validate expectedContext, cache results
- Fixture (e2e/utils/localTestFixture.ts): scenario fixture with @domain auto-tagging,
backwards-compatible with legacy localConfig path
- Reporter (e2e/reporters/scenario-reporter.ts): per-domain/scenario aggregation to
e2e/reports/results.json
- Scripts (e2e/scenario/scripts.ts): prewarm and clear CLI commands
- CI: upload e2e/reports/ artifact alongside playwright-report/
- Register scenario reporter in all 3 Playwright configs
- Add e2e:scenarios:prewarm and e2e:scenarios:clear npm scripts
- .gitignore: add .scenario-cache.json and e2e/reports/
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): stabilize scenario CI paths across msw and demo runs
Avoid remote scenario provisioning in MSW CI, make dismissal setup non-fatal in
global setup, and align runner mutations with current API requirements.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): normalize legacy onboarding status values in runner
Map legacy "completed" scenario values to "onboarding_completed" before
calling the API so demo provisioning remains compatible.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): avoid hard-failing on onboarding status API rejection
Treat onboarding-status decoration as best-effort so scenario provisioning can
continue when the API rejects completion on partially configured employees.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): make scenario payroll and URL overrides less brittle
Fallback to any unprocessed regular pay period when none are in the past and
preserve explicit employee/contractor query params in scenario-mode tests.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): tolerate payroll blockers during scenario seeding
Treat known payroll blocker errors during processed-payroll setup as non-fatal
so scenario provisioning can proceed in demo environments.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): include start_date and end_date when creating off-cycle payrolls
The gws-flows API now requires explicit start_date and end_date on the
off-cycle payroll create payload, even when the runner only knows the
check_date. Without these the request returns 422 and scenario
provisioning fails.
The runner now forwards explicit start_date/end_date from the scenario
JSON when present, and falls back to check_date (or today) so existing
scenarios keep working.
Co-authored-by: Cursor <cursoragent@cursor.com>
* ci(e2e): gate Playwright runs behind scenario validation
Add a fast 'scenarios' CI job that runs npm run scenarios:validate plus
npm run test:scenarios so a broken scenario JSON or scenario module
regresion fails the build immediately, before the much-slower MSW e2e
and demo e2e jobs spin up Playwright.
Both e2e and e2e-demo now depend on scenarios so a schema regression
short-circuits the chain.
Co-authored-by: Cursor <cursoragent@cursor.com>
* ci(e2e): drop MSW e2e job, keep e2e-demo as the only Playwright gate
The MSW e2e job was failing on tests that worked correctly against the
real demo backend, because MSW fixtures cannot mirror the full state
machine + form behavior the demo flow drives. Maintaining tolerant
fallbacks just to keep MSW happy was watering down assertions without
adding coverage that Storybook + unit tests don't already provide.
Removes the e2e job entirely. e2e-demo is now the only Playwright
gate. Adds an e2e-scenario-report-demo artifact upload so the
per-domain scenario report stays accessible in CI.
Saves roughly 2.5-3 min per branch per push and unblocks tests we
tightened in recent commits.
Co-authored-by: Cursor <cursoragent@cursor.com>
* ci(e2e): rename e2e-demo job to e2e (now the sole Playwright gate)
After removing the MSW-mode e2e job, the remaining job is the only
Playwright gate, so the -demo suffix is no longer informative.
Renames:
- job: e2e-demo -> e2e
- step: 'Run e2e tests against demo environment' -> 'Run e2e tests'
- step: 'Upload demo test results' -> 'Upload test results'
- step: 'Upload demo scenario reports' -> 'Upload scenario reports'
- artifact: playwright-report-demo -> playwright-report
- artifact: e2e-scenario-report-demo -> e2e-scenario-report
Also restores the e2e required status check on main branch
protection, which had been silently blocking PR merges since the
MSW job was removed (protection still required a check named e2e).
The npm script test:e2e:demo stays as-is locally so dev muscle memory
and pointer to the demo backend stay clear.
Co-authored-by: Cursor <cursoragent@cursor.com>
* ci(e2e): shard Playwright job by domain
Splits the single e2e job into a matrix with one entry per domain folder
under e2e/tests/. Each shard runs in parallel with fail-fast disabled,
so:
- one domain's failure no longer cancels the others' feedback
- total wall-clock drops from sequential single-worker runtime to the
slowest domain's runtime
- re-running just one failed domain is cheap (small CI re-spend)
Domains: company, contractor, dismissal, employee, information-requests,
payroll, termination, time-off, legacy.
Filter is a Playwright path substring so each shard picks up both flat
specs at e2e/tests/<domain>*.spec.ts and nested specs under
e2e/tests/<domain>/. --pass-with-no-tests keeps shards green on
branches where a domain folder hasn't materialized yet (e.g. infra
itself, where domain reorganizations still live on stacked PRs).
Artifact uploads are scoped per shard so playwright-report-<domain>
and e2e-scenario-report-<domain> don't collide.
Co-authored-by: Cursor <cursoragent@cursor.com>
* ci(e2e): throttle matrix to max-parallel 2 to avoid demo backend timeouts
Each e2e shard's globalSetup creates ~2 demo companies on
flows.gusto-demo.com (one primary onboarded company plus the dismissal
company). With the matrix expanded to 9 shards, all 9 ran simultaneously
and the demo backend couldn't keep up — flow-token lookup hit the 200s
timeout and 8/9 shards failed in the previous CI run on #1873.
max-parallel: 2 caps the concurrency so demo provisioning stays
manageable. Trades some wall-clock for reliability; one slow shard no
longer cascades into half the matrix failing on infrastructure load.
Co-authored-by: Cursor <cursoragent@cursor.com>
* ci(e2e): provision demo companies once via shared e2e-setup job
Replaces per-shard demo provisioning with a single upstream e2e-setup
job that publishes the resulting state as a CI artifact. The matrix
shards download that artifact, and globalSetup short-circuits when it
finds a valid e2e/.e2e-state.json on disk.
Changes:
- New e2e-setup CI job runs globalSetup once, uploads e2e-state
artifact (1 day retention)
- Matrix shards depend on e2e-setup, download the artifact before
running tests
- globalSetup gains an idempotency check: if .e2e-state.json exists
with a flowToken/companyId that the demo backend still accepts,
reuse it and skip ~3 minutes of provisioning per shard
- E2EState now carries flowToken alongside companyId so workers in
CI (which lack a local.config.env file) can read the token without
needing process-env propagation through Playwright
- localTestFixture reads flowToken from dynamic state with the env
var as fallback, mirroring how it already handles companyId
- New npm run e2e:setup script wraps a tsx invocation of
e2e/scripts/runGlobalSetup.ts so the CI job has a single entry point
This reduces concurrent load on flows.gusto-demo.com from up to 18
parallel demo creations (9 shards x 2 demos) down to 1, and trims
~3 minutes of cold-start time off each shard.
Co-authored-by: Cursor <cursoragent@cursor.com>
* ci(e2e): include hidden files when uploading e2e state artifact
The e2e-setup job writes state to e2e/.e2e-state.json (leading dot to
keep it gitignored). actions/upload-artifact@v6 excludes hidden files
by default for security, so the previous run succeeded at provisioning
but failed to publish the artifact (\"No files were found with the
provided path\").
Opting in via include-hidden-files: true is the targeted fix —
renaming the file would require touching every reader and break the
existing local-dev gitignore convention.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): validate gwsFlowsBase URL before fetch in scenario cache
Parse gwsFlowsBase via the URL constructor and require an http(s)
scheme before issuing the cache-validation request, instead of
interpolating the raw string into a template literal. URL-encode
flowToken and companyId for the path segments. Reject malformed input
by returning false (treated as a cache miss, same as a network
failure).
Addresses the Boost/Semgrep SSRF finding on the prior fetch call.
Adds tests covering invalid-URL and non-http(s)-scheme rejection.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(test): stabilize OffCycleExecution breadcrumb flake on CI
Switch the initial 'Jane Doe' assertion from
waitFor(() => getByText(...)) to await findByText(..., { timeout: 5000 }).
The previous waitFor relied on the default 1s timeout, which is below
the time the i18next-Suspense first render takes when the suite is run
under coverage instrumentation on CI. findByText queries the DOM on
every interval (rather than re-running an assertion that throws
synchronously on miss), and the explicit 5s budget matches the wait
budget already used by other async assertions in this file.
The test file is otherwise unrelated to this branch; this is a
drive-by stability fix to unblock the e2e/infrastructure CI.
Co-authored-by: Cursor <cursoragent@cursor.com>
* chore(e2e): drop unused scenario fields and dead example fixture
The runner advertised `street_2` on locations and a `start_date`
override branch on contractors that no scenario or fragment ever
exercises. Strip both so the runner only carries surface area that
maps to a real consumer.
`e2e/scenarios/payroll/example-minimal.json` existed solely as an
on-disk fixture for the loader test. Inline it into the test file
using the same `mkdtempSync` pattern the other test cases already
use, then delete the standalone scenario so prewarm/validators don't
treat it as a real scenario.
Co-authored-by: Cursor <cursoragent@cursor.com>
* refactor(e2e): rename E2E_LOCAL to E2E_USE_REAL_BACKEND
`E2E_LOCAL` was misleading on two fronts: it reads as "are we running
locally" but is also set by the demo-cloud config, and the original
"local vs MSW" distinction it gated has narrowed since the MSW-mode
CI job was retired. The flag's real meaning is "this run will hit a
real gws-flows backend (local or demo) and should provision scenarios
+ refresh tokens accordingly."
Rename it across configs, CI, fixture, globalSetup, docs, and the
remaining legacy spec that reads it. Behavior unchanged; this is a
straight find/replace with no fallback. Internal LocalConfig.isLocal
left alone — it's a private fixture field that doesn't surface to
test authors.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): remove scenario cache and fix loading helper
Two compounding issues made canary suites appear to hang after the
[scenario-runner] Cache hit log line:
1. The scenario cache reused provisioned demo companies between local
runs. For state-mutating tests (any spec that submits a payroll,
terminates an employee, etc.) cache hits return a company in
whatever state the previous run left it, breaking repeatability.
CI never used the cache (no .scenario-cache.json checked in), so
removing it brings local behavior in line with CI: every test gets
a fresh demo company. Local re-runs pay the 30-60s provisioning
cost, which is the honest cost of a repeatable test environment.
2. waitForLoadingComplete polled getByText(/loading/i) and friends,
matching the SDK's <Loading> Suspense fallback and any per-section
spinner. It required 3 consecutive non-loading checks and rarely
got them, silently sitting at 60s timeout. Because Playwright
does not print step-level progress by default, this manifested as
"test stalls after Cache hit." Replace with a targeted
waitFor({ state: 'detached' }) on the Suspense fallback region.
Verified on infrastructure: e2e/tests/payroll.spec.ts now passes all
4 tests in ~12 seconds (vs 3+ minutes per test before the helper fix).
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): disable state caching in CI to prevent stale company reuse
Co-authored-by: Jeffrey D Johnson <jeffredodd@users.noreply.github.com>
* fix(e2e): remove state caching from CI, each shard provisions independently
Co-authored-by: Jeffrey D Johnson <jeffredodd@users.noreply.github.com>
* fix: prettier formatting for ci.yaml
* fix(e2e): restore e2e-setup job with fresh provisioning, share state across shards
* ci(e2e): discover matrix domains from e2e/tests subfolders
Replace the hardcoded 9-entry domain list with a small e2e-domains job
that lists immediate subdirectories under e2e/tests/ and publishes the
result as a JSON array. The e2e job's matrix consumes it via fromJson,
with an if-guard that skips the job cleanly when no domain folders
exist.
Drops dismissal and legacy from the matrix as a side effect: neither
has a folder under e2e/tests/, so neither becomes a shard. The
dismissal spec, its globalSetup block, and the scenario schema enum
are intentionally left in place for a follow-up PR that moves the
dismissal spec into the employee domain.
New domain folders added by stacked branches automatically become
shards with no further CI changes.
Co-authored-by: Cursor <cursoragent@cursor.com>
* feat(e2e): company domain — scenario + spec rewrite
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): harden company onboarding scenario for CI
Merge shared infrastructure scenario fixes and seed a location in the company
scenario so onboarding endpoints have required company setup.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): accept company onboarding copy variations in demo runs
Allow current onboarding heading/button text variants while keeping flow
coverage, and include shared scenario runner/fixture hardening updates.
Co-authored-by: Cursor <cursoragent@cursor.com>
* feat(e2e): expand company domain with multi-entity, filing/mailing split, and step nav
Adds two new company scenarios:
- company-multi-entity: 3 locations, mixed workforce, configured pay
schedule. Surfaced via company-complex-scenario.spec.ts.
- company-filing-mailing-split: separate filing-only and mailing-only
locations to exercise the address-step branch.
Adds company-step-navigation.spec.ts for progressbar visibility and
back-from-first-step coverage on the existing company-onboarding
scenario.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): walk into onboarding flow in company complex/split scenario tests
The company-multi-entity and company-filing-mailing-split provisioning
tests stopped at the onboarding overview heading, which only proves
that the company loads — not that the provisioned data flows through
to the actual onboarding UI. Both now click "Start onboarding" and
assert the address step heading + progress bar are visible, giving
each video a real terminal state.
Co-authored-by: Cursor <cursoragent@cursor.com>
* feat(e2e): walk company onboarding through step 5 (bank account)
Adds company-deep-onboarding lifecycle spec that drives:
overview -> start onboarding -> addresses continue -> federal taxes
(EIN, taxpayer type, legal name) -> industry (NAICS select) -> assert
bank account / verification heading is visible.
This pushes coverage from "stops at industry" (step 4) to step 5
of the 8-step company onboarding state machine, exercising the
COMPANY_INDUSTRY_SELECTED -> bankAccount transition.
Co-authored-by: Cursor <cursoragent@cursor.com>
* feat(e2e): cover company onboarding bank account empty-state lifecycle
Walks overview -> addresses -> federal taxes -> industry -> bank account
step and asserts either the routing/account input pair (empty form
branch) OR the verify/change/continue actions (existing-account
branch). Exercises the BankAccount state machine entry from the
company onboarding flow.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): anchor fillDate spinbutton matchers to ^month/^day/^year
React Aria renders each date segment with the accessible name
"<type>, <group>" (e.g. "day, Last day of work"), so the unanchored
/day/i matcher inside fillDate also matches the month and year
segments whenever the group name itself contains "day" — producing
'strict mode violation: getByRole(\'spinbutton\', { name: /day/i })
resolved to 3 elements'.
Anchoring to /^month/, /^day/, /^year/ keeps the helper working for
date groups whose label happens to include "day" (Birthday, Last day
of work, First pay date, etc.) without changing behavior for plain
labels.
Verified end-to-end by the new company onboarding canary suite, which
drives "First pay date" and "First pay period end date" through this
helper inside the pay-schedule wizard step.
Co-authored-by: Cursor <cursoragent@cursor.com>
* feat(e2e): add company canary suite covering all 8 onboarding wizard steps
Adds a 5-spec canary suite that drives the Company Onboarding flow
end-to-end through the SDK UI against the gws-flows demo backend. The
suite complements the existing per-step rendering specs by proving
each branch of the wizard works as a continuous flow.
Why
---
The existing company-domain specs verify individual screens land and
that the wizard advances one step at a time. None of them drives the
full wizard or asserts the completion state — the path through bank
account creation, pay schedule creation, and the terminal "Nice! We'll
take it from here." overview was only covered piecemeal.
What
----
- e2e/scenarios/company/full-flow-canary.json — fresh react_sdk_demo
decorated with a single HQ location (filing + mailing) so the
wizard can be driven entirely through the SDK UI.
- e2e/scenarios/company/onboarded-completion-canary.json — uses
react_sdk_demo_company_onboarded so loading /?flow=company-onboarding
lands directly on the terminal completion overview.
- e2e/utils/companyFlowDrivers.ts — per-screen drivers
(landOnCompanyOnboarding, advancePastLocations,
advancePastFederalTaxes, advancePastIndustry,
advancePastBankAccount, skipEmployeesStep, advancePastPaySchedule,
advancePastStateTaxes, runFullOnboardingThroughDocuments,
assertCompletedOverview). All headings/buttons sourced from
src/i18n/en/Company.*.json. Imports fillDate and waitForLoadingComplete
from e2e/utils/helpers.ts.
- e2e/tests/company/canary/
- 01-overview-to-federal-taxes.spec.ts — entry → locations → federal
- 02-locations-add-another-address.spec.ts — add 2nd location via UI
- 03-federal-to-bank-account.spec.ts — federal → industry → bank
- 04-full-flow-through-documents.spec.ts — full 8-step wizard
- 05-onboarded-completion.spec.ts — terminal completion overview
Notable driver subtleties
-------------------------
- Bank account add: clicking Continue on the empty form creates the
account but stays on the bank step (now in list view). A second
Continue is required to advance to Employees.
- Pay schedule create: same two-click pattern — Save creates the
schedule and renders the list view (still step 6), then Continue
advances to State tax (step 7).
- Locations state field: rendered as a React Aria button with
accessible name "Select state... State", not a labelable input,
so the driver uses getByRole('button', { name: /select state/i }).
Verified
--------
All 5 specs verified PASSED against the demo backend (workers=1,
matching CI's serial mode): 5 passed (1.7m). Each spec also passed
individually under the video-capture config — videos archived at
~/Desktop/company-videos/.
Co-authored-by: Cursor <cursoragent@cursor.com>
* refactor(e2e): eliminate test duplication and use shared driver functions
* fix(TimeOff): validate waiting period as integer in policy settings (#1879)
fix: validate waiting period as integer in time off policy settings
The API requires accrualWaitingPeriodDays to be an integer, but the form
allowed decimal input, causing an unhandled Zod validation error. Add
maximumFractionDigits={0} to prevent decimal entry and a form-level
validation rule that surfaces a clear error message as a safety net.
* feat(Dashboard): add Deductions block to the Job and Pay tab (#1872)
* fix(Deductions): un-squash the IncludeDeductions view inside Flow
The empty-state CTA rendered into a ~200px column even though the
parent had 1189px of available width. Verified via Playwright against
the SDK dev app at /employee/Deductions.
Root cause: Flow's outer Flex is flex-direction:row (default) with one
child column-flex. Without a child that declares width:100%, the
column-flex sizes to its content's intrinsic width — which for the
empty-state's narrow text means every word wraps to its own line.
DocumentSigner doesn't show this bug because DocumentList wraps its
content in <BaseComponent>, which renders <BaseLayout>/<FadeIn
width:100%>. That FadeIn is the width anchor. The list and form
contextuals here already use <BaseLayout>; the include contextual
didn't because it has no per-view errors to surface. Adding it now —
the FadeIn anchor matters more than the error display.
Verified in browser: the heading, description, empty-state box, and
buttons all render at full content width. Form view ("Add deduction"
radio + garnishment-type picker) also renders correctly. Test suite
green.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(Dashboard): wire Deductions block into JobAndPayView
Replaces the bare garnishments DataView in JobAndPayView with a fully
interactive Deductions block mirroring the PaymentMethod pattern: row-
level HamburgerMenu (Edit / Delete), a confirmation dialog backed by a
new useDeleteDeduction helper, and a DeleteDeductionDialog component.
The block sources its data from useDeductionsList (the existing hook —
its soft-delete action + remainingActiveCount return are reused as-is),
so the consumer drops the legacy garnishments fetch in
useEmployeeCompensation and JobAndPayView no longer takes a
garnishments prop.
Add / Edit / Delete events flow through the dashboardStateMachine the
same way the bank-account ones do:
- EMPLOYEE_DEDUCTION_ADD on the index state → deductionForm with no
editingDeductionId (create mode).
- EMPLOYEE_DEDUCTION_EDIT on the index state → deductionForm with
editingDeductionId set from the event payload (the DeductionsForm
picker pre-populates from the loaded row via the dedup-ed list
query).
- EMPLOYEE_DEDUCTION_DELETED on the index state → index with
successAlert: 'deductionDeleted'.
- EMPLOYEE_DEDUCTION_CREATED / UPDATED on deductionForm → index with
'deductionAdded' / 'deductionUpdated'.
- EMPLOYEE_DEDUCTION_CANCEL / CANCEL on deductionForm → index.
DeductionFormContextual mounts the DeductionsForm picker (chooses
between StandardDeductionForm and ChildSupportFormView) so the
Dashboard surfaces support both custom deductions and any
court-ordered garnishment type.
Also fixes a pre-existing rendering bug in the withheld column:
`amount` is a string per the API but the old branch checked
`typeof === 'number'` (never true) and fell back to printing
annualMaximum with a hardcoded '%'. The new column matches the legacy
DeductionsList — currency / percent via `deductAsPercentage`, with the
"{value} per paycheck" suffix for recurring rows.
Errors from both paymentMethodList and deductionsList are merged with
composeErrorHandler so the existing JobAndPayView BaseLayout surfaces
either hook's failure.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(Dashboard): surface deductions errors through the loading gate
When `useDeductionsList` (or `usePaymentMethodList`) fails before first
paint, the hook returns `isLoading: true` with populated `errorHandling.errors`.
The early `<Loading />` swallowed those errors, leaving the Job and Pay
tab in a permanent skeleton state instead of showing a retry alert.
Replace with `<BaseLayout isLoading error={errorHandling.errors} />` so
the existing error surface handles the failure.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* refactor(Deductions): extract shared formatDeductionAmount + dashboard tests
Pulls the currency/percent/per-paycheck branching that lived in both
JobAndPayView.tsx and DeductionsList.tsx into a single
`formatDeductionAmount` helper, exported from `Deductions/shared/`. The
per-paycheck suffix is injected as a `formatPerPaycheck` callback so each
caller keeps its own i18n namespace (`Employee.Dashboard` vs
`Employee.Deductions`).
Adds:
- `formatDeductionAmount.test.ts` — table-driven unit coverage of the
one-time / recurring × fixed / percent matrix plus missing/non-numeric
amounts.
- Job-and-pay Deductions integration tests in `Dashboard.test.tsx`:
row rendering, EMPLOYEE_DEDUCTION_ADD, EMPLOYEE_DEDUCTION_EDIT, and a
full confirm-delete flow asserting the PUT body and
EMPLOYEE_DEDUCTION_DELETED payload.
Fixes the `useContainerBreakpoints` mock to expose both the named and
default exports — the previous mock broke as soon as a test navigated
into the Job and Pay tab.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* fix(PayrollOverview): remove Text wrapper from check payment warning alert (#1884)
The nested Text component breaks rendering when partners override the
Alert via an adapter. Pass the description string directly so adapters
receive plain text children.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(e2e): time-off domain — scenario + spec rewrite (#1834)
* feat(e2e): add scenario JSON schema, fragments, and validator
Foundation for the per-domain scenario-driven E2E rebuild.
- e2e/scenarios/schema/scenario.schema.json — full scenario definition
covering locations, employees, contractors, paySchedule, payrolls;
fragment refs with overrides; templated strings
- e2e/scenarios/schema/scenario.types.ts — generated TS types via
json-schema-to-typescript
- e2e/scenarios/fragments/ — w2-salaried, w2-hourly, contractor-1099
- e2e/scenarios/payroll/example-minimal.json — loader reference fixture
- e2e/scenarios/scripts/validate.mjs — ajv-based standalone validator
- npm scripts: scenarios:types (codegen), scenarios:validate
Implements Notion tasks #007-#010 (Phase A foundation). First PR in the
16-PR draft stack for the E2E overhaul + API upgrade initiative.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(e2e): scenario loader — $ref resolution, overrides, templates
Implements Phase A tasks #011-#014: the deterministic loader that turns a
scenario JSON file into a provisioning-ready Scenario object.
- e2e/scenario/loader.ts — public API: resolveScenario (fragments + overrides,
templates intact, used as the hash input) and loadScenario (full pipeline:
resolve + applyTemplates + ajv schema-validate)
- Deep merge semantics: arrays REPLACE, objects merge recursively. \$ref
sibling fields and \`overrides\` both layer onto the resolved fragment;
overrides win. Cycle detection via \$ref stack.
- Template grammar: {{ts}} (injectable timestamp; defaults to Date.now())
and {{relative:+Nd[:DayName]}} (UTC date arithmetic; optional next-weekday
advance). Unknown tokens throw rather than silently passing through.
- e2e/scenario/loader.test.ts — 12 cases: deepMerge rules, template grammar,
resolution against the committed example-minimal.json, synthesized cycle
+ override + bad-schema fixtures via mkdtempSync.
- vitest.scenario.config.ts + package.json: scenario tests run via
\`npm run test:scenarios\` (separate from the main vitest run, which still
excludes e2e/**). Node environment, no globals.
Second PR in the 16-PR stack for the E2E overhaul + API upgrade initiative.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(e2e): scenario structural hash via canonical JSON + SHA-256
Implements Phase A task #015: the cache-key function that gives each
scenario a stable identity independent of object key ordering and
template substitution.
- e2e/scenario/hash.ts — canonicalize() sorts object keys recursively
(arrays preserve order since array order is semantically meaningful in
the scenario schema); hashScenarioStructure() SHA-256-hex over the
canonical form.
- Input is meant to be the output of resolveScenario (refs + overrides
applied, {{ts}}/templates intact). Hashing pre-substitution keeps the
hash stable across runs while still invalidating when an author edits
a referenced fragment.
- e2e/scenario/hash.test.ts — 6 cases pinning canonicalization rules,
key-order insensitivity, value-change sensitivity, array-order
significance, and the 64-char hex output shape.
Third PR in the 16-PR stack for the E2E overhaul + API upgrade
initiative. Sets up the cache key used by the next PR (cache).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
* feat(e2e): scenario infrastructure — cache, runner, decorations, fixture, reporter, scripts
Complete E2E scenario infrastructure for per-domain testing:
- Cache layer (e2e/scenario/cache.ts): atomic R/W, token validation, hit/miss logic
- Runner (e2e/scenario/runner.ts): provision demos, decorate entities (locations,
employees, addresses, jobs, compensation, onboarding, contractors, pay schedules,
payroll processing), validate expectedContext, cache results
- Fixture (e2e/utils/localTestFixture.ts): scenario fixture with @domain auto-tagging,
backwards-compatible with legacy localConfig path
- Reporter (e2e/reporters/scenario-reporter.ts): per-domain/scenario aggregation to
e2e/reports/results.json
- Scripts (e2e/scenario/scripts.ts): prewarm and clear CLI commands
- CI: upload e2e/reports/ artifact alongside playwright-report/
- Register scenario reporter in all 3 Playwright configs
- Add e2e:scenarios:prewarm and e2e:scenarios:clear npm scripts
- .gitignore: add .scenario-cache.json and e2e/reports/
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): stabilize scenario CI paths across msw and demo runs
Avoid remote scenario provisioning in MSW CI, make dismissal setup non-fatal in
global setup, and align runner mutations with current API requirements.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): normalize legacy onboarding status values in runner
Map legacy "completed" scenario values to "onboarding_completed" before
calling the API so demo provisioning remains compatible.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): avoid hard-failing on onboarding status API rejection
Treat onboarding-status decoration as best-effort so scenario provisioning can
continue when the API rejects completion on partially configured employees.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): make scenario payroll and URL overrides less brittle
Fallback to any unprocessed regular pay period when none are in the past and
preserve explicit employee/contractor query params in scenario-mode tests.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): tolerate payroll blockers during scenario seeding
Treat known payroll blocker errors during processed-payroll setup as non-fatal
so scenario provisioning can proceed in demo environments.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): include start_date and end_date when creating off-cycle payrolls
The gws-flows API now requires explicit start_date and end_date on the
off-cycle payroll create payload, even when the runner only knows the
check_date. Without these the request returns 422 and scenario
provisioning fails.
The runner now forwards explicit start_date/end_date from the scenario
JSON when present, and falls back to check_date (or today) so existing
scenarios keep working.
Co-authored-by: Cursor <cursoragent@cursor.com>
* ci(e2e): gate Playwright runs behind scenario validation
Add a fast 'scenarios' CI job that runs npm run scenarios:validate plus
npm run test:scenarios so a broken scenario JSON or scenario module
regresion fails the build immediately, before the much-slower MSW e2e
and demo e2e jobs spin up Playwright.
Both e2e and e2e-demo now depend on scenarios so a schema regression
short-circuits the chain.
Co-authored-by: Cursor <cursoragent@cursor.com>
* ci(e2e): drop MSW e2e job, keep e2e-demo as the only Playwright gate
The MSW e2e job was failing on tests that worked correctly against the
real demo backend, because MSW fixtures cannot mirror the full state
machine + form behavior the demo flow drives. Maintaining tolerant
fallbacks just to keep MSW happy was watering down assertions without
adding coverage that Storybook + unit tests don't already provide.
Removes the e2e job entirely. e2e-demo is now the only Playwright
gate. Adds an e2e-scenario-report-demo artifact upload so the
per-domain scenario report stays accessible in CI.
Saves roughly 2.5-3 min per branch per push and unblocks tests we
tightened in recent commits.
Co-authored-by: Cursor <cursoragent@cursor.com>
* ci(e2e): rename e2e-demo job to e2e (now the sole Playwright gate)
After removing the MSW-mode e2e job, the remaining job is the only
Playwright gate, so the -demo suffix is no longer informative.
Renames:
- job: e2e-demo -> e2e
- step: 'Run e2e tests against demo environment' -> 'Run e2e tests'
- step: 'Upload demo test results' -> 'Upload test results'
- step: 'Upload demo scenario reports' -> 'Upload scenario reports'
- artifact: playwright-report-demo -> playwright-report
- artifact: e2e-scenario-report-demo -> e2e-scenario-report
Also restores the e2e required status check on main branch
protection, which had been silently blocking PR merges since the
MSW job was removed (protection still required a check named e2e).
The npm script test:e2e:demo stays as-is locally so dev muscle memory
and pointer to the demo backend stay clear.
Co-authored-by: Cursor <cursoragent@cursor.com>
* ci(e2e): shard Playwright job by domain
Splits the single e2e job into a matrix with one entry per domain folder
under e2e/tests/. Each shard runs in parallel with fail-fast disabled,
so:
- one domain's failure no longer cancels the others' feedback
- total wall-clock drops from sequential single-worker runtime to the
slowest domain's runtime
- re-running just one failed domain is cheap (small CI re-spend)
Domains: company, contractor, dismissal, employee, information-requests,
payroll, termination, time-off, legacy.
Filter is a Playwright path substring so each shard picks up both flat
specs at e2e/tests/<domain>*.spec.ts and nested specs under
e2e/tests/<domain>/. --pass-with-no-tests keeps shards green on
branches where a domain folder hasn't materialized yet (e.g. infra
itself, where domain reorganizations still live on stacked PRs).
Artifact uploads are scoped per shard so playwright-report-<domain>
and e2e-scenario-report-<domain> don't collide.
Co-authored-by: Cursor <cursoragent@cursor.com>
* ci(e2e): throttle matrix to max-parallel 2 to avoid demo backend timeouts
Each e2e shard's globalSetup creates ~2 demo companies on
flows.gusto-demo.com (one primary onboarded company plus the dismissal
company). With the matrix expanded to 9 shards, all 9 ran simultaneously
and the demo backend couldn't keep up — flow-token lookup hit the 200s
timeout and 8/9 shards failed in the previous CI run on #1873.
max-parallel: 2 caps the concurrency so demo provisioning stays
manageable. Trades some wall-clock for reliability; one slow shard no
longer cascades into half the matrix failing on infrastructure load.
Co-authored-by: Cursor <cursoragent@cursor.com>
* ci(e2e): provision demo companies once via shared e2e-setup job
Replaces per-shard demo provisioning with a single upstream e2e-setup
job that publishes the resulting state as a CI artifact. The matrix
shards download that artifact, and globalSetup short-circuits when it
finds a valid e2e/.e2e-state.json on disk.
Changes:
- New e2e-setup CI job runs globalSetup once, uploads e2e-state
artifact (1 day retention)
- Matrix shards depend on e2e-setup, download the artifact before
running tests
- globalSetup gains an idempotency check: if .e2e-state.json exists
with a flowToken/companyId that the demo backend still accepts,
reuse it and skip ~3 minutes of provisioning per shard
- E2EState now carries flowToken alongside companyId so workers in
CI (which lack a local.config.env file) can read the token without
needing process-env propagation through Playwright
- localTestFixture reads flowToken from dynamic state with the env
var as fallback, mirroring how it already handles companyId
- New npm run e2e:setup script wraps a tsx invocation of
e2e/scripts/runGlobalSetup.ts so the CI job has a single entry point
This reduces concurrent load on flows.gusto-demo.com from up to 18
parallel demo creations (9 shards x 2 demos) down to 1, and trims
~3 minutes of cold-start time off each shard.
Co-authored-by: Cursor <cursoragent@cursor.com>
* ci(e2e): include hidden files when uploading e2e state artifact
The e2e-setup job writes state to e2e/.e2e-state.json (leading dot to
keep it gitignored). actions/upload-artifact@v6 excludes hidden files
by default for security, so the previous run succeeded at provisioning
but failed to publish the artifact (\"No files were found with the
provided path\").
Opting in via include-hidden-files: true is the targeted fix —
renaming the file would require touching every reader and break the
existing local-dev gitignore convention.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): validate gwsFlowsBase URL before fetch in scenario cache
Parse gwsFlowsBase via the URL constructor and require an http(s)
scheme before issuing the cache-validation request, instead of
interpolating the raw string into a template literal. URL-encode
flowToken and companyId for the path segments. Reject malformed input
by returning false (treated as a cache miss, same as a network
failure).
Addresses the Boost/Semgrep SSRF finding on the prior fetch call.
Adds tests covering invalid-URL and non-http(s)-scheme rejection.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(test): stabilize OffCycleExecution breadcrumb flake on CI
Switch the initial 'Jane Doe' assertion from
waitFor(() => getByText(...)) to await findByText(..., { timeout: 5000 }).
The previous waitFor relied on the default 1s timeout, which is below
the time the i18next-Suspense first render takes when the suite is run
under coverage instrumentation on CI. findByText queries the DOM on
every interval (rather than re-running an assertion that throws
synchronously on miss), and the explicit 5s budget matches the wait
budget already used by other async assertions in this file.
The test file is otherwise unrelated to this branch; this is a
drive-by stability fix to unblock the e2e/infrastructure CI.
Co-authored-by: Cursor <cursoragent@cursor.com>
* chore(e2e): drop unused scenario fields and dead example fixture
The runner advertised `street_2` on locations and a `start_date`
override branch on contractors that no scenario or fragment ever
exercises. Strip both so the runner only carries surface area that
maps to a real consumer.
`e2e/scenarios/payroll/example-minimal.json` existed solely as an
on-disk fixture for the loader test. Inline it into the test file
using the same `mkdtempSync` pattern the other test cases already
use, then delete the standalone scenario so prewarm/validators don't
treat it as a real scenario.
Co-authored-by: Cursor <cursoragent@cursor.com>
* refactor(e2e): rename E2E_LOCAL to E2E_USE_REAL_BACKEND
`E2E_LOCAL` was misleading on two fronts: it reads as "are we running
locally" but is also set by the demo-cloud config, and the original
"local vs MSW" distinction it gated has narrowed since the MSW-mode
CI job was retired. The flag's real meaning is "this run will hit a
real gws-flows backend (local or demo) and should provision scenarios
+ refresh tokens accordingly."
Rename it across configs, CI, fixture, globalSetup, docs, and the
remaining legacy spec that reads it. Behavior unchanged; this is a
straight find/replace with no fallback. Internal LocalConfig.isLocal
left alone — it's a private fixture field that doesn't surface to
test authors.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): remove scenario cache and fix loading helper
Two compounding issues made canary suites appear to hang after the
[scenario-runner] Cache hit log line:
1. The scenario cache reused provisioned demo companies between local
runs. For state-mutating tests (any spec that submits a payroll,
terminates an employee, etc.) cache hits return a company in
whatever state the previous run left it, breaking repeatability.
CI never used the cache (no .scenario-cache.json checked in), so
removing it brings local behavior in line with CI: every test gets
a fresh demo company. Local re-runs pay the 30-60s provisioning
cost, which is the honest cost of a repeatable test environment.
2. waitForLoadingComplete polled getByText(/loading/i) and friends,
matching the SDK's <Loading> Suspense fallback and any per-section
spinner. It required 3 consecutive non-loading checks and rarely
got them, silently sitting at 60s timeout. Because Playwright
does not print step-level progress by default, this manifested as
"test stalls after Cache hit." Replace with a targeted
waitFor({ state: 'detached' }) on the Suspense fallback region.
Verified on infrastructure: e2e/tests/payroll.spec.ts now passes all
4 tests in ~12 seconds (vs 3+ minutes per test before the helper fix).
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): disable state caching in CI to prevent stale company reuse
Co-authored-by: Jeffrey D Johnson <jeffredodd@users.noreply.github.com>
* fix(e2e): remove state caching from CI, each shard provisions independently
Co-authored-by: Jeffrey D Johnson <jeffredodd@users.noreply.github.com>
* fix: prettier formatting for ci.yaml
* fix(e2e): restore e2e-setup job with fresh provisioning, share state across shards
* ci(e2e): discover matrix domains from e2e/tests subfolders
Replace the hardcoded 9-entry domain list with a small e2e-domains job
that lists immediate subdirectories under e2e/tests/ and publishes the
result as a JSON array. The e2e job's matrix consumes it via fromJson,
with an if-guard that skips the job cleanly when no domain folders
exist.
Drops dismissal and legacy from the matrix as a side effect: neither
has a folder under e2e/tests/, so neither becomes a shard. The
dismissal spec, its globalSetup block, and the scenario schema enum
are intentionally left in place for a follow-up PR that moves the
dismissal spec into the employee domain.
New domain folders added by stacked branches automatically become
shards with no further CI changes.
Co-authored-by: Cursor <cursoragent@cursor.com>
* feat(e2e): time-off domain — scenario + spec rewrite
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): use valid onboarding status in time-off scenario
Set a currently accepted employee onboarding status value so demo scenario
provisioning succeeds in CI.
Co-authored-by: Cursor <cursoragent@cursor.com>
* feat(e2e): expand time-off domain with scenario-driven policy coverage
Adds three new time-off scenarios (multi-employee policy list,
policy-create validation, multi-location assignment) and rewrites
e2e/tests/time-off so the long-skipped SelectEmployees blocks are
replaced with stable, flow-accurate tests grounded in the real
PolicyList -> PolicyTypeSelector -> PolicyDetails flow.
The new specs cover:
- policy list shell + create CTA visibility
- create policy entry into policy type selector
- policy type selector required-field gate (continue disabled)
- cancel returning to policy list
- proceeding through type selection into policy details form
- multi-location workforce provisioning sanity
Coverage requiring scenario provisioning is gated with
test.skip(!scenario.flowToken, ...) so MSW runs stay green.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): assert visible Time off radio instead of named radiogroup
The PolicyTypeSelectorPresentation renders policy type as a
RadioGroupField. Querying the group by accessible name '/policy type/i'
was unstable in demo runs; assert directly on the 'Time off' radio
option which is unambiguous and matches the rendered DOM.
Co-authored-by: Cursor <cursoragent@cursor.com>
* feat(e2e): rewrite time-off specs as end-to-end CRUD lifecycle flows
Replace the prior shallow waypoint specs with three lifecycle specs
that drive each CRUD action to its terminal UI state:
- policy-create-lifecycle: list -> type selector -> details (unlimited)
-> add employees -> Continue -> assert policy detail view loads
with the new policy heading, breadcrumb, and Edit policy CTA.
- policy-edit-lifecycle: create a fresh policy, click Edit policy,
rename, Save & continue, assert detail view shows the new name.
- policy-delete-lifecycle: create a fresh policy, return to list,
open hamburger -> Delete policy, confirm dialog, assert success
alert text and that the row disappears.
The smoke spec (time-off.spec.ts) is preserved as the cheapest
sanity check.
Drops the now-superseded list/create/assignment shallow specs and
their unused scenario JSON (time-off-policy-list-multi-employee.json,
time-off-policy-assignment-multi-location.json).
Co-authored-by: Cursor <cursoragent@cursor.com>
* feat(e2e): cover all time-off state-machine branches end-to-end
Adds three new lifecycle specs that exercise paths the existing CRUD
specs didn't cover. Each spec drives the flow to a terminal UI state:
- policy-cancel-lifecycle: enter policy details form, cancel, assert
return to policy list with no draft policy created.
- policy-fixed-accrual-lifecycle: create a sick-leave policy with
the fixed-per-year accrual branch, exercising the policy settings
step (which the unlimited path skips), then add employees and
land on the policy detail view.
- holiday-policy-lifecycle: holiday-pay sub-flow through type
selector, holiday selection (multi-select), add employees, and
holiday detail view; plus a separate delete path that confirms
the holiday-specific success alert text.
The holiday spec self-cleans any existing holiday policy in the
demo company before running so it's idempotent across cache hits.
Result: 8 specs covering ~10 distinct paths through the 14-state
TimeOff machine — every CRUD branch (vacation/sick unlimited,
sick fixed, holiday) plus cancel and edit transitions.
Co-authored-by: Cursor <cursoragent@cursor.com>
* feat(e2e): cover time-off policy details form UI validation lifecycle
Asserts the Save & continue button is disabled until both required
fields (policy name + accrual method) are populated. Verifies the
isContinueDisabled gate in PolicyConfigurationFormPresentation
without submitting to the backend.
Terminal: button transitions from disabled to enabled after both
fields populated.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): use fixed-per-year policy for time-off edit lifecycle
Updating an unlimited time-off policy via PUT
/v1/time_off_policies/:uuid currently fails on the demo backend with
"Policy accrual date by anniversary: Please make a selection", even
though the SDK request body and the Rails facade both null the field
out for unlimited policies. Switch the edit-lifecycle spec to seed a
fixed-per-year policy (per_pay_period accrual), which exercises the
same Edit -> rename -> Save & continue -> detail loop without
tripping the backend validation.
Co-authored-by: Cursor <cursoragent@cursor.com>
* chore(e2e): consolidate duplicate time-off scenarios
time-off-management.json and time-off-policy-create-validation.json
provisioned functionally identical state — same baseDemo, one
location, one onboarded W-2 employee — differing only in cosmetic
fields (street number, last name). Drop the duplicate and repoint
the lone consuming spec (time-off.spec.ts) at the surviving scenario
so we don't pay for two near-identical demo provisions when one
suffices.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): anchor fillDate spinbutton regex to date segment start
React Aria renders each date segment with the accessible name
"<segment>, <group>" (e.g. "day, Last day of work"). The previous
regexes /month/i, /day/i, /year/i would each match all three
segments inside any group whose name contained "day" or "year",
producing strict-mode locator violations like:
strict mode violation: getByRole('spinbutton', { name: /day/i })
resolved to 3 elements
Anchoring on /^month/, /^day/, /^year/ ensures we target the
segment whose own type begins with the matched word, regardless of
the surrounding group name. Verified locally; benefits any
subsequent rebase that pulls this helper.
Co-authored-by: Cursor <cursoragent@cursor.com>
* feat(e2e): add time-off canary suite covering all 5 TimeOffFlow paths
Adds a 5-spec canary suite under e2e/tests/time-off/canary/ that drives
every distinct end-to-end path through the TimeOffFlow state machine
against the demo backend, with a video proof per passing spec.
The suite exercises:
1. unlimited time-off policy create — list -> type -> details
(unlimited, skips settings) -> add employees -> detail view
2. fixed-accrual sick policy create — list -> type -> details
(fixed-per-year) -> settings -> add employees -> detail view
3. holiday pay policy create — list -> type -> holiday selection ->
add employees -> holiday detail view
4. edit policy rename — create -> view detail -> edit details ->
rename -> save -> detail view with new name
5. delete policy — create -> back to list -> row actions menu ->
confirm dialog -> success alert
Existing TimeOffFlow specs in e2e/tests/time-off/ remain in place as
cheaper surface checks; the canary suite sits alongside them under the
canary/ subdirectory and provisions its own scenario per spec so each
can run independently.
The new shared scenario time-off/full-flow-canary.json builds on
react_sdk_demo_company_onboarded with a single salaried employee. The
scenario runner's known onboarding-status decoration limitation
("Missing requirements: Date of birth ...") is harmless for these
specs — they only need an onboarded company, not an onboarded
employee.
Driver code lives in e2e/utils/timeOffFlowDrivers.ts with one exported
runX function per flow path; spec files are thin wrappers that name
the spec, set the scenario annotation, set timeouts, and assert the
final landing landmark.
All 5 specs verified PASSED against demo (workers=1, matching CI's
serial mode): 5 passed (2.0m).
Co-authored-by: Cursor <cursoragent@cursor.com>
* feat(e2e): enrich time-off canary suite with employees, balances, and settings
Updates the time-off canary suite to do real end-to-end work on each
flow rather than skipping past the add-employees and policy-settings
steps:
- 01 unlimited create: selects 2 specific employees and walks the
add-confirm dialog instead of clicking through with zero selected
- 02 fixed-accrual sick create: toggles Balance maximum (240),
Carry over limit (40), and Payout on dismissal in the policy
settings step; selects 3 employees and assigns a different
starting balance per row (8, 16, 24); confirms the add dialog
- 03 holiday create: explicitly checks the table-level "Select all"
on the add-employees step (it already did this for holidays) and
asserts the resulting policy lands populated
- 04 edit rename: creates a populated fixed-accrual policy with one
selected employee + a starting balance, then renames it through
the Edit flow so the rename is exercised against a non-empty
policy
- 05 delete: explicitly creates an empty policy and deletes it. The
driver carries a comment explaining why: deleting a populated
policy on the demo backend trips the "pending or approved time
off requests must be declined first" UX blocker because seed
employees on react_sdk_demo_company_onboarded carry pre-existing
requests. That's a real product behavior, not a regression — and
it's not what spec 05's contract is testing (delete-from-list
confirmation flow). The other four specs already cover the
populated-policy paths.
The shared driver helpers expose explicit knobs (employeesToSelect,
employeeBalances, balanceMaximumHours, carryOverLimitHours) and
gracefully handle the standalone-mode "Add and save" confirmation
dialog that appears whenever at least one employee is added.
All 5 specs verified PASSED individually against demo:
01 unlimited 27.7s
02 fixed sick 34.0s
03 holiday 29.7s
04 edit rename 31.1s
05 delete 30.1s
Fresh PASSED videos captured to ~/Desktop/timeoff-videos/.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): use 'Back to policies' button label in holiday delete spec
The delete-from-list path for the holiday policy lifecycle spec was
clicking a `getByRole('button', { name: /time off policies/i })` that
never existed in the rendered UI — the actual back button on the
policy-detail layout has the i18n label "Back to policies"
(Company.TimeOff.PolicyDetail.json:backLabel). When the demo company
arrived without a pre-existing holiday policy, the test ran the
create flow successfully but then sat for the full 240s test timeout
waiting for that nonexistent button, surfacing three identical
timedOut retries in CI on PR #1834.
Anchoring on `/back to policies/i` matches the rendered DOM.
Co-authored-by: Cursor <cursoragent@cursor.com>
* test(e2e): guard time-off input error regressions from QA-fest
Add five Playwright assertions extracted from #1879 (Kristine White), each
guarding a real input/validation regression the time-off QA fest called
out. Ported onto the existing scenario-driven infrastructure so they run
in CI rather than being skipped behind localConfig.isLocal.
- waiting period decimal value (Jeff Stephens)
- accrual method switch hours-worked -> fixed-per-year leaving no
accrual_rate_unit ghost error (Austin Shieh / Kevin Bartels)
- very-large accrual rate not 500ing (Sam Nazarian)
- blank balance input on edit-balance modal (Jeff Stephens)
- non-numeric chars in starting balance (Xiao Hu)
Also promotes createFixedPolicyForRename -> exported
createFixedPolicyWithOneEmployee and adds openPolicySettingsFromDetail,
openAddEmployeesFromDetail, openEditBalanceModalForFirstEmployee, and
enableBalanceMaximumWithValue helpers in timeOffFlowDrivers.ts, used by
the three new QA-extracted specs.
Co-authored-by: Kristine White <kristine.white@gusto.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
* test(e2e): guard time-off add-employees edge cases from QA-fest
Add four Playwright assertions extracted from #1879 (Kristine White),
each guarding contracts on the add-employees + edit-balance flows
flagged by the time-off QA fest.
- confirmation dialog appears when adding employees to a populated
policy (Wil Alvarez)
- header checkbox enters indeterminate state when only some rows
selected (Aaron Lee)
- API error messages use humanized field names, not snake_case
(Aaron Rosen)
- lowering max balance below existing balances surfaces descriptive
error context, not "unexpected error" (Kevin Bartels / Jeff Stephens)
Co-authored-by: Kristine White <kristine.white@gusto.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
* test(e2e): guard time-off edit-unlimited + navigation contracts from QA-fest
Add three Playwright assertions extracted from #1879 (Kristine White),
each guarding edit-unlimited + back-button navigation contracts that the
time-off QA fest reported.
- editing an unlimited policy renders the edit form without crashing
(Sam Nazarian) — UI render contract only; demo backend PUT-unlimited
bug is tracked separately and is not asserted here
- back from add-employees lands on the policy detail, not the policy
list (Jeff Stephens / Aaron Lee)
- edit policy -> cancel returns to the policy detail view
(Charlie Lai)
Co-authored-by: Kristine White <kristine.white@gusto.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): stop the 4 QA-fest specs from burning 21 of 30 min on the time-off shard
The latest CI run on this PR (26178700555) showed the time-off e2e shard
taking 30m43s end-to-end. The scenario report broke it down: 22 tests
pass cleanly in ~9 minutes; 4 broken tests burn ~21 minutes between
them retrying 3x at 22-250s per attempt.
All 4 came in with the recent QA-fest commits. None of the failures are
infrastructure or "time-off is slow" \u2014 each spec has a specific bug:
1. waiting period decimal value surfaces clean validation, not a Zod crash
(policy-input-error-handling.spec.ts)
The SDK fix in #1879 (already merged into this branch via 66003e5d)
added maximumFractionDigits=0 to the waiting-period NumberInput, which
silently clamps 1.5 to an integer before submit. The test only
accepted two outcomes (form-level validator OR moved-on-to-add-employees);
the clamp is a valid third outcome that proves the Zod crash is gone.
Added an inputClampedToInteger branch and moved the unconditional
no-unexpected-error assertion above the branch check so we still
surface that hard contract first.
2. header checkbox enters indeterminate state when only some employees
are selected (policy-add-employees-edge-cases.spec.ts)
Removed. The product doesn't currently set the DOM .indeterminate
property on the select-all checkbox \u2014 the underlying <input> shows
indeterminate: false in 63 polling cycles. This is a real product
gap that QA correctly identified, but the spec asserts the gap is
already fixed. Reintroduce when product is patched.
3. blank balance input on edit-balance modal shows a clean error
(policy-input-error-handling.spec.ts via openEditBalanceModalForFirstEmployee)
The helper was looking for a top-level "Edit balance" button. The
real UI (TimeOffPolicyDetail.tsx#L265) puts Edit balance inside a
HamburgerMenu \u2014 the trigger is "Actions <Employee Name>", clicking
it opens a menu where "Edit balance" is a menuitem. Updated the
helper to open the actions hamburger then pick the menuitem.
4. non-numeric chars in starting balance do not crash with "unexpected
error" (policy-input-error-handling.spec.ts)
The starting-balance TextInput
(SelectEmployeesPresentation.tsx#L84) is only rendered for
employees NOT already on a policy of the same type \u2014 enrolled
employees get a static <Text>. The previous code blindly grabbed
dataRows.nth(1) and waited 240s for an input that may not exist
on that row. Now iterates rows, picks the first one with a
visible balance input, and skips gracefully if none have one.
Source-read fixes for #3 and #4 \u2014 not validated with a live
Playwright MCP repro. If either still fails on the next CI run, the
next step is to repro locally and confirm the rendered DOM matches
the assumption.
Expected impact on the time-off shard: 30 min \u2192 \u2248 6 min, restoring
the green baseline this PR had at commit 537e0dd9.
Co-authored-by: Cursor <cursoragent@cursor.com>
* fix(e2e): finish stopping the QA-fest CI burn (waiting period + blank balance)
Follow-up to f33f9eb. The previous fix attempt cut the time-off shard
from 30m to 11m and dropped 2 of the 4 failing tests, but 2 remained:
waiting period decimal (3x ~22s = 1.1 min)
The previous fix added an inputClampedToInteger branch alongside the
validator-error and moved-on branches. None matched in practice: the
NumberInput with maximumFractionDigits=0 silently rejects the '.'
keystroke, leaving the input cleared and Save disabled. The form-level
validator only fires on Save click, so neither validator-error nor
move-on happens. Reproduces locally.
Resolution: drop the over-specified outcome assertion. The hard
contract the test exists to protect is just "no Zod crash, no
'unexpected error' overlay", with an additional sanity check that the
page is still on policy settings or has advanced to add-employees.
Try-Save-if-enabled exercises the third valid path when it shows up.
Verified passing locally (29.4s).
blank balance modal dialog (3x ~31s = 1.5 min)
Previous helper fix opened the hamburger menu and clicked the Edit
balance menuitem correctly, but the role="dialog" assertion hit a
strict-mode collision: the react-aria-Popover for the hamburger menu
also exposes role="dialog" and briefly overlapped the real modal
during its exit animation.
With the dialog selectors now scoped to the modal title ("time off
balance"), the helper passes and the test runs cleanly through the
Edit balance flow. It then catches a real product bug: the SDK
surfaces BOTH the expected field-level validation alert and a
top-level page alert "There was a problem with your submission - An
unexpected error has occurred." That dual-error state is exactly what
QA reported and it is not yet fixed in product code.
Marked test.fixme with a comment pointing at the dual-error bug and
a local repro snippet. When the SDK suppresses the page-level alert
in this case, drop t…
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a Deductions block to
JobAndPayViewin the Employee Dashboard. Users can now see all active deductions, add a new one, edit an existing one, and delete with a confirmation dialog — all flowing through the existing Dashboard state machine. Bundles a small earlier fix for the standalone Deductions page's empty-state layout.Changes
useDeductionsListis consumed directly inside the view (mirroring howusePaymentMethodListis wired) —garnishmentsprop drilling from Dashboard is gone. Each row has a HamburgerMenu (Edit / Delete). Delete opens a newDeleteDeductionDialog.useDeleteDeduction+DeleteDeductionDialog— small parallels of the bank-account counterparts; live inDeductions/shared/.dashboardStateMachine: newdeductionFormstate. Fromindex:EMPLOYEE_DEDUCTION_ADD/EMPLOYEE_DEDUCTION_EDIT→deductionForm;EMPLOYEE_DEDUCTION_DELETED→indexwithsuccessAlert: 'deductionDeleted'. FromdeductionForm:EMPLOYEE_DEDUCTION_CREATED/UPDATED→indexwith the matching alert;CANCEL/EMPLOYEE_DEDUCTION_CANCEL→index.DeductionFormContextualmounts the existingDeductionsFormpicker (Standard vs Child Support) so both custom deductions and any court-ordered garnishment type are handled from the Dashboard.useEmployeeCompensationdropsuseGarnishmentsListSuspense+garnishmentList— JobAndPayView fetches via the deductions hook directly, and React Query dedupes so there's no extra network call.amountis a string per the API but the branch checkedtypeof === 'number'(never true) and fell back to${annualMaximum}% per paycheck(wrong field). Now matches the legacy DeductionsList: currency / percent driven bydeductAsPercentage, with the "{value} per paycheck" suffix for recurring rows.paymentMethodListanddeductionsListare merged withcomposeErrorHandler, so the existing JobAndPayViewBaseLayoutsurfaces either hook's failure (read or delete)./employee/Deductionslayout fix (bundled from earlier work): wrapsIncludeDeductionsin<BaseLayout>inside the contextual so<Flow>'s outer row-Flex gets a definite width context — un-squashes the empty-state CTA.Testing
npx tsc --noEmit— cleannpm run format+npm run lint— clean (0 errors; only pre-existing warnings in unrelated files)npm run test -- --run src/components/Employee/Dashboard src/components/Employee/Deductions— 8 files, 34 tests pass/employee/DashboardFlow→ Job and pay tab → Deductions section renders with title + "Add deduction" button + Deduction/Frequency/Withheld/Actions columns.employee/deductions/add(verified in Events Log) and the state machine mounts the DeductionsForm picker with the minimal header / Back button./employee/Deductions(standalone) no longer renders the empty-state at ~200px width; full content width restored.