Fix main: the French catalogue, the evening clock flake, and the router advisory by Aman-Mittal · Pull Request #825 · apache/fineract-backoffice-ui

Aman-Mittal · 2026-10-20T15:03:16Z

main is red. Six jobs fail across the two causes below, plus a dependency advisory. This fixes Translation Check, Unit Tests, Security Audit and the GA Readiness Gate, and diagnoses the two E2E shards it does not fix.

Not caused by what merged

Worth saying first, because it looked like a bad merge: no merged change is at fault for the clock failures. Lining the recent runs up by start time:

run start (UTC)	commit	result
19:07	`741b3075` (#817 merge)	4 failures
18:26	`7f7e55bc` (#819 merge)	4 failures
15:02	`41201a01`	all green
14:23	`c2cc7a13` (#816 merge)	all green
12:46	`bce5f224` (#819 branch head)	all green
08:04	`2f663f29`	all green
17:41	`144f2880`	all green

Every run started before 17:45 UTC is green; both runs started after 18:26 UTC are red, with the same four jobs. Asia/Kolkata is UTC+5:30, so its date turns over at 18:30 UTC — and AppConfig.tenantTimezone defaults to it.

1. Translation Check — a clean merge of two correct changes

This one is a merge artefact, and a textbook one: both sides were green and git had nothing to conflict on.

#816 renamed ON_HOLD_TRANSACTIONS.REASON to LOAN, because that column shows the loan the funds are held against and never held a reason. #819 was authored before that and translated the key as it then stood, in a file that did not exist on #816's branch. Different keys, different files, clean merge, broken catalogue — in both directions at once:

fr.json defines ON_HOLD_TRANSACTIONS.REASON, which en.json does not — remove it.
fr.json covers 2746 keys, down from 2747.

Motif becomes Prêt: a retranslation, not a rename, since the column means something else now.

The same merge left #817's sixteen password and access keys untranslated, for the same reason — that branch predated fr.json, so there was no French file to add them to. Translated here, which takes fr to 2763/2763, with the coverage baseline refreshed so the ratchet holds the gain instead of the old floor.

app.language.fr is added to hi.json as well: #819 registered French in the language pickers and labelled it for en and fr, so a Hindi user was offered the new language under a raw translation key.

2. Unit Tests — a latent flake, now deterministic

Two cases in group-action-dialog.component.test.ts asserted component.actionDate() against toIsoDate(new Date()) — the browser's today. The dialog resolves the tenant's today, deliberately, because the platform validates activate against a date it stamped in the tenant's zone. For five and a half hours each evening those are different days:

AssertionError: expected '2026-10-20' to be '2026-10-21'

The component is right and the spec was wrong. The spec's own header claimed these cases "hold whatever time it is"; they now do, by pinning the platform's clock through recordServerTime rather than reading the real one — and pinning it inside the window that was breaking them (20:00Z on the 15th, already the 16th in Asia/Kolkata), so the cases assert the tenant's date against a browser that would say the 15th. That is the disagreement they exist for.

offsetFromToday moved with it: it stepped the browser's clock with local getters, so the floor cases drifted on the same boundary. ISO arithmetic from the pinned date now, anchored at midday UTC so no offset can shift them.

Reverting the component to the browser clock fails 4 of 5 cases — before this it caught that regression only between 18:30 and midnight UTC. Confirmed on CI: Unit Tests passed on this branch at 23:51 UTC, inside the window that had been failing.

3. Security Audit and the GA Readiness Gate — the router advisory

Both fail for one reason:

@angular/router  22.0.0 - 22.2.0
Severity: high
Denial of Service via Unmatched Empty-Path Outlet Route Matching in SSR
Denial of Service via RouterLink Query Parameter Retention in SSR
fix available — 22.2.3

npm audit --audit-level=high --omit=dev is the audit job outright, and ga:check counts the same finding as its one blocking failure; the adapter-boundary backlog it also reports is advisory and pre-existing. Both go green, and the production tree is now at 0 vulnerabilities.

Worth being precise about the exposure, because it is not what the severity suggests: both advisories are server-side rendering denial of service, and this application has no @angular/ssr and does not render on a server. There was no live exposure to either. The upgrade clears a gate that is right to block on a high-severity advisory in the production tree; it does not close a hole that was open.

The whole Angular family moves together because it has to — the packages peer-depend on their own exact version, so @angular/router cannot move alone. The nine exact pins go to 22.2.3 and @angular/cdk follows its own caret to 22.2.4.

The lock is regenerated rather than amended, and that is the part worth reviewing. npm's incremental resolver refuses this upgrade against the existing lock — it holds @angular/platform-browser@22.2.0 from the lock while the root asks for 22.2.3 and reports ERESOLVE, whichever subset of the family is named on the command line. --legacy-peer-deps is not an option: the Dependency Integrity job exists to forbid exactly that. A clean resolve is what npm accepts, and it re-floats every caret range to its newest member, so 156 packages move in all — among them vitest, prettier, the angular-eslint plugins, playwright and the OpenAPI generator, each of which gates a job. Nothing leaves a range the project already declared, and the gates those moves could break were checked individually:

risk from the re-float	checked
`angular-eslint` 22.5.0 → 22.6.0, `eslint-plugin-security` 4.0.1 → 4.2.0	`lint:prune` 0 errors, `eslint-suppressions.json` untouched — no new findings
`prettier` 3.9.9 → 3.9.10	`format:check` clean on every tracked file
`vitest` 5.0.3 → 5.0.5, `jsdom` 30.1.2 → 30.1.3	314 files / 2589 tests green
`@openapitools/openapi-generator-cli` 2.41.0 → 2.42.0	`generate-api` → no drift; the generator jar is pinned at 7.20.0 in `openapitools.json`, independent of the CLI
`playwright` 1.64.0 → 1.64.1	mocked shard 3/4: 106 passed, 0 failed
the lock itself	`npm ci` resolves it clean

4. The two E2E shards — same cause as §2, not fixed here

Shard 1 holds group-membership.spec.ts, whose own comment reads "this run is UTC in CI against a tenant on Asia/Kolkata, which are different days after 18:30". Shard 3 holds tenant-date-defaults-backend.spec.ts, which exists for precisely this defect and moves the browser clock a day forward to provoke it.

This branch's own run sharpened the evidence: shard 3/3 passed when it ran at 02:07 UTC, and shard 1/3 failed when it ran at 19:19 UTC — the two shards, same commit, opposite results, split by the window.

They are left alone deliberately. Whether the fault is in those specs or in a residual browser-clock path in the application is exactly what a reproduction inside the window would tell us, and a guess at an E2E spec is not worth making. If it is the application, the user-facing bug is real: forms refused between 18:30 and midnight UTC for a Kolkata tenant, the same class as #496 and #798.

Also found, deliberately not touched

platform-date.service.test.ts → "prefers the platform clock over the browser clock" fails at UTC+14 (Pacific/Kiritimati): with no tenant timezone configured the service falls back to local rendering, by design, and the case assumes an offset where 10:00Z is still the 15th. CI runs at UTC, so this has never fired there and is not part of main being red. Left for its own change.

Checks

unit suite 314 files / 2589 tests green at UTC, at America/New_York and at Etc/GMT-10; test:mfe green — all three passes the job runs
the dialog spec green across six zones
npm ci clean, 0 production vulnerabilities, ga:check 10/11 with 0 blocking failures
lint:prune 0 errors with the suppressions ratchet unchanged, format:check clean, tsconfig.app.json and tsconfig.e2e.json type-clean
api:surface unchanged at 145 services / 642 operations; generate-api produces no drift
mocked e2e shard 3/4: 106 passed, 1 skipped, 0 failed
hi.json is a two-line diff: only the one missing label, with the file's existing key order left alone

`main` has been red on Translation Check since apache#819 merged, and neither apache#819 nor the change it landed beside was wrong on its own — both were green. apache#816 renamed `ON_HOLD_TRANSACTIONS.REASON` to `LOAN`, because the column shows the loan the funds are held against and never held a reason. apache#819 was authored before that and translated the key as it then stood. Git merged the two cleanly: they touch different keys in different files, so there was nothing to conflict. The result is a catalogue that disagrees with `en.json` in both directions at once: fr.json defines ON_HOLD_TRANSACTIONS.REASON, which en.json does not — remove it. fr.json covers 2746 keys, down from 2747. So `Motif` becomes `Prêt` — a retranslation rather than a rename, since the column means something else now. The same merge left the sixteen keys from apache#817's password and access work untranslated, for the same reason: that branch predated `fr.json` existing, so there was no French file for it to add them to. They are translated here, which takes `fr` to 2763/2763, and the coverage baseline is refreshed so the ratchet holds the gain rather than the old floor. `app.language.fr` is added to `hi.json` too. apache#819 registered French in the language pickers and gave `en` and `fr` a label for it, so a Hindi user was offered the new language under a raw translation key.

Unit Tests and two of the three real-Fineract E2E shards have been failing on `main`, and not because of anything that merged. They fail on the clock. Every run started before 17:45 UTC is green; both runs started after 18:26 UTC are red, with the same four jobs: 19:07Z apache#817 merge 4 failures 18:26Z apache#819 merge 4 failures 15:02Z all green 14:23Z apache#816 merge all green 12:46Z all green `Asia/Kolkata` is UTC+5:30, so its date turns over at 18:30 UTC. `AppConfig.tenantTimezone` defaults to it, which is the zone the dialog resolves today in — deliberately, because the platform validates `activate` against a date it stamped in the tenant's zone, not the browser's. Two cases here asserted `component.actionDate()` against `toIsoDate(new Date())`, the browser's today. For five and a half hours each evening those are different days, the component answers the tenant's and the assertion wants the browser's, and the job goes red: AssertionError: expected '2026-10-20' to be '2026-10-21' The spec's own header claimed these cases "hold whatever time it is". They now do, by pinning the platform's clock through `recordServerTime` instead of reading the real one. It is pinned inside the window that was breaking them — 20:00Z on the 15th, already the 16th in `Asia/Kolkata` — so the cases assert the tenant's date against a browser that would say the 15th, which is the disagreement they exist for. Verified green at `Asia/Kolkata`, `UTC`, `America/New_York`, `Etc/GMT-10`, `Etc/GMT+12` and `Pacific/Kiritimati`, and failing 4 of 5 when the component is reverted to the browser clock — before this it caught that regression only between 18:30 and midnight UTC. The relative dates move with it: `offsetFromToday` stepped the browser's clock with local getters, so the floor cases drifted on the same boundary. They are ISO arithmetic from the pinned date now, anchored at midday UTC so no offset can shift them. The two E2E shards are the same disagreement — shard 1 holds `group-membership.spec.ts` and shard 3 `tenant-date-defaults-backend.spec.ts`, both written for this window — but they are not addressed here. Reproducing them needs a live platform inside the window, and a guess at an E2E spec is not worth making.

github-actions · 2026-10-20T23:58:13Z

E2E — mocked backend

🎭 E2E Tests

✅ All green — 427 passed · 0 failed · 1 skipped, across 40 spec files in 8m 5s.

By spec file

Spec	✅	⏭️	Time
accessibility.spec.ts	5	0	23.8s
all-functions-read-shortcut.spec.ts	5	0	11.2s
branded-deployment.spec.ts	9	0	20.1s
breadcrumb.spec.ts	2	0	6.0s
client-date-picker-revisit.spec.ts	1	0	8.6s
client-servicing-gaps.spec.ts	14	0	1m 2s
client.spec.ts	1	0	4.3s
collateral-currency-search.spec.ts	5	0	20.1s
date-picker-revisit.spec.ts	6	0	27.1s
deployment-customization.spec.ts	19	0	40.4s
deposit-product-edit.spec.ts	2	0	7.8s
e2e-journey.spec.ts	81	0	3m 3s
feature-coverage.spec.ts	49	0	1m 43s
functional-coverage.spec.ts	42	0	1m 60s
global-search-nav-shortcuts.spec.ts	4	0	10.7s
global-search-navigation.spec.ts	8	0	22.1s
group-detail.spec.ts	8	0	34.7s
guidance-tour.spec.ts	5	1	14.8s
keyboard-shortcuts.spec.ts	5	0	11.2s
list-load-failure.spec.ts	5	0	18.8s
list-pagination.spec.ts	17	0	1m 10s
loan-delinquency-actions.spec.ts	11	0	46.1s
loan-portfolio-summary.spec.ts	4	0	16.3s
loan-product-down-payment.spec.ts	13	0	1m 0s
charge-refund.spec.ts	1	0	6.3s
client-accounts.spec.ts	2	0	9.5s
client-load-error.spec.ts	2	0	7.6s
contract-termination.spec.ts	1	0	7.6s
loan-schedule-type-gating.spec.ts	6	0	22.6s
loan-servicing-gaps.spec.ts	18	0	1m 8s
logout-reason-notice.spec.ts	4	0	3.9s
oidc-login.spec.ts	8	0	11.0s
rbac-feature-flag.spec.ts	11	0	20.7s
rbac-route-protection.spec.ts	18	0	1m 42s
report-enhancements.spec.ts	2	0	7.3s
reporting.spec.ts	2	0	3.4s
scheduler-jobs.spec.ts	3	0	10.8s
sidebar-active-state.spec.ts	1	0	1m 20s
two-factor-authentication.spec.ts	10	0	19.6s
working-capital-loan-actions.spec.ts	17	0	1m 12s

All 428 tests — click to expand

accessibility.spec.ts

✅ Runtime accessibility › client list has no blocking violations — 4.8s
✅ Runtime accessibility › client list links meet color contrast in dark mode — 4.6s
✅ Runtime accessibility › client form has no blocking violations — 5.2s
✅ Runtime accessibility › banner and dashboard content have no blocking violations — 4.4s
✅ Runtime accessibility › create office dialog has no blocking violations — 4.8s

all-functions-read-shortcut.spec.ts

✅ ALL_FUNCTIONS_READ shortcut › grants read access to the Clients list without any explicit READ_CLIENT permission — 2.3s
✅ ALL_FUNCTIONS_READ shortcut › does not grant the Create Client action — 2.5s
✅ ALL_FUNCTIONS_READ shortcut › does not grant Create Client even combined with an explicit READ_CLIENT permission — 2.2s
✅ ALL_FUNCTIONS_READ shortcut › a user with the real CREATE_CLIENT permission still sees the button — 2.0s
✅ ALL_FUNCTIONS_READ shortcut › ALL_FUNCTIONS (full superuser) still sees the Create Client button — 2.2s

branded-deployment.spec.ts

✅ a fully branded deployment › wears the institution’s name and mark, not Fineract’s — 2.0s
✅ a fully branded deployment › carries the institution’s palette into its own chrome and into Ionic — 2.2s
✅ a fully branded deployment › drops the sections the institution does not run — 2.0s
✅ a fully branded deployment › renames and reorders entries to the institution’s vocabulary — 2.0s
✅ a fully branded deployment › offers the institution’s own systems beside Fineract’s screens — 2.0s
✅ a fully branded deployment › restates the labels the institution words differently — 2.0s
✅ a fully branded deployment › keeps a readable palette in dark mode, with a label colour to match — 2.5s
✅ a fully branded deployment › does not leak a light colour into the dark palette — 2.0s
✅ a fully branded deployment › reports no configuration defects for the published example — 3.5s

breadcrumb.spec.ts

✅ a single-crumb page shows no breadcrumb trail — 2.0s
✅ a nested page shows a trail, and the ancestor crumb navigates back — 4.1s

client-date-picker-revisit.spec.ts

✅ Client form date pickers › stay usable on a second visit to the create form — 8.6s

client-servicing-gaps.spec.ts

✅ Client transfers › proposing a transfer sends the destination, the date and the format that parses it — 5.4s
✅ Client transfers › a one-step transfer omits the date the platform refuses — 4.6s
✅ Client transfers › the client’s own office is not offered as a destination — 4.2s
✅ Client transfers › accepting a transfer sends a note and nothing else — 4.6s
✅ Client transfers › accepting with no note sends an empty body — 4.3s
✅ Client transfers › rejecting a transfer is offered while one is pending — 4.3s
✅ Client transfers › withdrawing is offered from on hold, which is the only way back — 4.7s
✅ Client transfers › answers to a transfer are not offered when none is pending — 3.6s
✅ Client staff and default savings account › assigning a member of staff sends the staff id — 4.6s
✅ Client staff and default savings account › unassigning echoes the current holder back, which the platform requires — 4.8s
✅ Client staff and default savings account › unassigning is not offered when nobody is assigned — 3.6s
✅ Client staff and default savings account › the assigned officer is shown on the header — 4.0s
✅ Client staff and default savings account › setting the default savings account sends the account id — 4.7s
✅ Undoing a rejection › posts the command name the platform recognises, not the menu identifier — 4.6s

client.spec.ts

✅ Client Management › should create a new client — 4.3s

collateral-currency-search.spec.ts

✅ Collateral product currency — searchable select (#626) › the field is closed with no option list until it is opened — 4.1s
✅ Collateral product currency — searchable select (#626) › typing narrows a long, alphabetical list to the matching currency — 4.2s
✅ Collateral product currency — searchable select (#626) › matches by currency code as well as by name — 3.7s
✅ Collateral product currency — searchable select (#626) › shows a "no results" message rather than an empty panel — 4.0s
✅ Collateral product currency — searchable select (#626) › Cancel closes the picker without changing the selection — 4.1s

date-picker-revisit.spec.ts

✅ Date pickers on revisited forms › office form keeps its pickers usable on every visit — 4.2s
✅ Date pickers on revisited forms › staff form keeps its pickers usable on every visit — 4.6s
✅ Date pickers on revisited forms › holiday form keeps its pickers usable on every visit — 4.7s
✅ Date pickers on revisited forms › teller form keeps its pickers usable on every visit — 4.2s
✅ Date pickers on revisited forms › accounting closure form keeps its pickers usable on every visit — 4.6s
✅ Date pickers on revisited forms › floating rate form keeps its pickers usable on every visit — 4.8s

deployment-customization.spec.ts

✅ with no overlay mounted › boots, keeps the shipped branding, and shows the full menu — 2.1s
✅ with no overlay mounted › does not ask for an overlay this deployment has not declared — 1.9s
✅ with no overlay mounted › logs no federation parse error on load — 2.4s
✅ branding › applies colour and density tokens to the document — 2.0s
✅ branding › recolours Ionic through the same tokens — 2.0s
✅ branding › renames the product in the header and the tab title — 3.5s
✅ branding › serves the deployment logo and names it after the deployment — 2.0s
✅ branding › refuses a fill that cannot carry the white text baked into the stylesheet — 2.4s
✅ branding › accepts a light accent and derives a dark label for it — 2.0s
✅ branding › ignores a token outside the published allow-list, and says so — 2.0s
✅ navigation › hides an entry named by its id — 2.0s
✅ navigation › does not hide an entry named by its labelKey — 2.1s
✅ navigation › renames and reorders entries — 2.0s
✅ navigation › adds an external entry that opens in a new tab — 2.2s
✅ navigation › nests an added entry under an existing group — 1.9s
✅ navigation › gates an added entry on permissions like any built-in one — 2.0s
✅ navigation › drops an external entry with no usable url rather than rendering a dead link — 1.9s
✅ layering › merges over config.json instead of replacing it — 2.0s
✅ layering › a malformed overlay leaves the application usable — 2.0s

deposit-product-edit.spec.ts

✅ Editing a deposit product keeps what it was not asked to change › a fixed deposit product keeps its deposit amount, accounting and rate chart on save — 4.0s
✅ Editing a deposit product keeps what it was not asked to change › a recurring deposit product keeps its deposit amount, accounting and rate chart on save — 3.8s

e2e-journey.spec.ts

✅ E2E: Login Flow › should display login page with all required fields — 1.9s
✅ E2E: Login Flow › should have Sign In button disabled when fields are empty — 1.8s
✅ E2E: Login Flow › should enable Sign In when credentials are entered — 1.8s
✅ E2E: Login Flow › should redirect to dashboard after successful login — 2.0s
✅ E2E: Login Flow › should display language selector on login page — 1.8s
✅ E2E: Login Flow › should display API endpoint selector with value — 1.8s
✅ E2E: Dashboard › should display dashboard summary cards — 2.1s
✅ E2E: Dashboard › should display system health as Online — 2.0s
✅ E2E: Dashboard › should display pending approvals section — 2.5s
✅ E2E: Dashboard › should display loan and savings status distribution charts — 2.0s
✅ E2E: Dashboard › should display system operational status — 2.1s
✅ E2E: Dashboard › should have header with business date, render time, and logout — 2.0s
✅ E2E: Dashboard › should have sidebar toggle button — 2.0s
✅ E2E: Dashboard › should have global search bar in header — 1.9s
✅ E2E: Dashboard › should have Guide button in header — 2.2s
✅ E2E: Dashboard › should have dark mode toggle button — 2.1s
✅ E2E: Sidebar Navigation › should have all main navigation links — 2.1s
✅ E2E: Sidebar Navigation › should have Products section with sub-links — 2.1s
✅ E2E: Sidebar Navigation › should have Transfers section with sub-links — 2.2s
✅ E2E: Sidebar Navigation › should have Accounting section with sub-links — 2.0s
✅ E2E: Sidebar Navigation › should have Security section — 2.4s
✅ E2E: Sidebar Navigation › should have Settings section — 2.0s
✅ E2E: Sidebar Navigation › should have Organization section — 2.1s
✅ E2E: Sidebar Navigation › should have System section — 2.0s
✅ E2E: Sidebar Navigation › should navigate to all major pages via sidebar — 4.3s
✅ E2E: Offices › should display offices list with table — 2.4s
✅ E2E: Offices › should have Create Office button — 2.8s
✅ E2E: Offices › should navigate to office create form — 2.5s
✅ E2E: Offices › should validate office create form - save disabled when empty — 2.6s
✅ E2E: Offices › should fill office create form and enable save — 3.0s
✅ E2E: Offices › should cancel office creation and return to list — 2.7s
✅ E2E: Offices › should have search input on offices page — 2.4s
✅ E2E: Offices › should show edit button for each office — 2.9s
✅ E2E: Offices › should have pagination controls — 2.3s
✅ E2E: Clients › should display clients list page — 2.4s
✅ E2E: Clients › should display client data in table — 2.4s
✅ E2E: Clients › should show ACTIVE status badge — 2.3s
✅ E2E: Clients › should have Create Client button — 2.2s
✅ E2E: Clients › should show empty state when no clients exist — 2.3s
✅ E2E: Clients › should have search input and status filter — 2.2s
✅ E2E: Clients › should have pagination controls — 2.3s
✅ E2E: Client Creation › should navigate to client create form — 2.5s
✅ E2E: Client Creation › should display all required client form fields, across the wizard steps — 3.0s
✅ E2E: Client Creation › should display optional client form fields, across the wizard steps — 3.1s
✅ E2E: Client Creation › should have Next disabled until the current step is valid — 2.8s
✅ E2E: Client Creation › should populate office dropdown from API — 2.4s
✅ E2E: Client Creation › should fill client form and enable save on the last step — 3.1s
✅ E2E: Client Creation › should submit client and redirect to the new client view — 3.3s
✅ E2E: Client Creation › should cancel client creation and return to clients list — 2.4s
✅ E2E: Client Creation › should have add office quick-action button — 2.4s
✅ E2E: Client Creation › should have help icons for form fields — 2.0s
✅ E2E: Client Creation › should have calendar buttons for date fields — 2.4s
✅ E2E: Client Creation › should have pre-filled dates in Submitted On and Activation Date — 2.9s
✅ E2E: Client Creation › should have Active checkbox checked by default — 2.4s
✅ E2E: Client Creation › should handle Entity legal form showing fullname field — 3.4s
✅ E2E: Loan Products Page › should display loan products list page — 2.1s
✅ E2E: Loan Products Page › should have Create Loan Product button — 2.1s
✅ E2E: Loan Products Page › should display table with correct headers — 2.0s
✅ E2E: Loan Products Page › should show empty state when no products exist — 2.1s
✅ E2E: Loan Products Page › should have search input — 2.1s
✅ E2E: Loan Products Page › should navigate to loan product create form — 2.3s
✅ E2E: Savings Products Page › should display savings products list page — 2.2s
✅ E2E: Other Products Pages › Fixed Deposit Products page loads — 2.1s
✅ E2E: Other Products Pages › Recurring Deposit Products page loads — 1.7s
✅ E2E: Other Products Pages › Share Products page loads — 1.7s
✅ E2E: Other Products Pages › Tax Components page loads — 2.1s
✅ E2E: Other Products Pages › Tax Groups page loads — 2.0s
✅ E2E: Other Products Pages › Floating Rates page loads — 2.1s
✅ E2E: Loans Portfolio › should display loans portfolio page — 2.1s
✅ E2E: Loans Portfolio › should have Create Loan Account button — 2.0s
✅ E2E: Loans Portfolio › should display table with correct headers — 2.1s
✅ E2E: Loans Portfolio › should show empty state when no loans exist — 2.1s
✅ E2E: Loans Portfolio › should have search input — 2.0s
✅ E2E: Loans Portfolio › should have pagination controls — 2.1s
✅ E2E: Header & Global Elements › should display Fineract logo and title in header — 1.9s
✅ E2E: Header & Global Elements › should display logged-in username — 1.8s
✅ E2E: Header & Global Elements › should display office name for user — 1.9s
✅ E2E: Header & Global Elements › should have Logout button — 1.5s
✅ E2E: Header & Global Elements › should have language selector in header — 1.8s
✅ E2E: Header & Global Elements › should display render time — 2.3s
✅ E2E: Header & Global Elements › should display business date — 1.5s

feature-coverage.spec.ts

✅ Navigation & Sidebar › all main navigation links are visible in sidebar — 2.3s
✅ Navigation & Sidebar › sidebar navigation routes to correct pages — 2.6s
✅ Navigation & Sidebar › navigating to /accounting redirects to /accounting/chart-of-accounts — 2.9s
✅ Navigation & Sidebar › navigating to /organization redirects to /organization/offices — 3.0s
✅ Navigation & Sidebar › navigating to /system redirects to /system/data-tables — 3.3s
✅ Navigation & Sidebar › an unknown route keeps its URL and offers recovery actions — 3.2s
✅ Navigation & Sidebar › header shows logged-in user info — 1.9s
✅ Navigation & Sidebar › help tour button is visible and interactive — 1.9s
✅ Navigation & Sidebar › logout button is visible — 1.9s
✅ Navigation & Sidebar › language selector is present — 1.8s
✅ Dashboard › dashboard shows key metrics cards — 1.9s
✅ Dashboard › dashboard shows pending approvals section — 1.8s
✅ Dashboard › dashboard shows loan and savings status distribution — 1.5s
✅ Dashboard › dashboard shows system operational status — 2.0s
✅ Groups › groups page renders with title — 1.6s
✅ Groups › groups page has create button — 2.0s
✅ Centers › centers page renders with title — 2.0s
✅ Centers › centers page has create button — 2.0s
✅ Organization › offices page loads with list — 1.6s
✅ Organization › staff page loads — 2.1s
✅ Organization › funds page loads — 2.1s
✅ Organization › payment types page loads — 1.7s
✅ Accounting › chart of accounts loads — 2.0s
✅ Accounting › journal entries page loads — 2.2s
✅ Accounting › accounting closures loads — 2.0s
✅ Accounting › accounting rules loads — 2.1s
✅ Accounting › financial activity mappings loads — 2.0s
✅ Accounting › charges page loads — 1.7s
✅ Security › users page loads — 2.0s
✅ Security › roles page loads — 1.7s
✅ Security › audit logs page loads — 2.2s
✅ Security › leftover audit trails path lands on audits, not the dashboard — 3.3s
✅ Products - Loan & Savings › loan products page loads — 2.1s
✅ Products - Loan & Savings › savings products page loads — 1.7s
✅ Products - Loan & Savings › tax components page loads — 2.1s
✅ Products - Loan & Savings › tax groups page loads — 2.1s
✅ Products - Loan & Savings › floating rates page loads — 2.1s
✅ Products - Loan & Savings › savings accounts page loads — 2.1s
✅ Settings › global configurations page loads — 2.0s
✅ Settings › holidays page loads — 2.1s
✅ Settings › working days page loads — 2.0s
✅ System › data tables page loads — 2.1s
✅ System › bulk import page loads — 2.1s
✅ System › delinquency page loads — 2.2s
✅ Tellers › tellers page loads with create button — 2.0s
✅ Transfers › account transfer page loads — 2.1s
✅ Transfers › standing instructions page loads — 2.1s
✅ Transfers › SI history page loads — 2.0s
✅ Embedded Fintech › asset owners page loads — 2.0s

functional-coverage.spec.ts

✅ Client CRUD Workflow › should complete full client creation flow — Person — 3.9s
✅ Client CRUD Workflow › should complete full client creation flow — Entity — 3.2s
✅ Client CRUD Workflow › should cancel client creation and return to list — 2.3s
✅ Client CRUD Workflow › should disable office and legal form in edit mode — 3.3s
✅ Client View & Status Transitions › should display client view with correct details — 2.9s
✅ Client View & Status Transitions › should show actions menu for pending client (status 100) — 3.4s
✅ Client View & Status Transitions › should show actions menu for active client (status 300) — 3.6s
✅ Client View & Status Transitions › should show actions menu for closed client (status 600) — 3.5s
✅ Client View & Status Transitions › should show New Account menu for active client — 3.4s
✅ Client View & Status Transitions › should navigate from client view to client list via breadcrumb — 3.4s
✅ Client View & Status Transitions › should navigate back from client view — 3.5s
✅ Client View Tabs › should display all expected tabs on client view — 3.6s
✅ Client View Tabs › should switch between client view tabs — 3.2s
✅ Search & Filter Interactions › should have search input on clients page and accept input — 2.1s
✅ Search & Filter Interactions › should have office filter on groups page — 2.2s
✅ Search & Filter Interactions › should have office filter on loans page — 2.6s
✅ Search & Filter Interactions › should have search input on charges page — 2.4s
✅ Navigation Flow Verification › should navigate full client lifecycle: list → create → back → list — 2.9s
✅ Navigation Flow Verification › should navigate from dashboard to all top-level pages via sidebar — 4.7s
✅ Navigation Flow Verification › should go from loan products → create → back — 3.2s
✅ Office CRUD › should validate office create form — save disabled when empty — 2.5s
✅ Office CRUD › should validate office create form — save enabled when filled — 2.9s
✅ Office CRUD › should cancel office creation — 2.6s
✅ Organization Create Flows › staff create form loads — 2.6s
✅ Organization Create Flows › funds create form loads — 2.6s
✅ Organization Create Flows › payment types create form loads — 2.4s
✅ Accounting CRUD › accounting closure create form loads — 2.5s
✅ Accounting CRUD › accounting rule create form loads — 2.4s
✅ Accounting CRUD › financial activity mapping create form loads — 2.4s
✅ Accounting CRUD › charge create form loads — 2.7s
✅ Accounting CRUD › chart of accounts create form loads — 2.3s
✅ Settings CRUD › global configurations page has editable toggle — 2.2s
✅ Settings CRUD › holiday create form loads — 2.7s
✅ Settings CRUD › working days page has save button — 2.2s
✅ System CRUD › data table create form loads — 2.6s
✅ System CRUD › delinquency page has create buttons for ranges and buckets — 2.2s
✅ Security CRUD › role create form loads — 2.4s
✅ Security CRUD › audit logs search form has date range — 2.6s
✅ Security CRUD › audit logs list exports the loaded page as CSV — 2.5s
✅ Reporting — Run Report Flow › should navigate to report and verify report parameters — 3.7s
✅ Teller CRUD › teller create form loads — 2.5s
✅ Create Office Dialog from Client Form › should open create office dialog from client create form — 2.8s

global-search-nav-shortcuts.spec.ts

✅ Global search navigation shortcuts › offers a settings page the entity search cannot return — 2.3s
✅ Global search navigation shortcuts › navigates to the page behind a shortcut — 2.6s
✅ Global search navigation shortcuts › keeps the results open across the mousedown that starts a click, so a slow render cannot race the dropdown closed — 2.6s
✅ Global search navigation shortcuts › withholds a shortcut the user has no permission to reach — 3.2s

global-search-navigation.spec.ts

✅ Global search navigation › does not query the backend for a single character — 2.9s
✅ Global search navigation › sends one request for a phrase typed straight through — 3.3s
✅ Global search navigation › opens the client behind a client result — 2.6s
✅ Global search navigation › opens the loan behind a loan result — 2.7s
✅ Global search navigation › opens the savings account behind a savings result — 2.8s
✅ Global search navigation › clears the query and closes the dropdown after a selection — 2.4s
✅ Global search navigation › closes the dropdown when focus leaves without a selection — 2.5s
✅ Global search navigation › shows nothing rather than an empty dropdown when there are no matches — 2.8s

group-detail.spec.ts

✅ Group detail › custom field tabs expose the app keyboard and panel contract at 1280px — 4.4s
✅ Group detail › custom field tabs expose the app keyboard and panel contract at 390px — 4.1s
✅ Group detail › asks for the associations, and shows every member rather than only the active ones — 3.8s
✅ Group detail › closes a group with the reason id and a Fineract-formatted date — 5.9s
✅ Group detail › does not offer a client who is already a member, and associates the one it does — 4.2s
✅ Group detail › unassigns a committee role by the assignment id, not the role id — 4.2s
✅ Group detail › offers a retry when the group cannot be loaded — 3.8s
✅ Group detail › says so when no closure reason has been defined — 4.2s

guidance-tour.spec.ts

✅ the guided tour › highlights the System Status card, not the sidebar, on the dashboard tour — 2.4s
✅ the guided tour › presents the card as a dialog named and described by its own copy — 2.0s
✅ the guided tour › announces the step counter as a polite live region — 2.4s
✅ the guided tour › closes on Escape and hands focus back to the Guide button — 2.5s
✅ the guided tour › names an unmatched route after itself instead of handing it the dashboard tour — 3.5s
⏭️ the guided tour at a phone viewport › opens from the overflow menu as a full-width bottom sheet — 1.9s

keyboard-shortcuts.spec.ts

✅ Alt+C jumps straight to Create Client from anywhere — 2.3s
✅ Alt+G jumps to Create Group — 2.2s
✅ Alt+E jumps to Create Center — 2.7s
✅ Alt+H opens the guidance tour for the current page — 2.0s
✅ typing in the global search box does not trigger the Create Client shortcut — 2.0s

list-load-failure.spec.ts

✅ entity-to-entity mapping › renders the rows the endpoint returns, rather than claiming there are none — 3.4s
✅ entity-to-entity mapping › shows a failure state, not an empty one, when the payload cannot be read — 4.0s
✅ entity-to-entity mapping › retries and recovers — 3.8s
✅ report mailing jobs › reads rows out of the paged envelope the endpoint returns — 4.0s
✅ report mailing jobs › shows a failure state when the request errors — 3.6s

list-pagination.spec.ts

✅ Server total modes › shows an exact loan count of 1 without opting in — 3.6s
✅ Server total modes › shows an exact loan count of 11 without opting in — 4.2s
✅ Server total modes › shows an exact loan count of 21 without opting in — 3.7s
✅ Server total modes › keeps the unknown total for a full audit page — 3.6s
✅ List pagination › advances through pages and back again — 4.0s
✅ List pagination › jumps to the last page — 3.9s
✅ List pagination › returns to the first page when a filter changes — 4.4s
✅ List pagination › keeps search text when paging and shows the v2 account number — 4.5s
✅ List pagination › redirects the old search page and exposes only one client navigation item — 5.1s
✅ List pagination › keeps an account-number search broad and disables unsupported Office sorting — 4.5s
✅ List pagination › returns to the first page when searching — 5.0s
✅ Profile › renders the signed-in user rather than hanging on a spinner — 3.7s
✅ Profile › changes the signed-in user password from the profile screen — 3.9s
✅ Profile › shows an error when the profile cannot be loaded — 4.1s
✅ List load failure › reports the failure and reloads when the user retries — 3.8s
✅ List load failure › calendars: reports the failure and reloads when the user retries — 3.7s
✅ List load failure › accounting rules: reports the failure and reloads when the user retries — 4.0s

loan-delinquency-actions.spec.ts

✅ Delinquency pause and resume on a regular loan › shows the dates as dates, and the pause periods under their real fields — 3.7s
✅ Delinquency pause and resume on a regular loan › pauses delinquency for a period, from the business date — 4.9s
✅ Delinquency pause and resume on a regular loan › will not take a pause that ends before, or when, it starts — 4.4s
✅ Delinquency pause and resume on a regular loan › sends nothing when the pause dialog is cancelled — 4.9s
✅ Delinquency pause and resume on a regular loan › shows the platform’s own reason when it refuses a pause, and stays usable — 4.3s
✅ Delinquency pause and resume on a regular loan › resumes a pause that is in effect, dated the business date and with no end date — 4.7s
✅ Delinquency pause and resume on a regular loan › stops offering resume once the pause has been ended — 4.3s
✅ Delinquency pause and resume on a regular loan › does not offer resume when no pause is in effect — 3.6s
✅ Delinquency pause and resume on a regular loan › offers neither action without the permission to create a delinquency action — 4.0s
✅ Delinquency pause and resume on a regular loan › offers the permitted user the actions that permission opens, and no others — 3.5s
✅ Delinquency pause and resume on a regular loan › offers neither action on a loan that is not active — 3.7s

loan-portfolio-summary.spec.ts

✅ Loan Portfolio Summary › searching sends entities: loans and shows the grouped results — 3.9s
✅ Loan Portfolio Summary › Edit Parameters returns from the results view to the filter form — 4.0s
✅ Loan Portfolio Summary › checking the outstanding-amount filter sends the between min/max values — 3.9s
✅ Loan Portfolio Summary › switching to a single-value comparison condition sends one value — 4.5s

loan-product-down-payment.spec.ts

✅ Loan product down payment and tranches › down payment is offered only for a progressive product — 4.5s
✅ Loan product down payment and tranches › the percentage and auto-repayment appear only once down payment is on — 4.9s
✅ Loan product down payment and tranches › multi-tranche disbursement reveals its tranche count, on either engine — 3.9s
✅ Loan product down payment and tranches › submits the down payment and tranche settings it was given — 4.9s
✅ Loan product down payment and tranches › does not send a down payment on a cumulative product — 5.8s
✅ Loan product down payment and tranches › income recognition is offered only for a progressive product — 4.5s
✅ Loan product down payment and tranches › the capitalisation details appear only once it is on — 4.7s
✅ Loan product down payment and tranches › submits the income recognition settings it was given — 5.2s
✅ Loan product down payment and tranches › does not send income recognition on a cumulative product — 5.6s
✅ Loan product down payment and tranches › interest recalculation reveals its mandatory settings only once it is on — 3.8s
✅ Loan product down payment and tranches › the rest interval appears only when the frequency is not the repayment period — 4.9s
✅ Loan product down payment and tranches › submits the interest recalculation settings it was given — 4.1s
✅ Loan product down payment and tranches › does not send recalculation settings once it is switched back off — 3.7s

charge-refund.spec.ts

✅ refunds the remaining balance of a collected loan charge — 6.3s

client-accounts.spec.ts

✅ loan account rows show the principal returned by the accounts endpoint — 3.7s
✅ empty account tabs offer the matching creation action — 5.8s

client-load-error.spec.ts

✅ shows a not-found state and returns to the list, without an error toast — 3.8s
✅ offers a retry for a transient failure, and recovers on success — 3.8s

contract-termination.spec.ts

✅ terminates and undoes a progressive loan contract — 7.6s

loan-schedule-type-gating.spec.ts

✅ Loan schedule type gating › a cumulative loan offers neither progressive-only tab, and fetches neither — 3.8s
✅ Loan schedule type gating › a progressive loan shows only the capabilities it actually has — 4.0s
✅ Loan schedule type gating › fetches buy-down fees for a progressive loan that has no external id — 3.7s
✅ Loan schedule type gating › a progressive loan with both capabilities shows both — 3.8s
✅ Loan schedule type gating › a charged-off loan says so and offers the reversal instead — 3.8s
✅ Loan schedule type gating › a healthy loan offers charge-off and no marker — 3.5s

loan-servicing-gaps.spec.ts

✅ Loan servicing gaps › edits an interest pause through PUT while preserving its existing dates — 3.7s
✅ Loan servicing gaps › undo approval sends an empty body, without the locale the platform refuses — 3.9s
✅ Loan servicing gaps › undo approval carries the reason when one was given — 4.3s
✅ Loan servicing gaps › undo approval is offered only while the loan is approved — 3.5s
✅ Loan servicing gaps › the delinquency tab shows the summary the loan carries and the tags it fetches — 3.6s
✅ Loan servicing gaps › the data-only tabs stay hidden when the loan carries nothing for them — 3.6s
✅ Loan servicing gaps › each data-only tab appears and renders once the loan carries its data — 3.3s
✅ Loan servicing gaps › disburse to savings sends the date and amount, with the platform date format — 4.3s
✅ Loan servicing gaps › disburse to savings is offered only on an approved loan — 3.5s
✅ Loan servicing gaps › unassign loan officer sends the date, and appears only when one is assigned — 4.4s
✅ Loan servicing gaps › unassign loan officer is hidden on a loan with no officer — 3.5s
✅ Loan servicing gaps › undo last disbursal appears only on a multi-disbursal loan, and sends an empty body — 3.9s
✅ Loan servicing gaps › undo last disbursal is hidden on a single-disbursal loan — 3.5s
✅ Loan servicing gaps › close as rescheduled is offered on an active loan — 3.4s
✅ Loan servicing gaps › revising the amounts is offered on an approved loan — 3.4s
✅ Loan servicing gaps › revising the amounts is hidden before approval — 3.4s
✅ Loan servicing gaps › revising the approved amount sends the new amount and locale — 4.2s
✅ Loan servicing gaps › revising the available disbursement amount sends the new amount, including zero — 4.2s

logout-reason-notice.spec.ts

✅ explains an inactivity sign-out — 1.5s
✅ explains an expired session, with different wording — 1.9s
✅ stays silent when the user came to sign in of their own accord — 213ms
✅ stays silent for a reason it does not recognise, rather than showing a blank notice — 161ms

oidc-login.spec.ts

✅ identity-provider route on the login page › a deployment that never set the flag sees the screen it always saw — 1.2s
✅ identity-provider route on the login page › does not offer the route when the flag is false — 1.2s
✅ identity-provider route on the login page › does not offer the route when the flag is "true" — 1.2s
✅ identity-provider route on the login page › does not offer the route when the flag is 1 — 1.2s
✅ identity-provider route on the login page › offers the route above the password form, which stays in place — 1.3s
✅ identity-provider route on the login page › says plainly that it is not available yet, and goes nowhere — 1.8s
✅ identity-provider route on the login page › username and password still sign in when the route is offered — 2.0s
✅ identity-provider route on the login page › is not offered while a second factor is being asked for — 1.3s

rbac-feature-flag.spec.ts

✅ RBAC permission gating (rbacEnabled = true) › a limited user does not see permission-gated nav groups — 1.5s
✅ RBAC permission gating (rbacEnabled = true) › a user with READ_USER sees only the Security entries that permission covers — 1.8s
✅ RBAC permission gating (rbacEnabled = true) › the Security group fills in as the user is granted each of its permissions — 1.9s
✅ RBAC permission gating (rbacEnabled = true) › a superuser (ALL_FUNCTIONS) sees all permission-gated groups — 2.0s
✅ RBAC institution-feature gating (rbacEnabled = true) › universal institution shows Groups, Centers and Collection Sheet — 2.0s
✅ RBAC institution-feature gating (rbacEnabled = true) › commercial bank (cb) hides all group-lending features — 1.9s
✅ RBAC institution-feature gating (rbacEnabled = true) › credit union (cu) shows Groups but hides Centers and Collection Sheet — 2.0s
✅ rbacEnabled = false › restores the pre-RBAC behaviour of showing everything — 2.0s
✅ deployment navigation overrides › removes the entries the deployment names by id, leaving the rest alone — 1.8s
✅ deployment navigation overrides › ignores a labelKey where an id is required — 1.9s
✅ deployment navigation overrides › removes them even where RBAC is off — 1.9s

rbac-route-protection.spec.ts

✅ route authorization › a superuser reaches every sampled route and sees the full navigation — 13.2s
✅ route authorization › a single-module user is confined to that module — 9.2s
✅ route authorization › a read-only user gets the lists and not the forms — 11.2s
✅ route authorization › a user with an empty permission list is refused everywhere and the app still works — 9.6s
✅ route authorization › a session carrying no permissions field is treated as carrying none — 5.4s
✅ route authorization › an unrecognised permission code grants nothing — 5.4s
✅ route authorization › an unauthenticated visitor is asked to sign in, not told they are forbidden — 5.9s
✅ route authorization › a deployment with RBAC turned off behaves as it did before the guard — 7.7s
✅ the Access Denied page › says what happened, under a single heading — 3.4s
✅ the Access Denied page › moves focus to the heading, since the user did not ask to come here — 3.8s
✅ the Access Denied page › announces itself politely — 3.4s
✅ the Access Denied page › names the permissions the screen wanted, so the user can ask for them — 3.5s
✅ the Access Denied page › offers a way back that the user is allowed to take — 4.0s
✅ the Access Denied page › is reachable by keyboard alone — 3.9s
✅ permission feedback › a visible nav entry says what the user can do in that module — 1.3s
✅ permission feedback › a nav entry carries no hint when there is nothing specific to say — 1.9s
✅ navigation and routes agree › a hidden menu entry is also refused by URL, and a shown one is not — 5.1s
✅ navigation and routes agree › the create button is withheld from a user whose create route would refuse them — 3.9s

report-enhancements.spec.ts

✅ Report Enhancements, Pagination, and Help Tour › should run report, show paginated data, and download CSV — 4.0s
✅ Report Enhancements, Pagination, and Help Tour › should trigger guidance help tour and navigate steps — 3.3s

reporting.spec.ts

✅ Reporting › should display list of reports — 1.6s
✅ Reporting › should navigate to run report page — 1.8s

scheduler-jobs.spec.ts

✅ Scheduler Jobs bulk run › Run Selected is disabled until a job is checked — 3.2s
✅ Scheduler Jobs bulk run › Select All checks every job, and running confirms then triggers each one — 4.1s
✅ Scheduler Jobs bulk run › declining the confirmation runs nothing — 3.5s

sidebar-active-state.spec.ts

✅ Sidebar active route matching › does not mark a parent sidebar link active on nested routes — 1m 20s

two-factor-authentication.spec.ts

✅ two-step verification › asks for a code and lets the user in once it is accepted — 2.0s
✅ two-step verification › sends the token on every later request — 2.0s
✅ two-step verification › keeps the user on the step when the code is wrong, and says why — 1.8s
✅ two-step verification › accepts a correct code after a wrong one — 2.1s
✅ two-step verification › offers the choice when there is more than one channel — 1.7s
✅ two-step verification › says so when the account has no channel configured — 1.2s
✅ two-step verification › returns to the choice when the code could not be sent — 1.8s
✅ two-step verification › does not let a half-finished session reach the application — 3.8s
✅ two-step verification › backing out returns to the password form — 1.3s
✅ two-step verification › a deployment without a second factor signs in exactly as before — 1.9s

working-capital-loan-actions.spec.ts

✅ Working Capital loan delinquency, breach and near-breach actions, and originators › shows delinquency action history and submits a new one — 4.8s
✅ Working Capital loan delinquency, breach and near-breach actions, and originators › shows breach action history and submits a new one — 5.5s
✅ Working Capital loan delinquency, breach and near-breach actions, and originators › shows near-breach action history and submits a new one — 4.4s
✅ Working Capital loan delinquency, breach and near-breach actions, and originators › attaches and detaches a loan originator — 4.2s
✅ Working Capital loan delinquency, breach and near-breach actions, and originators › adds a new charge and waives an existing one — 5.0s
✅ Working Capital loan delinquency, breach and near-breach actions, and originators › shows rate-change history, amortization schedule, and delinquency range tags — 4.0s
✅ Working Capital loan delinquency, breach and near-breach actions, and originators › marks the loan as fraud, applies a discount, and changes the payment rate — 5.6s
✅ Working Capital loan transactions, loss actions and modification › credits the borrower through a goodwill credit — 4.7s
✅ Working Capital loan transactions, loss actions and modification › refunds a merchant payout — 3.9s
✅ Working Capital loan transactions, loss actions and modification › refunds a credit balance only on an overpaid loan — 4.3s
✅ Working Capital loan transactions, loss actions and modification › charges off an active loan — 3.9s
✅ Working Capital loan transactions, loss actions and modification › swaps charge-off for its undo once the loan is charged off — 3.5s
✅ Working Capital loan transactions, loss actions and modification › writes off an active loan — 4.2s
✅ Working Capital loan transactions, loss actions and modification › offers recovery and undo on a written-off loan, but not a second write-off — 3.7s
✅ Working Capital loan transactions, loss actions and modification › withholds undo write-off once a recovery has been collected — 3.1s
✅ Working Capital loan transactions, loss actions and modification › modifies a submitted application through the edit route — 4.5s
✅ Working Capital loan transactions, loss actions and modification › disables the actions a read-only role may not perform — 3.0s

Slowest 10 — what the shard counts should be tuned against

Test	Spec	Time
Sidebar active route matching › does not mark a parent sidebar link active on nested routes	`sidebar-active-state.spec.ts`	1m 20s
route authorization › a superuser reaches every sampled route and sees the full navigation	`rbac-route-protection.spec.ts`	13.2s
route authorization › a read-only user gets the lists and not the forms	`rbac-route-protection.spec.ts`	11.2s
route authorization › a user with an empty permission list is refused everywhere and the app still works	`rbac-route-protection.spec.ts`	9.6s
route authorization › a single-module user is confined to that module	`rbac-route-protection.spec.ts`	9.2s
Client form date pickers › stay usable on a second visit to the create form	`client-date-picker-revisit.spec.ts`	8.6s
route authorization › a deployment with RBAC turned off behaves as it did before the guard	`rbac-route-protection.spec.ts`	7.7s
terminates and undoes a progressive loan contract	`contract-termination.spec.ts`	7.6s
refunds the remaining balance of a collected loan charge	`charge-refund.spec.ts`	6.3s
route authorization › an unauthenticated visitor is asked to sign in, not told they are forbidden	`rbac-route-protection.spec.ts`	5.9s

📼 Download the HTML report, videos and traces — see the playwright-report-mocked artifact.

_{Generated by run 39626430537 from 8350ba1. The run executed a fork branch, so treat its contents as unverified.}

github-actions · 2026-10-20T23:58:14Z

E2E — real Fineract

🎭 E2E Tests

❌ 6 failing — 151 passed · 6 failed · 14 skipped · 8 flaky, across 50 spec files in 16m 41s.

❌ Failures

Accounting closures against Fineract › the form keeps the user on the page and names the reason when Fineract refuses — accounting-closure-backend.spec.ts
- Error: DELETE /glclosures/6 -> 403: {"developerMessage":"Request was understood but caused a domain rule violation.","httpStatusCode":"403","defaultUserMessage":"Errors contain reason for domain rule
a loan taken through four separated duties, every account built in the UI › the approver, differing from the officer in one code, is offered it and approves — loan-flows-non-admin-roles.spec.ts
- Error: expect(page).toHaveURL(expected) failed
Full feature demo recording › walk through loan schedule type, lifecycle, custom fields, collateral, and disbursement — full-demo.spec.ts
- Error: expect(page).toHaveURL(expected) failed
Loan lifecycle: creation, approval, disbursement › create, approve, and disburse a Cumulative loan — loan-lifecycle.spec.ts
- Error: expect(page).toHaveURL(expected) failed
a savings account taken through four separated duties, every account built in the UI › the approver, differing in one code, is offered it and approves — savings-flows-non-admin-roles.spec.ts
- Error: expect(page).toHaveURL(expected) failed
charge adjustment › adjusts a charge, and the outstanding amount follows — working-capital-servicing-backend.spec.ts
- Error: POST /working-capital-loans/15/charges -> 400: {"developerMessage":"The request was invalid. This typically will happen due to validation errors which are provided.","httpStatusCode":"400","def

⚠️ Passed on retry

Green overall, but these needed more than one attempt — the shape a flake takes.

a loan taken through four separated duties, every account built in the UI › an administrator builds the four roles and accounts through the forms — loan-flows-non-admin-roles.spec.ts (2 retry/retries)
a loan taken through four separated duties, every account built in the UI › the officer books the application and is not offered approval of their own loan — loan-flows-non-admin-roles.spec.ts (2 retry/retries)
Dynamic report parameters against Fineract › changing Office changes the Client Listing row set — report-parameter-backend.spec.ts (2 retry/retries)
a savings account taken through four separated duties, every account built in the UI › an administrator builds the five roles and accounts through the forms — savings-flows-non-admin-roles.spec.ts (2 retry/retries)
a savings account taken through four separated duties, every account built in the UI › the officer books the application and is not offered approval of it — savings-flows-non-admin-roles.spec.ts (2 retry/retries)
transaction corrections › undoes a repayment, and the platform marks it reversed — working-capital-servicing-backend.spec.ts (2 retry/retries)
transaction corrections › offers no correction on the disbursement, which the platform refuses by type — working-capital-servicing-backend.spec.ts (2 retry/retries)
transaction corrections › adjusts a repayment, which reverses it and books the new amount — working-capital-servicing-backend.spec.ts (2 retry/retries)

By spec file

Spec	✅	❌	⏭️	Time
backend.setup.ts	3	0	0	6.0s
accounting-closure-backend.spec.ts	1	1	0	14.7s
batch-api-operations.spec.ts	5	0	0	31.0s
center-servicing.spec.ts	2	0	0	19.0s
charge-servicing-backend.spec.ts	6	0	0	32.1s
client-legal-form-search.spec.ts	1	0	0	5.7s
client-transfer.spec.ts	4	0	0	49.4s
collection-sheet.spec.ts	1	0	0	7.5s
deposit-account-servicing.spec.ts	3	0	0	29.8s
deposit-lifecycle-backend.spec.ts	4	0	0	26.2s
deposit-product-configuration.spec.ts	3	0	0	19.7s
double-submit-backend.spec.ts	2	0	0	14.2s
form-layout-reflow.spec.ts	6	0	0	38.7s
group-membership.spec.ts	3	0	0	53.3s
loan-account-actions.spec.ts	3	0	0	26.8s
loan-approved-amount-revision.spec.ts	3	0	0	23.3s
loan-charge-off.spec.ts	2	0	0	22.2s
loan-flows-non-admin-roles.spec.ts	2	1	5	1m 22s
loan-product-accounting.spec.ts	1	0	0	35.3s
loan-repayment-gating.spec.ts	2	0	0	10.5s
loan-servicing-rbac-backend.spec.ts	4	0	0	11.4s
loan-servicing.spec.ts	2	0	0	20.4s
login.spec.ts	4	0	0	7.5s
oidc-login-backend.spec.ts	2	0	0	5.3s
parity-screens.spec.ts	8	0	0	49.8s
rbac-backend-restricted-user.spec.ts	7	0	0	41.9s
rbac-dead-end-controls.spec.ts	7	0	0	41.5s
rbac-disabled-flag-backend.spec.ts	6	0	0	30.4s
rbac-multi-permission.spec.ts	9	0	0	1m 9s
rbac-office-scoped-user.spec.ts	6	0	0	32.6s
bulk-import-entity-types.spec.ts	1	0	0	9.0s
delinquency-configuration.spec.ts	2	0	0	17.5s
full-demo.spec.ts	0	1	0	54.9s
interest-rate-charts.spec.ts	1	0	0	7.2s
loan-lifecycle.spec.ts	0	1	3	40.7s
loan-schedule-type.spec.ts	3	0	0	31.1s
rbac-permissionless-user.spec.ts	4	0	0	24.4s
report-mailing-job.spec.ts	3	0	0	20.6s
report-parameter-backend.spec.ts	4	0	0	24.4s
savings-flows-non-admin-roles.spec.ts	2	1	4	1m 24s
savings-transaction-correction.spec.ts	1	0	0	7.7s
savings-transaction-gating.spec.ts	2	0	0	7.0s
share-account-servicing.spec.ts	2	0	0	19.0s
share-product-accounting.spec.ts	1	0	0	25.9s
teller-cash-management.spec.ts	2	0	0	39.8s
tenant-date-defaults-backend.spec.ts	1	0	0	7.2s
working-capital-loan-actions-backend.spec.ts	3	0	0	23.6s
working-capital-product-accounting-backend.spec.ts	2	0	0	21.2s
working-capital-rbac-backend.spec.ts	2	0	0	7.8s
working-capital-servicing-backend.spec.ts	3	1	2	17.5s

All 171 tests — click to expand

backend.setup.ts

✅ seed backend reference data — 2.0s
✅ seed backend reference data — 2.0s
✅ seed backend reference data — 2.0s

accounting-closure-backend.spec.ts

✅ Accounting closures against Fineract › a closed period reads as Closed, and the platform refuses a posting inside it — 7.8s
❌ Accounting closures against Fineract › the form keeps the user on the page and names the reason when Fineract refuses — 6.8s (retried 2×)

batch-api-operations.spec.ts

✅ Batch API Operations against Fineract › runs the sample batch scenario — create client, create loan, add and read back a charge — 6.5s
✅ Batch API Operations against Fineract › shows a parse error instead of submitting when the batch input is not valid JSON — 7.5s
✅ Batch API enclosingTransaction semantics against Fineract › rolls back the earlier steps when enclosingTransaction is true and a later step fails — 5.5s
✅ Batch API enclosingTransaction semantics against Fineract › does not roll back the earlier steps when enclosingTransaction is false and a later step fails — 5.9s
✅ Batch API Operations on a mobile viewport against Fineract › the sample batch scenario is reachable and works by touch at mobile width — 5.6s

center-servicing.spec.ts

✅ Center servicing › a center is activated, staffed and given a group — 13.0s
✅ Center servicing › notes are recorded against the center — 6.0s

charge-servicing-backend.spec.ts

✅ loan charge servicing › waives a loan charge, and the platform records the waiver — 6.5s
✅ loan charge servicing › cannot reverse a waiver: the platform answers 500, not a business rule — 631ms
✅ loan charge servicing › offers no Pay on a charge the platform will not let be paid — 5.7s
✅ loan charge servicing › adjusts a loan charge to a smaller amount — 6.6s
✅ savings charge servicing › pays a savings charge with the amount and due date the platform demands — 6.1s
✅ savings charge servicing › carries an active flag, which is what gates Inactivate — 6.6s

client-legal-form-search.spec.ts

✅ Client list: legal form filtering › an entity client appears in the main client list — 5.7s

client-transfer.spec.ts

✅ Client transfer between offices › a proposed transfer is held until the destination accepts, and then the client moves — 12.2s
✅ Client transfer between offices › a rejected transfer leaves the client on hold, and withdrawing is the way back — 13.0s
✅ Client transfer between offices › a client can be transferred in one step when the user may act for both offices — 11.8s
✅ Client staff assignment › an officer can be assigned and then removed — 12.5s

collection-sheet.spec.ts

✅ Collection Sheet › scopes staff to the office, sends the choice, and reports an empty sheet — 7.5s

deposit-account-servicing.spec.ts

✅ Term deposit account servicing › an account is approved, activated and closed before maturity — 12.5s
✅ Term deposit account servicing › a deposit is recorded, listed, and reversed without leaving the list — 10.3s
✅ Term deposit account servicing › an application can be rejected instead of approved — 7.0s

deposit-lifecycle-backend.spec.ts

✅ fixed deposit products › carry the rate the user typed, not a hidden default — 5.8s
✅ an active fixed deposit account › shows its balance and maturity figures — 5.7s
✅ an active fixed deposit account › can be closed into the client savings account — 7.8s
✅ an active fixed deposit account › can have a charge added to it — 6.9s

deposit-product-configuration.spec.ts

✅ Deposit product configuration › a fixed deposit product survives being edited — 6.5s
✅ Deposit product configuration › a recurring deposit product can be created at all — 6.3s
✅ Deposit product configuration › a savings product carries its accounting configuration — 6.8s

double-submit-backend.spec.ts

✅ A double-click submits once › a repayment is recorded once, not twice — 7.0s
✅ A double-click submits once › a client is created once, not twice — 7.2s

form-layout-reflow.spec.ts

✅ form layout at the narrow viewport › Create GL Account gives every field a usable width at 320px — 5.8s
✅ form layout at the narrow viewport › Create Loan gives every field a usable width at 320px — 5.6s
✅ form layout at the narrow viewport › Create Office gives every field a usable width at 320px — 5.6s
✅ form layout at the narrow viewport › Create Staff gives every field a usable width at 320px — 5.3s
✅ form layout at the narrow viewport › no page-level horizontal scroll at 320px — 10.6s
✅ form layout at the wide viewport › Create GL Account still uses more than one column at 1280px — 5.8s

group-membership.spec.ts

✅ Group membership and lifecycle › a group is activated, staffed, given members and a committee, then emptied — 22.5s
✅ Group membership and lifecycle › notes are recorded against the group and can be removed again — 10.0s
✅ Group membership and lifecycle › an empty group is closed with a reason, and a group with members is refused — 20.8s

loan-account-actions.spec.ts

✅ Loan account lifecycle actions › new action menu items appear only for active loans — 7.6s
✅ Loan account lifecycle actions › undo disbursal shows a confirm dialog and reverts the loan to Approved — 10.1s
✅ Loan account lifecycle actions › write off requires confirmation and moves the loan out of Active status — 9.1s

loan-approved-amount-revision.spec.ts

✅ Loan approved and available-disbursement amount revision › revises the approved amount on an active, partially-disbursed loan — 7.4s
✅ Loan approved and available-disbursement amount revision › revises the available disbursement amount, which also changes the approved amount — 8.0s
✅ Loan approved and available-disbursement amount revision › shows the platform’s own refusal, not a generic validation message — 7.9s

loan-charge-off.spec.ts

✅ Loan servicing commands › charges a loan off through the UI and reverses it — 11.9s
✅ Loan servicing commands › records a goodwill credit through the shared transaction form — 10.3s

loan-flows-non-admin-roles.spec.ts

✅ a loan taken through four separated duties, every account built in the UI › an administrator builds the four roles and accounts through the forms — 40.4s (retried 2×)
✅ a loan taken through four separated duties, every account built in the UI › the officer books the application and is not offered approval of their own loan — 15.4s (retried 2×)
❌ a loan taken through four separated duties, every account built in the UI › the approver, differing from the officer in one code, is offered it and approves — 26.4s (retried 2×)
⏭️ a loan taken through four separated duties, every account built in the UI › the approver is not offered disbursement of the loan they just approved — 0ms (retried 2×)
⏭️ a loan taken through four separated duties, every account built in the UI › the disburser, holding only DISBURSE_LOAN, completes the payout end to end — 0ms (retried 2×)
⏭️ a loan taken through four separated duties, every account built in the UI › and the same route now refuses an UPDATE_LOAN holder, as the platform does — 0ms (retried 2×)
⏭️ a loan taken through four separated duties, every account built in the UI › a command with no mapped code is left to the platform rather than guessed at — 0ms (retried 2×)
⏭️ a loan taken through four separated duties, every account built in the UI › a repayment duty reaches its own form, and records a repayment — 0ms (retried 2×)

loan-product-accounting.spec.ts

✅ Loan product accounting › a cash-accounting product is configured, round-trips on edit, and posts to the ledger — 35.3s

loan-repayment-gating.spec.ts

✅ Repayment is offered only where the platform allows it › withheld on a loan awaiting approval, offered once it is active — 10.1s
✅ Repayment is offered only where the platform allows it › the platform refuses a repayment on a loan awaiting approval — 395ms

loan-servicing-rbac-backend.spec.ts

✅ loan servicing and charge command permissions, on the platform › each command is authorised by the code the UI declares for it — 5.4s
✅ loan servicing and charge command permissions, on the platform › no portfolio write code authorises any of its entity commands — 5.6s
✅ loan servicing and charge command permissions, on the platform › the deferred-income adjustments are not commands at loan level — 168ms
✅ loan servicing and charge command permissions, on the platform › the deferred-income adjustments are commands on one transaction — 185ms

loan-servicing.spec.ts

✅ Loan servicing: notes and transaction adjustment › notes can be added and removed, with a confirm dialog on delete — 9.3s
✅ Loan servicing: notes and transaction adjustment › a repayment transaction can be viewed and adjusted with a corrected amount — 11.1s

login.spec.ts

✅ Login › login page displays correctly — 1.8s
✅ Login › login form has required fields — 2.1s
✅ Login › submit button is disabled when form is empty — 1.8s
✅ Login › submit button is enabled when form is filled — 1.8s

oidc-login-backend.spec.ts

✅ identity-provider route against a real Fineract › is offered beside the password form, and pressing it sends nothing to Fineract — 1.8s
✅ identity-provider route against a real Fineract › a real password sign-in still gets a session with the route offered — 3.5s

parity-screens.spec.ts

✅ Screens added for platform parity › a manual journal entry can be read whole and reversed — 6.3s
✅ Screens added for platform parity › an entry that is already reversed is not offered again — 5.3s
✅ Screens added for platform parity › a report definition can be created, edited and deleted; a core one cannot — 6.6s
✅ Screens added for platform parity › a core report opens read-only with only its in-use setting — 5.6s
✅ Screens added for platform parity › a pending loan is approved from the queue, in a batch — 7.3s
✅ Screens added for platform parity › a fixed deposit is listed as a deposit, not as a savings account — 5.6s
✅ Screens added for platform parity › an office has a screen, and it carries its custom fields — 5.6s
✅ Screens added for platform parity › a savings account carries notes, and the note survives a reload — 7.5s

rbac-backend-restricted-user.spec.ts

✅ a genuinely restricted Fineract user › holds exactly the permissions their role was granted — 173ms
✅ a genuinely restricted Fineract user › reaches the screen their permission covers — 6.1s
✅ a genuinely restricted Fineract user › is refused a screen their permission does not cover, by URL and by the backend — 5.9s
✅ a genuinely restricted Fineract user › is refused a write screen they can read the list for, and the write itself — 7.9s
✅ a genuinely restricted Fineract user › is not offered the actions it would be refused for — 4.9s
✅ a genuinely restricted Fineract user › is shown an action it cannot take, disabled and saying what it needs — 6.8s
✅ a genuinely restricted Fineract user › the superuser the rest of the suite uses is unaffected — 10.1s

rbac-dead-end-controls.spec.ts

✅ a client's account tables › withhold the link, but not the number, from a user who cannot open the account — 5.9s
✅ a client's account tables › keep the link for a user who holds READ_LOAN — 6.4s
✅ the office transactions list › withholds Create from a reader, and the route refuses it too — 7.2s
✅ the office transactions list › offers Create to an administrator — 5.4s
✅ the office transactions list › refuses the list at the door for the code the platform does not check — 5.2s
✅ a group's member list › names the member without linking when the reader cannot open clients — 5.8s
✅ a group's member list › keeps the link for a reader who holds READ_CLIENT — 5.7s

rbac-disabled-flag-backend.spec.ts

✅ rbacEnabled: false, with a user who holds only READ_CLIENT › is shown the whole navigation, including modules their role does not cover — 3.9s
✅ rbacEnabled: false, with a user who holds only READ_CLIENT › is admitted by the route guard to a screen their role does not cover — 8.1s
✅ rbacEnabled: false, with a user who holds only READ_CLIENT › is still refused by Fineract, which the flag does not reach — 576ms
✅ rbacEnabled: false, with a user who holds only READ_CLIENT › is told the list is beyond their role, and not offered a retry that cannot succeed — 6.1s
✅ rbacEnabled: false, with a user who holds only READ_CLIENT › gets the same treatment on a second refused list, not a one-screen fix — 5.6s
✅ rbacEnabled: false, with a user who holds only READ_CLIENT › still loads the list their role does cover, with no failure state at all — 6.2s

rbac-multi-permission.spec.ts

✅ a route declaring more than one permission code (OR semantics) › is admitted by either declared code alone — 6.2s
✅ a route declaring more than one permission code (OR semantics) › is admitted by the other declared code alone — 5.7s
✅ a route declaring more than one permission code (OR semantics) › is refused when holding neither declared code, by the router and by the backend — 6.0s
✅ ALL_FUNCTIONS_READ, against the real Fineract permission catalogue › reaches read screens across modules it holds no specific code for — 10.8s
✅ ALL_FUNCTIONS_READ, against the real Fineract permission catalogue › is refused every write screen, and the writes themselves — 8.8s
✅ a restricted session across a real page reload › keeps the same permission boundary after reloading, not just after a fresh login — 12.3s
✅ a second real action-level gate, distinct from loan repayment › is shown the Approve action disabled and naming what it needs, refused by the backend too — 6.7s
✅ Security module writes (users, roles), against the real backend › reaches the list screens but is refused the write screens — 12.7s
✅ Security module writes (users, roles), against the real backend › is refused creating a user and modifying a role, by the backend itself — 245ms

rbac-office-scoped-user.spec.ts

✅ an account scoped to a branch office › differs from a head-office account in office alone, not in permissions — 347ms
✅ an account scoped to a branch office › is shown only its own office in the client list, and told which office it is in — 6.1s
✅ an account scoped to a branch office › sees a shorter list than an identically-permissioned head-office account — 5.6s
✅ an account scoped to a branch office › is refused another office’s client by the platform, and told so once — 6.1s
✅ an account scoped to a branch office › can still open the record that is in its own office — 5.7s
✅ an account scoped to a branch office › is not offered an edit it would be refused for on the Offices screen — 8.8s

bulk-import-entity-types.spec.ts

✅ every offered entity type is one the platform accepts — 9.0s

delinquency-configuration.spec.ts

✅ creates a delinquency range, then edits it — 9.1s
✅ creates a delinquency bucket from the ranges the template offers — 8.4s

full-demo.spec.ts

❌ Full feature demo recording › walk through loan schedule type, lifecycle, custom fields, collateral, and disbursement — 54.9s (retried 2×)

interest-rate-charts.spec.ts

✅ lists charts without a server error — 7.2s

loan-lifecycle.spec.ts

❌ Loan lifecycle: creation, approval, disbursement › create, approve, and disburse a Cumulative loan — 40.7s (retried 2×)
⏭️ Loan lifecycle: creation, approval, disbursement › create, approve, and disburse a Progressive loan — 0ms (retried 2×)
⏭️ Loan lifecycle: creation, approval, disbursement › an approved loan can be returned to pending approval — 0ms (retried 2×)
⏭️ Loan lifecycle: creation, approval, disbursement › the delinquency tab reads a real loan, and the empty data tabs stay hidden — 0ms (retried 2×)

loan-schedule-type.spec.ts

✅ Loan Schedule Type (Cumulative vs Progressive) › loan products list shows a schedule type chip per product — 7.8s
✅ Loan Schedule Type (Cumulative vs Progressive) › create a Progressive loan product end-to-end and verify it round-trips — 13.3s
✅ Loan Schedule Type (Cumulative vs Progressive) › loan creation shows the schedule type badge for a Progressive product — 10.0s

rbac-permissionless-user.spec.ts

✅ an account whose role grants nothing › is authenticated by Fineract and authorized by it for nothing — 833ms
✅ an account whose role grants nothing › is signed in and landed on a screen rather than stranded at the login form — 5.5s
✅ an account whose role grants nothing › is offered no permission-gated module, and refused each one by URL and by Fineract — 12.5s
✅ an account whose role grants nothing › is left a navigation whose entries actually work — 5.5s

report-mailing-job.spec.ts

✅ report mailing job creation › is no longer refused for a missing parameter — 6.3s
✅ report mailing job creation › the payload carries the locale and the schedule — 6.4s
✅ report mailing job creation at the narrow viewport › every field is reachable and the job still saves at 320px — 7.9s

report-parameter-backend.spec.ts

✅ Dynamic report parameters against Fineract › keeps the parameter form available when a report has cascading lookups — 5.2s
✅ Dynamic report parameters against Fineract › changing Office changes the Client Listing row set — 6.7s (retried 2×)
✅ Cascading report parameters against Fineract › sends the parent value to the child lookup and clears the child when it changes — 7.6s
✅ Chart reports against Fineract › renders a chart report as a chart rather than a table — 4.9s

savings-flows-non-admin-roles.spec.ts

✅ a savings account taken through four separated duties, every account built in the UI › an administrator builds the five roles and accounts through the forms — 49.6s (retried 2×)
✅ a savings account taken through four separated duties, every account built in the UI › the officer books the application and is not offered approval of it — 8.8s (retried 2×)
❌ a savings account taken through four separated duties, every account built in the UI › the approver, differing in one code, is offered it and approves — 25.2s (retried 2×)
⏭️ a savings account taken through four separated duties, every account built in the UI › the activator activates, and cannot take a deposit — 0ms (retried 2×)
⏭️ a savings account taken through four separated duties, every account built in the UI › the teller, holding only the transaction codes, records a deposit end to end — 0ms (retried 2×)
⏭️ a savings account taken through four separated duties, every account built in the UI › the cash-withdrawal control asks for the cash code, not the application one — 0ms (retried 2×)
⏭️ a savings account taken through four separated duties, every account built in the UI › the transaction route refuses an UPDATE_SAVINGSACCOUNT holder, as the platform does — 0ms (retried 2×)

savings-transaction-correction.spec.ts

✅ Savings transaction correction › a deposit is reversed and a hold is released — 7.7s

savings-transaction-gating.spec.ts

✅ Savings transactions are offered only on an active account › withheld while awaiting approval, offered once active — 6.7s
✅ Savings transactions are offered only on an active account › the platform refuses a deposit on an account awaiting approval — 253ms

share-account-servicing.spec.ts

✅ Share account servicing › an account is approved, activated, traded and closed — 12.9s
✅ Share account servicing › an application can be rejected — 6.2s

share-product-accounting.spec.ts

✅ Share product accounting › a share product is mapped to equity and round-trips on edit — 25.9s

teller-cash-management.spec.ts

✅ Teller cash management › a cashier is listed, receives an allocation, and settles cash back — 27.0s
✅ Teller cash management › settling more than the cashier holds is refused and the form stays usable — 12.8s

tenant-date-defaults-backend.spec.ts

✅ Date defaults come from the platform, not the browser › a client can be created while the browser is a day ahead — 7.2s

working-capital-loan-actions-backend.spec.ts

✅ Working Capital loan actions, against a real Fineract › charges off an active loan, and then offers only the undo — 8.7s
✅ Working Capital loan actions, against a real Fineract › credits the borrower with a goodwill credit, and the balance falls — 6.4s
✅ Working Capital loan actions, against a real Fineract › writes the loan off, which closes it and opens the recovery path — 8.5s

working-capital-product-accounting-backend.spec.ts

✅ Working Capital product accounting, on the platform › configures the accrual rule and its twelve accounts, and the platform accepts it — 15.5s
✅ Working Capital product accounting, on the platform › prefills a configured product and re-saves it without blanking anything — 5.7s

working-capital-rbac-backend.spec.ts

✅ Working Capital command permissions, on the platform › each command is authorised by the code the UI declares for it — 5.4s
✅ Working Capital command permissions, on the platform › UPDATE_WORKINGCAPITALLOAN authorises none of them — 2.4s

working-capital-servicing-backend.spec.ts

✅ transaction corrections › undoes a repayment, and the platform marks it reversed — 6.0s (retried 2×)
✅ transaction corrections › offers no correction on the disbursement, which the platform refuses by type — 5.3s (retried 2×)
✅ transaction corrections › adjusts a repayment, which reverses it and books the new amount — 5.9s (retried 2×)
❌ charge adjustment › adjusts a charge, and the outstanding amount follows — 259ms (retried 2×)
⏭️ custom datatables › adds, edits and deletes a row of a multi-row table on the loan — 0ms (retried 2×)
⏭️ custom datatables › creates a loan that a create-time check would otherwise refuse — 0ms (retried 2×)

Slowest 10 — what the shard counts should be tuned against

Test	Spec	Time
Full feature demo recording › walk through loan schedule type, lifecycle, custom fields, collateral, and disbursement	`full-demo.spec.ts`	54.9s
a savings account taken through four separated duties, every account built in the UI › an administrator builds the five roles and accounts through the forms	`savings-flows-non-admin-roles.spec.ts`	49.6s
Loan lifecycle: creation, approval, disbursement › create, approve, and disburse a Cumulative loan	`loan-lifecycle.spec.ts`	40.7s
a loan taken through four separated duties, every account built in the UI › an administrator builds the four roles and accounts through the forms	`loan-flows-non-admin-roles.spec.ts`	40.4s
Loan product accounting › a cash-accounting product is configured, round-trips on edit, and posts to the ledger	`loan-product-accounting.spec.ts`	35.3s
Teller cash management › a cashier is listed, receives an allocation, and settles cash back	`teller-cash-management.spec.ts`	27.0s
a loan taken through four separated duties, every account built in the UI › the approver, differing from the officer in one code, is offered it and approves	`loan-flows-non-admin-roles.spec.ts`	26.4s
Share product accounting › a share product is mapped to equity and round-trips on edit	`share-product-accounting.spec.ts`	25.9s
a savings account taken through four separated duties, every account built in the UI › the approver, differing in one code, is offered it and approves	`savings-flows-non-admin-roles.spec.ts`	25.2s
Group membership and lifecycle › a group is activated, staffed, given members and a committee, then emptied	`group-membership.spec.ts`	22.5s

📼 Download the HTML report, videos and traces — see the playwright-report-backend artifact.

_{Generated by run 39626430537 from 8350ba1. The run executed a fork branch, so treat its contents as unverified.}

github-actions · 2026-10-21T01:21:52Z

🔄 What this change talks to

No application TypeScript files changed, so there is nothing to draw.

_{Generated by run 39626430528 from 8350ba1. The run executed a fork branch, so treat its contents as unverified.}

…advisory Security Audit and the GA Readiness Gate both fail on `main` for one reason: @angular/router 22.0.0 - 22.2.0 Severity: high Denial of Service via Unmatched Empty-Path Outlet Route Matching in SSR Denial of Service via RouterLink Query Parameter Retention in SSR fix available — 22.2.3 `npm audit --audit-level=high --omit=dev` is the audit job outright, and `ga:check` counts the same finding as its one *blocking* failure ("1 blocking failure(s)"); the adapter-boundary backlog it also reports is advisory and pre-existing. Both go green on this upgrade, and the production tree is now at 0 vulnerabilities. Worth being precise about the exposure, because it is not what the severity suggests: both advisories are server-side rendering denial of service, and this application has no `@angular/ssr` and does not render on a server. There was no live exposure to either. The upgrade is to clear a gate that is right to block on a high-severity advisory in the production tree, not to close a hole that was open. The whole Angular family moves together because it has to: the packages peer-depend on their own exact version, so `@angular/router` alone cannot move. The nine exact pins go to 22.2.3, and `@angular/cdk` follows its own caret to 22.2.4. The lock is regenerated rather than amended. npm's incremental resolver refuses the upgrade against the existing lock — it holds `@angular/platform-browser@22.2.0` from the lock while the root asks for 22.2.3 and reports `ERESOLVE`, whichever subset of the family is named on the command line. `--legacy-peer-deps` is not an option here: the Dependency Integrity job exists to forbid exactly that. A clean resolve is what npm will accept, and it re-floats every caret range to its newest member, so 156 packages move in all — among them vitest, prettier, the angular-eslint plugins, playwright and the OpenAPI generator, each of which gates a job. Nothing leaves a range the project already declared. Verified against the gates those moves could break, rather than on the Angular bump alone: `npm ci` resolves the lock clean, 0 production vulnerabilities, `ga:check` 10/11 with no blocking failure, `lint:prune` 0 errors leaving `eslint-suppressions.json` untouched (the plugin bump found nothing new), `format:check` clean on every tracked file, both `tsconfig.app.json` and `tsconfig.e2e.json` type-clean, `api:surface` unchanged at 145 services and 642 operations, and the unit suite 314 files / 2589 tests green.

Aman-Mittal added 2 commits October 20, 2026 21:25

Aman-Mittal force-pushed the fix/main-ci-french-catalogue-and-clock-flake branch from 7382713 to af97825 Compare October 20, 2026 15:56

Aman-Mittal changed the title ~~Fix main: complete the French catalogue, and stop the evening clock flake~~ Fix main: the French catalogue, the evening clock flake, and the router advisory Oct 21, 2026

Aman-Mittal merged commit 9406940 into apache:main Oct 21, 2026
12 of 14 checks passed

Navigation Menu

Repository navigation

Fix main: the French catalogue, the evening clock flake, and the router advisory - #825

Fix main: the French catalogue, the evening clock flake, and the router advisory#825
Aman-Mittal merged 3 commits into
apache:mainfrom
Aman-Mittal:fix/main-ci-french-catalogue-and-clock-flake

Aman-Mittal commented Oct 20, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Oct 20, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Oct 20, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Oct 21, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

Aman-Mittal commented Oct 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Not caused by what merged

1. Translation Check — a clean merge of two correct changes

2. Unit Tests — a latent flake, now deterministic

3. Security Audit and the GA Readiness Gate — the router advisory

4. The two E2E shards — same cause as §2, not fixed here

Also found, deliberately not touched

Checks

Uh oh!

github-actions Bot commented Oct 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

E2E — mocked backend

🎭 E2E Tests

By spec file

Uh oh!

github-actions Bot commented Oct 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

E2E — real Fineract

🎭 E2E Tests

❌ Failures

⚠️ Passed on retry

By spec file

Uh oh!

github-actions Bot commented Oct 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔄 What this change talks to

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Aman-Mittal commented Oct 20, 2026 •

edited

Loading

github-actions Bot commented Oct 20, 2026 •

edited

Loading

github-actions Bot commented Oct 20, 2026 •

edited

Loading

github-actions Bot commented Oct 21, 2026 •

edited

Loading