Repository navigation
feat(working-capital): transaction corrections, charge adjustment, product accounting and custom datatables - #802
Merged
Aman-Mittal merged 5 commits intoOct 17, 2026
Conversation
Closes apache#773. The transactions tab was a read-only table: a mistaken repayment could not be reversed from this application at all, and no screen showed how a transaction was allocated between principal, fees and penalties. A row now opens a detail panel carrying the allocation, the external id and the reversal state, with the three corrections the module supports — `undo`, `adjust` and, for a discount fee, `discountFeeAdjustment`. Reversed rows are struck through *and* carry a text marker, because strike-through alone reads to a screen reader as money that moved. ## Which corrections are offered, and why those `WorkingCapitalLoanWritePlatformServiceImpl` switches on the transaction type: undo accepts WAIVE_CHARGES, REPAYMENT, GOODWILL_CREDIT, CHARGE_ADJUSTMENT and PAYOUT_REFUND, and adjust the same list without the waiver — a waiver has no amount to re-state. Everything else answers 400 `validation.msg.wc.loan.transaction.{undo,adjust}.not.supported`. Measured against `apache/fineract:latest` as well as read: undo of a disbursement is refused by type, undo of a repayment and of a charge adjustment succeed, undo of an already-reversed transaction is refused, and adjust reverses the original and books a replacement. A discount fee carries no boolean flag on its type enum — there is one per type and none for this one — so it is recognised by `loanTransactionType.discountFee`, and it takes `discountFeeAdjustment` rather than `adjust`. ## Permissions Each button carries its own code, and the diagonal was measured the way apache#691 and apache#777 established: a role holding exactly one code, the command sent with an empty body, 403 against anything else. | Command | Code | | ----------------------- | ------------------------------------------ | | `undo` | `UNDO_WORKINGCAPITALLOANTRANSACTION` | | `adjust` | `ADJUST_WORKINGCAPITALLOANTRANSACTION` | | `discountFeeAdjustment` | `DISCOUNTFEEADJUSTMENT_WORKINGCAPITALLOAN` | `UPDATE_WORKINGCAPITALLOAN` authorises none of them, as it authorises none of the commands in apache#777. `ADJUST_WORKINGCAPITALLOANTRANSACTION` was missing from `scripts/permission-codes.json`, so the snapshot is refreshed from the live platform: 707 codes against the recorded 720, which had drifted in both directions since 3 October. ## Maker-checker With maker-checker on for the command, Fineract answers 200 with a `commandId` and no `resourceId`: the reversal is queued and nothing has happened to the loan yet. The panel says so instead of re-reading and showing the transaction unchanged with no explanation. `commandId` is absent from the generated response type because the OpenAPI document does not describe that branch. ## Why a panel rather than a route The issue proposes a detail route. A new routed component cannot be written today without naming Ionic and the generated client directly, which ADR 0005 and ADR 0006 forbid outside `src/app/ui` and the API adapters — and the form primitives those ADRs plan do not exist yet, so there is nothing to build the amount and date fields from. `eslint-suppressions.json` may only shrink, so the detail lives in the already-suppressed loan screen that owns the tab. The loan route is read-gated, which is what the issue asks the detail route to be, and each action still carries its own code.
…-fee transactions Closes apache#774. Charges could be added and waived. They could not be opened, so the amount paid, the amount waived and what was still outstanding were invisible, and a charge entered wrongly could only be waived in full. The discount fee could only be set through `PUT /discount`, so the two commands that post it as a transaction were unreachable. ## The charge panel A charge row now opens a panel with its paid, waived and outstanding amounts, its due date, its calculation type and whether it is a penalty, plus **Adjust**. `amount` is the only parameter `command=adjustment` takes: an empty body answers `validation.msg.workingCapitalLoanChargeAdjustment.amount.cannot.be.blank`, and the platform dates the adjustment itself rather than accepting a date — so the form asks for an amount and sends nothing else. The adjustment is prefilled with what is outstanding, which is both the usual figure and the platform's cap. An adjustment books a **Charge Adjustment transaction**, so the panel, the charge list, the transactions tab and the loan header are all re-read after it. A waiver does too, and only the charge list was being refreshed before, so a waived charge left a transactions tab that did not show the waiver — fixed here because the panel made it visible. ## The discount fee `discountFee` joins the action route and the dispatch map, and the loan menu offers it on an active loan that has no discount yet: Fineract refuses a second one with "Discount was already set before disbursement and cannot be added again", and a loan priced with a discount at disbursement reads back carrying it. Changing an agreed discount stays the `PUT /discount` sub-resource that "Apply discount" opens — a different operation with a different code. `discountFeeAdjustment` corrects a posted discount fee and acts on one transaction rather than on the loan, so it lives on the transaction panel from apache#773 rather than on this route. Measured against `apache/fineract:latest`: - `discountFee` takes `transactionAmount` and `transactionDate`; the date is what the platform resolves the related disbursement from, and its response `changes` name the disbursement it picked. - Its template answers with the currency and the classification options and *no* amount, so unlike every other amount-bearing command there is no figure to offer — the user enters it. ## Permissions | Action | Code | | ----------------------- | ------------------------------------------ | | Adjust charge | `ADJUSTMENT_WORKINGCAPITALLOANCHARGE` | | Waive charge | `WAIVE_WORKINGCAPITALLOANCHARGE` | | Post discount fee | `DISCOUNTFEE_WORKINGCAPITALLOAN` | | Adjust discount fee | `DISCOUNTFEEADJUSTMENT_WORKINGCAPITALLOAN` | Probed the same way as the rest: each code authorises exactly its own command and is refused every other, and `UPDATE_WORKINGCAPITALLOAN` is refused all of them. The guess worth recording as wrong is that posting the discount fee might need `UPDATEDISCOUNT_WORKINGCAPITALLOAN`, the code for the agreed discount. It does not, in either direction.
…t allocation Closes apache#775. The Working Capital product form offered `accountingRule` and nothing else, so a product saved with a posting rule had no GL accounts mapped and nothing it booked could post. It also could not set the payment allocation, which decides how a repayment settles fees, penalties and principal. ## The rule itself could not be saved The select bound each option's `code` — the dotted `wcAccountingRuleType.none` spelling — and the platform accepts only the name: POST /working-capital-loan-products {"accountingRule": "wcAccountingRuleType.none"} → 400 …accountingRule.is.not.one.of.expected.enumerations So *any* product saved after touching that select was refused, and the field was one a user would reasonably touch first. The shared accounting section binds `id`, which is the name. This is why the form now uses that section rather than keeping its own select. ## Nineteen slots, twelve of them mandatory Enumerated from the platform the way the other five families were — post the rule with no mapping ids and read the 400: fundSourceAccountId, loanPortfolioAccountId, transfersInSuspenseAccountId, deferredIncomeLiabilityAccountId, incomeFromDiscountFeeAccountId, receivableFeeAccountId, receivablePenaltyAccountId, incomeFromFeeAccountId, incomeFromPenaltyAccountId, incomeFromRecoveryAccountId, writeOffAccountId, overpaymentLiabilityAccountId Seven more — the charge-off, fraud and goodwill-credit slots — are accepted and not demanded, so they are offered as optional. `AccountingMappingField` gains `required`, which defaults to true: every slot of the five original families is mandatory under the rules that name it, because each of those lists was enumerated from such a 400 in the first place. Two differences from the term-loan list look like omissions and are not. There is **no interest slot** — this product earns a discount fee, and `incomeFromDiscountFeeAccountId` is the mandatory slot in its place — and there is a **deferred income liability**, because the fee is recognised over the loan's life and the unearned part has to sit somewhere. No other family has that slot. The module also has only two rules, `NONE` and `ACC_DEF_REV_AM`: no cash basis and no choice of accrual timing. The shared model and section are generalised from a numeric rule to `number | string` to carry that, with the "none" sentinel and the posting rules passed in; the other five families call them unchanged. ## Reason mappings `chargeOffReasonToExpenseAccountMappings` and `writeOffReasonsToExpenseMappings` route a loss to an expense account by *why* it happened — fraud separately from insolvency — which several jurisdictions require reported separately. Both are new UI: the term-loan form has neither. The trap they exist to absorb: the request keys disagree (`chargeOffReasonCodeValueId` against `writeOffReasonCodeValueId`) while **both** read back under `reasonCodeValue`. One mapping holds all three spellings, so an edit cannot silently drop the table it did not name — the same class of defect `advancedMappingsFromResponse` was written for. ## Payment allocation The existing editor is reused with two new inputs. The Working Capital product has no future-installment allocation rule — its template returns no such options and the parameter is refused — and no credit allocation, so both are turned off rather than rendered empty. A new product starts with `DEFAULT` over all six rules, which is what the platform accepts; an edit loads the product's own. ## The `READ_GLACCOUNT` case in the issue does not arise here The issue asks for a clear message where a user holds `UPDATE_WORKINGCAPITALLOANPRODUCT` but not `READ_GLACCOUNT`, on the premise that the picker loads `/glaccounts`. It does not: the account options come from the product template, and a user holding only the two product codes gets all four option lists back — measured. There is no call to be refused and no empty select to explain. The real empty case is a tenant with no accounts of a class, which the platform signals by omitting the list, and the section already says so per group. ## Verification Measured against `apache/fineract:latest`: a product created with all nineteen accounts, both reason tables, a payment-channel mapping and the full allocation is accepted, and reads back with each slot under the `Id`-less key the prefill expects.
… per table Closes apache#776. An institution can attach datatables to `m_wc_loan` and `m_wc_loan_product` — `EntityTables` declares both — and this UI had nowhere to see or enter that data, so any field a tenant had defined for these loans could not be captured at all. Working Capital loans get a **Custom fields** tab, and the product form a custom fields section on edit (a datatable row is keyed by the product, so there is nothing to attach one to until it exists). ## The shared component gains permissions and row editing `EntityDatatablesComponent` listed every registered table and offered Add only. It now: - **lists only the tables the user can read.** Removed rather than disabled, which is right here: a table they cannot read has no rows to show, so a tab would be an empty panel with nothing to explain. It also stops the component fetching rows that can only answer 403. - **gates Add, Edit and Delete** on the generated code for that table, disabled with the missing code named. - **edits and deletes a row**, which needs the one-row and many-row cases told apart. The listing carries no `multiRow` flag, so the shape is the discriminator: a multi-row table's primary key is its own `id` and the entity key rides alongside, while a single-row table's primary key *is* the entity key. That decides the URL — `…/{table}/{entityId}/{rowId}` against `…/{table}/{entityId}` — and both were measured by registering one of each. Codes are generated per table with the registered name **verbatim**: `READ_wc_kyc`, not an upper-cased form. `permissionsSatisfy` already implements both platform shortcuts, so a read-only auditor sees every tab and no enabled write control with no special case here. This reaches beyond Working Capital: clients, groups, centres, offices, loans and deposit accounts render the same component, so a user without a table's `READ_` code no longer sees a tab whose rows would 403. ## Create-time checks are honoured, not reported A tenant can register a datatable as a CREATE check on `m_wc_loan`, and then: POST /working-capital-loans (no datatables) → 403 Please fill in the data table [wc_kyc] before creating this working capital loan. The row cannot be added afterwards either — the create request carries the rows inline — so the application form reads the checks that apply (`status=100`, `entity=m_wc_loan`), collects each table's fields, and sends them as `datatables: [{registeredTableName, data}]`. Submit is held back while one is outstanding, rather than letting the user fill a long form and collect a 403. The fields are rendered by the existing entry dialog in a new collect-only mode, which hands the values back instead of posting them. That keeps one renderer for datatable fields rather than a second copy of it on this form, and reopening it shows what was entered. Measured end to end: with the check registered the application is refused, and the same application carrying the inline row is accepted.
…ble paths against a real Fineract The mocked specs prove the screens post the right command with the right body. They cannot prove the platform accepts any of it, and for everything apache#773 to apache#776 added the interesting rules are the platform's: which transaction types accept a correction, what a charge adjustment takes, which GL accounts a posting rule demands, and what a create-time datatable check refuses. ## `working-capital-servicing-backend.spec.ts` Six journeys through the screen, each checked against what the platform then reports: - undo a repayment → the transaction reads back reversed; - the disbursement offers no correction at all, which is the type gate the module enforces (`Undo is not supported for transaction type DISBURSEMENT`); - adjust a repayment → the original is reversed *and* a replacement for the new amount exists, which is what adjust does rather than editing in place; - adjust a charge → a Charge Adjustment transaction appears in the transactions tab, the half a charge-screen mock cannot show; - add, edit and delete a row of a multi-row datatable on the loan; - create a loan that a registered CREATE check would otherwise refuse, with the required row collected on the form and sent inline. ## `working-capital-product-accounting-backend.spec.ts` Two, both about the shape of the agreement rather than the screen: - configure the accrual rule and its twelve mandatory accounts through the form, and read the product back: the rule saved as `ACC_DEF_REV_AM` and each slot under its `Id`-less response key. This is the test that would have caught the form sending the dotted `wcAccountingRuleType.*` code, which the platform refuses; - open a fully configured product and re-save it with only the name changed. Nothing may be lost: the response renames every key it was written with, so a form that read it wrongly would post the product with its accounting stripped. ## The RBAC probe now reads the reason, not the status `working-capital-rbac-backend.spec.ts` gains the five pairs from apache#773 and apache#774, taking the measured diagonal to 22, and had to get stricter to do it: the probe treated any 403 as "not authorised", and the platform also answers 403 for a **domain rule violation**. On a charge another spec had already waived, `WAIVE_WORKINGCAPITALLOANCHARGE` looked unauthorised. `notAuthorisedAs` reads the globalisation code instead, which separates "you may not" from "not like that". `UPDATE_WORKINGCAPITALLOAN` still authorises none of the 22. ## Seeding `seed-api.ts` gains the Working Capital charge (`chargeAppliesTo` 5, and specified-due-date is the only charge time type the module accepts — a disbursement-time charge answers `error.msg.wc.loan.charge.time.type.not.supported`), a repayment poster, GL accounts by class, the two loss-reason code values, the datatables in both shapes, and the create check with an idempotent teardown. Two defects in the existing seeding came out of this and are fixed: - the product short name was built from the *leading* characters of a base-36 timestamp, which every run within the same minute shares, so two runs a minute apart collided on `Wcez`. It now takes the trailing three. - `removeEntityDatatableCheck` threw on a failed delete, and ran in a `finally` where Playwright had already disposed the request context — so a timeout in the test body was reported as a failed DELETE. It warns instead. ## Verification All four Working Capital backend specs together: 14 pass in 46s against `apache/fineract:latest`. The mocked suite is unchanged and still passes — 17 loan-action tests and 27 RBAC tests. One note for whoever reads the output: configuring the GL selects raises the interval-sampling `NG0100` on `ng-untouched` that issue apache#572 documents, which the fixture classifies as a known artifact and does not enforce. It comes from `NgControlStatus` on a programmatically set `ngModel`, not from this change.
Contributor
🔄 What this change talks toFrom the 14 application TypeScript file(s) changed in this pull request. sequenceDiagram
autonumber
participant LoanProductFormComponent as LoanProductFormComponent (Component)
participant FundsService as FundsService (API client)
participant Fineract as Fineract (REST API)
participant DelinquencyRangeAndBucketsManagementServ as DelinquencyRangeAndBucketsManagementService (API client)
participant LoanProductsService as LoanProductsService (API client)
participant Router as Router (Injected)
participant SavingsProductFormComponent as SavingsProductFormComponent (Component)
participant SavingsProductService as SavingsProductService (API client)
participant ShareProductFormComponent as ShareProductFormComponent (Component)
participant I18N as I18N (Injected)
participant ProductsService as ProductsService (API client)
participant WcLoanProductFormComponent as WcLoanProductFormComponent (Component)
LoanProductFormComponent->>FundsService: getFunds()
FundsService->>Fineract: getFunds()
Fineract-->>FundsService: response
LoanProductFormComponent->>DelinquencyRangeAndBucketsManagementServ: getDelinquencyBuckets()
DelinquencyRangeAndBucketsManagementServ->>Fineract: getDelinquencyBuckets()
Fineract-->>DelinquencyRangeAndBucketsManagementServ: response
LoanProductFormComponent->>LoanProductsService: getLoanproductsTemplate()
LoanProductsService->>Fineract: getLoanproductsTemplate()
Fineract-->>LoanProductsService: response
LoanProductFormComponent->>LoanProductsService: getLoanproductsProductId()
LoanProductsService->>Fineract: getLoanproductsProductId()
Fineract-->>LoanProductsService: response
LoanProductFormComponent->>LoanProductsService: putLoanproductsProductId()
LoanProductsService->>Fineract: putLoanproductsProductId()
Fineract-->>LoanProductsService: response
LoanProductFormComponent->>Router: navigate()
LoanProductFormComponent->>LoanProductsService: postLoanproducts()
LoanProductsService->>Fineract: postLoanproducts()
Fineract-->>LoanProductsService: response
SavingsProductFormComponent->>SavingsProductService: getSavingsproductsTemplate()
SavingsProductService->>Fineract: getSavingsproductsTemplate()
Fineract-->>SavingsProductService: response
SavingsProductFormComponent->>SavingsProductService: getSavingsproductsProductId()
SavingsProductService->>Fineract: getSavingsproductsProductId()
Fineract-->>SavingsProductService: response
SavingsProductFormComponent->>SavingsProductService: putSavingsproductsProductId()
SavingsProductService->>Fineract: putSavingsproductsProductId()
Fineract-->>SavingsProductService: response
SavingsProductFormComponent->>Router: navigate()
SavingsProductFormComponent->>SavingsProductService: postSavingsproducts()
SavingsProductService->>Fineract: postSavingsproducts()
Fineract-->>SavingsProductService: response
ShareProductFormComponent->>I18N: translate()
ShareProductFormComponent->>ProductsService: getProductsTypeTemplate()
ProductsService->>Fineract: getProductsTypeTemplate()
Fineract-->>ProductsService: response
ShareProductFormComponent->>ProductsService: getProductsTypeProductId()
ProductsService->>Fineract: getProductsTypeProductId()
Fineract-->>ProductsService: response
ShareProductFormComponent->>ProductsService: putProductsTypeProductId()
ProductsService->>Fineract: putProductsTypeProductId()
Fineract-->>ProductsService: response
ShareProductFormComponent->>Router: navigate()
Truncated for readability: 23 further participant(s) and 3 further call(s) not shown.
Generated by run 39037788799 from |
Contributor
E2E — mocked backend🎭 E2E Tests✅ All green — 423 passed · 0 failed · 1 skipped · 1 flaky, across 40 spec files in 6m 46s.
|
| Spec | ✅ | ❌ | ⏭️ | 🔒 | Time |
|---|---|---|---|---|---|
| accessibility.spec.ts | 5 | 0 | 0 | 0 | 32.8s |
| all-functions-read-shortcut.spec.ts | 5 | 0 | 0 | 0 | 10.2s |
| branded-deployment.spec.ts | 9 | 0 | 0 | 0 | 19.0s |
| breadcrumb.spec.ts | 2 | 0 | 0 | 0 | 5.7s |
| client-date-picker-revisit.spec.ts | 1 | 0 | 0 | 0 | 6.7s |
| client-servicing-gaps.spec.ts | 14 | 0 | 0 | 0 | 1m 2s |
| client.spec.ts | 1 | 0 | 0 | 0 | 3.8s |
| collateral-currency-search.spec.ts | 5 | 0 | 0 | 0 | 18.4s |
| date-picker-revisit.spec.ts | 6 | 0 | 0 | 0 | 28.9s |
| deployment-customization.spec.ts | 19 | 0 | 0 | 0 | 37.7s |
| deposit-product-edit.spec.ts | 2 | 0 | 0 | 0 | 7.3s |
| e2e-journey.spec.ts | 81 | 0 | 0 | 0 | 3m 4s |
| feature-coverage.spec.ts | 49 | 0 | 0 | 0 | 1m 52s |
| functional-coverage.spec.ts | 42 | 0 | 0 | 0 | 2m 0s |
| global-search-nav-shortcuts.spec.ts | 4 | 0 | 0 | 0 | 9.7s |
| global-search-navigation.spec.ts | 8 | 0 | 0 | 0 | 21.0s |
| group-detail.spec.ts | 8 | 0 | 0 | 0 | 34.8s |
| guidance-tour.spec.ts | 5 | 0 | 1 | 0 | 13.7s |
| keyboard-shortcuts.spec.ts | 5 | 0 | 0 | 0 | 10.7s |
| list-load-failure.spec.ts | 5 | 0 | 0 | 0 | 18.6s |
| list-pagination.spec.ts | 13 | 0 | 0 | 0 | 55.2s |
| loan-delinquency-actions.spec.ts | 11 | 0 | 0 | 0 | 43.6s |
| loan-portfolio-summary.spec.ts | 4 | 0 | 0 | 0 | 14.4s |
| loan-product-down-payment.spec.ts | 13 | 0 | 0 | 0 | 58.4s |
| charge-refund.spec.ts | 1 | 0 | 0 | 0 | 4.9s |
| client-accounts.spec.ts | 2 | 0 | 0 | 0 | 6.5s |
| client-load-error.spec.ts | 2 | 0 | 0 | 0 | 4.9s |
| contract-termination.spec.ts | 1 | 0 | 0 | 0 | 6.2s |
| loan-schedule-type-gating.spec.ts | 6 | 0 | 0 | 0 | 14.4s |
| loan-servicing-gaps.spec.ts | 18 | 0 | 0 | 0 | 49.0s |
| logout-reason-notice.spec.ts | 4 | 0 | 0 | 0 | 2.7s |
| oidc-login.spec.ts | 8 | 0 | 0 | 0 | 10.1s |
| rbac-feature-flag.spec.ts | 11 | 0 | 0 | 0 | 14.5s |
| rbac-route-protection.spec.ts | 18 | 0 | 0 | 0 | 1m 21s |
| report-enhancements.spec.ts | 2 | 0 | 0 | 0 | 6.1s |
| reporting.spec.ts | 2 | 0 | 0 | 0 | 3.3s |
| scheduler-jobs.spec.ts | 3 | 0 | 0 | 0 | 8.5s |
| sidebar-active-state.spec.ts | 1 | 0 | 0 | 0 | 58.8s |
| two-factor-authentication.spec.ts | 10 | 0 | 0 | 0 | 14.2s |
| working-capital-loan-actions.spec.ts | 17 | 0 | 0 | 0 | 52.8s |
All 424 tests — click to expand
accessibility.spec.ts
- ✅ Runtime accessibility › client list has no blocking violations —
4.5s - ✅ Runtime accessibility › client list links meet color contrast in dark mode —
4.1s - ✅ Runtime accessibility › client form has no blocking violations —
5.0s - ✅ Runtime accessibility › banner and dashboard content have no blocking violations —
15.0s - ✅ Runtime accessibility › create office dialog has no blocking violations —
4.2s
all-functions-read-shortcut.spec.ts
- ✅ ALL_FUNCTIONS_READ shortcut › grants read access to the Clients list without any explicit READ_CLIENT permission —
2.4s - ✅ ALL_FUNCTIONS_READ shortcut › does not grant the Create Client action —
1.9s - ✅ ALL_FUNCTIONS_READ shortcut › does not grant Create Client even combined with an explicit READ_CLIENT permission —
2.0s - ✅ ALL_FUNCTIONS_READ shortcut › a user with the real CREATE_CLIENT permission still sees the button —
1.9s - ✅ ALL_FUNCTIONS_READ shortcut › ALL_FUNCTIONS (full superuser) still sees the Create Client button —
2.0s
branded-deployment.spec.ts
- ✅ a fully branded deployment › wears the institution’s name and mark, not Fineract’s —
2.1s - ✅ a fully branded deployment › carries the institution’s palette into its own chrome and into Ionic —
2.0s - ✅ a fully branded deployment › drops the sections the institution does not run —
1.7s - ✅ a fully branded deployment › renames and reorders entries to the institution’s vocabulary —
1.9s - ✅ 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 —
1.9s - ✅ 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.4s
breadcrumb.spec.ts
- ✅ a single-crumb page shows no breadcrumb trail —
2.2s - ✅ a nested page shows a trail, and the ancestor crumb navigates back —
3.5s
client-date-picker-revisit.spec.ts
- ✅ Client form date pickers › stay usable on a second visit to the create form —
6.7s
client-servicing-gaps.spec.ts
- ✅ Client transfers › proposing a transfer sends the destination, the date and the format that parses it —
5.1s - ✅ Client transfers › a one-step transfer omits the date the platform refuses —
5.0s - ✅ Client transfers › the client’s own office is not offered as a destination —
4.4s - ✅ Client transfers › accepting a transfer sends a note and nothing else —
4.5s - ✅ Client transfers › accepting with no note sends an empty body —
4.6s - ✅ Client transfers › rejecting a transfer is offered while one is pending —
4.4s - ✅ Client transfers › withdrawing is offered from on hold, which is the only way back —
4.9s - ✅ 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.7s - ✅ Client staff and default savings account › unassigning echoes the current holder back, which the platform requires —
4.3s - ✅ Client staff and default savings account › unassigning is not offered when nobody is assigned —
3.8s - ✅ Client staff and default savings account › the assigned officer is shown on the header —
3.5s - ✅ Client staff and default savings account › setting the default savings account sends the account id —
4.5s - ✅ Undoing a rejection › posts the command name the platform recognises, not the menu identifier —
4.3s
client.spec.ts
- ✅ Client Management › should create a new client —
3.8s
collateral-currency-search.spec.ts
- ✅ Collateral product currency — searchable select (#626) › the field is closed with no option list until it is opened —
3.5s - ✅ Collateral product currency — searchable select (#626) › typing narrows a long, alphabetical list to the matching currency —
3.8s - ✅ Collateral product currency — searchable select (#626) › matches by currency code as well as by name —
3.5s - ✅ Collateral product currency — searchable select (#626) › shows a "no results" message rather than an empty panel —
3.3s - ✅ Collateral product currency — searchable select (#626) › Cancel closes the picker without changing the selection —
4.2s
date-picker-revisit.spec.ts
- ✅ Date pickers on revisited forms › office form keeps its pickers usable on every visit —
4.1s - ✅ Date pickers on revisited forms › staff form keeps its pickers usable on every visit —
4.5s - ✅ Date pickers on revisited forms › holiday form keeps its pickers usable on every visit —
5.1s - ✅ Date pickers on revisited forms › teller form keeps its pickers usable on every visit —
4.1s - ✅ Date pickers on revisited forms › accounting closure form keeps its pickers usable on every visit —
4.3s - ✅ Date pickers on revisited forms › floating rate form keeps its pickers usable on every visit —
6.8s(retried 1×)
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.6s - ✅ with no overlay mounted › logs no federation parse error on load —
2.1s - ✅ branding › applies colour and density tokens to the document —
2.0s - ✅ branding › recolours Ionic through the same tokens —
1.9s - ✅ branding › renames the product in the header and the tab title —
3.1s - ✅ branding › serves the deployment logo and names it after the deployment —
2.1s - ✅ branding › refuses a fill that cannot carry the white text baked into the stylesheet —
2.0s - ✅ branding › accepts a light accent and derives a dark label for it —
2.1s - ✅ branding › ignores a token outside the published allow-list, and says so —
1.7s - ✅ 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 —
1.7s - ✅ navigation › adds an external entry that opens in a new tab —
2.0s - ✅ navigation › nests an added entry under an existing group —
1.7s - ✅ navigation › gates an added entry on permissions like any built-in one —
1.6s - ✅ navigation › drops an external entry with no usable url rather than rendering a dead link —
2.1s - ✅ layering › merges over config.json instead of replacing it —
1.7s - ✅ layering › a malformed overlay leaves the application usable —
1.9s
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 —
3.3s - ✅ 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 —
4.0s
e2e-journey.spec.ts
- ✅ E2E: Login Flow › should display login page with all required fields —
1.3s - ✅ E2E: Login Flow › should have Sign In button disabled when fields are empty —
1.3s - ✅ E2E: Login Flow › should enable Sign In when credentials are entered —
1.4s - ✅ E2E: Login Flow › should redirect to dashboard after successful login —
2.1s - ✅ E2E: Login Flow › should display language selector on login page —
1.3s - ✅ 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 —
1.7s - ✅ E2E: Dashboard › should display pending approvals section —
1.8s - ✅ E2E: Dashboard › should display loan and savings status distribution charts —
1.9s - ✅ 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 —
1.9s - ✅ E2E: Dashboard › should have global search bar in header —
2.1s - ✅ E2E: Dashboard › should have Guide button in header —
1.7s - ✅ 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.0s - ✅ E2E: Sidebar Navigation › should have Transfers section with sub-links —
1.7s - ✅ E2E: Sidebar Navigation › should have Accounting section with sub-links —
1.8s - ✅ E2E: Sidebar Navigation › should have Security section —
2.1s - ✅ E2E: Sidebar Navigation › should have Settings section —
1.7s - ✅ E2E: Sidebar Navigation › should have Organization section —
1.7s - ✅ E2E: Sidebar Navigation › should have System section —
2.0s - ✅ E2E: Sidebar Navigation › should navigate to all major pages via sidebar —
4.5s - ✅ E2E: Offices › should display offices list with table —
2.5s - ✅ E2E: Offices › should have Create Office button —
2.4s - ✅ E2E: Offices › should navigate to office create form —
2.5s - ✅ E2E: Offices › should validate office create form - save disabled when empty —
2.5s - ✅ E2E: Offices › should fill office create form and enable save —
3.0s - ✅ E2E: Offices › should cancel office creation and return to list —
2.8s - ✅ E2E: Offices › should have search input on offices page —
2.0s - ✅ E2E: Offices › should show edit button for each office —
2.0s - ✅ E2E: Offices › should have pagination controls —
2.4s - ✅ E2E: Clients › should display clients list page —
2.1s - ✅ E2E: Clients › should display client data in table —
2.6s - ✅ E2E: Clients › should show ACTIVE status badge —
2.4s - ✅ E2E: Clients › should have Create Client button —
2.1s - ✅ E2E: Clients › should show empty state when no clients exist —
2.1s - ✅ E2E: Clients › should have search input and status filter —
1.9s - ✅ E2E: Clients › should have pagination controls —
2.3s - ✅ E2E: Client Creation › should navigate to client create form —
2.8s - ✅ E2E: Client Creation › should display all required client form fields, across the wizard steps —
3.4s - ✅ E2E: Client Creation › should display optional client form fields, across the wizard steps —
3.0s - ✅ 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.8s - ✅ E2E: Client Creation › should fill client form and enable save on the last step —
3.4s - ✅ E2E: Client Creation › should submit client and redirect to clients list —
3.6s - ✅ E2E: Client Creation › should cancel client creation and return to clients list —
2.8s - ✅ E2E: Client Creation › should have add office quick-action button —
2.6s - ✅ E2E: Client Creation › should have help icons for form fields —
1.9s - ✅ E2E: Client Creation › should have calendar buttons for date fields —
3.2s - ✅ E2E: Client Creation › should have pre-filled dates in Submitted On and Activation Date —
3.2s - ✅ E2E: Client Creation › should have Active checkbox checked by default —
2.6s - ✅ E2E: Client Creation › should handle Entity legal form showing fullname field —
3.8s - ✅ E2E: Loan Products Page › should display loan products list page —
2.0s - ✅ E2E: Loan Products Page › should have Create Loan Product button —
2.4s - ✅ E2E: Loan Products Page › should display table with correct headers —
2.5s - ✅ E2E: Loan Products Page › should show empty state when no products exist —
2.0s - ✅ E2E: Loan Products Page › should have search input —
2.0s - ✅ E2E: Loan Products Page › should navigate to loan product create form —
2.7s - ✅ E2E: Savings Products Page › should display savings products list page —
2.4s - ✅ E2E: Other Products Pages › Fixed Deposit Products page loads —
2.3s - ✅ E2E: Other Products Pages › Recurring Deposit Products page loads —
2.4s - ✅ E2E: Other Products Pages › Share Products page loads —
2.0s - ✅ E2E: Other Products Pages › Tax Components page loads —
2.3s - ✅ E2E: Other Products Pages › Tax Groups page loads —
2.3s - ✅ E2E: Other Products Pages › Floating Rates page loads —
1.9s - ✅ E2E: Loans Portfolio › should display loans portfolio page —
2.1s - ✅ E2E: Loans Portfolio › should have Create Loan Account button —
2.3s - ✅ E2E: Loans Portfolio › should display table with correct headers —
2.3s - ✅ E2E: Loans Portfolio › should show empty state when no loans exist —
2.0s - ✅ E2E: Loans Portfolio › should have search input —
2.5s - ✅ E2E: Loans Portfolio › should have pagination controls —
2.3s - ✅ E2E: Header & Global Elements › should display Fineract logo and title in header —
2.0s - ✅ E2E: Header & Global Elements › should display logged-in username —
1.9s - ✅ E2E: Header & Global Elements › should display office name for user —
2.1s - ✅ E2E: Header & Global Elements › should have Logout button —
2.1s - ✅ E2E: Header & Global Elements › should have language selector in header —
2.1s - ✅ E2E: Header & Global Elements › should display render time —
2.0s - ✅ E2E: Header & Global Elements › should display business date —
2.0s
feature-coverage.spec.ts
- ✅ Navigation & Sidebar › all main navigation links are visible in sidebar —
2.6s - ✅ Navigation & Sidebar › sidebar navigation routes to correct pages —
3.5s - ✅ Navigation & Sidebar › navigating to /accounting redirects to /accounting/chart-of-accounts —
3.4s - ✅ 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.5s - ✅ Navigation & Sidebar › header shows logged-in user info —
1.7s - ✅ Navigation & Sidebar › help tour button is visible and interactive —
1.7s - ✅ Navigation & Sidebar › logout button is visible —
1.7s - ✅ Navigation & Sidebar › language selector is present —
1.9s - ✅ Dashboard › dashboard shows key metrics cards —
1.7s - ✅ Dashboard › dashboard shows pending approvals section —
2.1s - ✅ Dashboard › dashboard shows loan and savings status distribution —
1.7s - ✅ Dashboard › dashboard shows system operational status —
2.1s - ✅ Groups › groups page renders with title —
2.3s - ✅ Groups › groups page has create button —
1.9s - ✅ Centers › centers page renders with title —
2.3s - ✅ Centers › centers page has create button —
1.9s - ✅ Organization › offices page loads with list —
2.4s - ✅ Organization › staff page loads —
2.3s - ✅ Organization › funds page loads —
1.9s - ✅ Organization › payment types page loads —
2.4s - ✅ Accounting › chart of accounts loads —
2.2s - ✅ Accounting › journal entries page loads —
2.4s - ✅ Accounting › accounting closures loads —
2.0s - ✅ Accounting › accounting rules loads —
2.3s - ✅ Accounting › financial activity mappings loads —
2.5s - ✅ Accounting › charges page loads —
1.9s - ✅ Security › users page loads —
2.4s - ✅ Security › roles page loads —
2.3s - ✅ Security › audit logs page loads —
2.2s - ✅ Security › leftover audit trails path lands on audits, not the dashboard —
3.6s - ✅ Products - Loan & Savings › loan products page loads —
2.3s - ✅ Products - Loan & Savings › savings products page loads —
1.9s - ✅ Products - Loan & Savings › tax components page loads —
2.0s - ✅ Products - Loan & Savings › tax groups page loads —
2.0s - ✅ Products - Loan & Savings › floating rates page loads —
2.0s - ✅ Products - Loan & Savings › savings accounts page loads —
2.4s - ✅ Settings › global configurations page loads —
2.2s - ✅ Settings › holidays page loads —
2.0s - ✅ Settings › working days page loads —
2.0s - ✅ System › data tables page loads —
1.9s - ✅ System › bulk import page loads —
2.3s - ✅ System › delinquency page loads —
2.0s - ✅ Tellers › tellers page loads with create button —
2.4s - ✅ Transfers › account transfer page loads —
2.6s - ✅ Transfers › standing instructions page loads —
2.2s - ✅ Transfers › SI history page loads —
2.4s - ✅ Embedded Fintech › asset owners page loads —
2.3s
functional-coverage.spec.ts
- ✅ Client CRUD Workflow › should complete full client creation flow — Person —
4.2s - ✅ Client CRUD Workflow › should complete full client creation flow — Entity —
3.5s - ✅ Client CRUD Workflow › should cancel client creation and return to list —
2.6s - ✅ Client CRUD Workflow › should disable office and legal form in edit mode —
3.5s - ✅ Client View & Status Transitions › should display client view with correct details —
3.6s - ✅ Client View & Status Transitions › should show actions menu for pending client (status 100) —
3.5s - ✅ Client View & Status Transitions › should show actions menu for active client (status 300) —
3.7s - ✅ Client View & Status Transitions › should show actions menu for closed client (status 600) —
3.6s - ✅ Client View & Status Transitions › should show New Account menu for active client —
3.5s - ✅ Client View & Status Transitions › should navigate from client view to client list via breadcrumb —
3.7s - ✅ Client View & Status Transitions › should navigate back from client view —
3.3s - ✅ Client View Tabs › should display all expected tabs on client view —
3.5s - ✅ Client View Tabs › should switch between client view tabs —
3.5s - ✅ Search & Filter Interactions › should have search input on clients page and accept input —
2.6s - ✅ Search & Filter Interactions › should have office filter on groups page —
2.5s - ✅ Search & Filter Interactions › should have office filter on loans page —
2.0s - ✅ Search & Filter Interactions › should have search input on charges page —
1.9s - ✅ 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.4s - ✅ Navigation Flow Verification › should go from loan products → create → back —
2.4s - ✅ Office CRUD › should validate office create form — save disabled when empty —
2.5s - ✅ Office CRUD › should validate office create form — save enabled when filled —
3.0s - ✅ Office CRUD › should cancel office creation —
2.7s - ✅ Organization Create Flows › staff create form loads —
2.8s - ✅ Organization Create Flows › funds create form loads —
2.5s - ✅ Organization Create Flows › payment types create form loads —
2.7s - ✅ Accounting CRUD › accounting closure create form loads —
2.6s - ✅ Accounting CRUD › accounting rule create form loads —
2.5s - ✅ Accounting CRUD › financial activity mapping create form loads —
2.1s - ✅ Accounting CRUD › charge create form loads —
2.1s - ✅ Accounting CRUD › chart of accounts create form loads —
2.4s - ✅ Settings CRUD › global configurations page has editable toggle —
2.0s - ✅ Settings CRUD › holiday create form loads —
2.7s - ✅ Settings CRUD › working days page has save button —
2.0s - ✅ System CRUD › data table create form loads —
2.4s - ✅ System CRUD › delinquency page has create buttons for ranges and buckets —
2.5s - ✅ Security CRUD › role create form loads —
2.5s - ✅ Security CRUD › audit logs search form has date range —
2.8s - ✅ 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.3s - ✅ Teller CRUD › teller create form loads —
2.6s - ✅ Create Office Dialog from Client Form › should open create office dialog from client create form —
2.6s
global-search-nav-shortcuts.spec.ts
- ✅ Global search navigation shortcuts › offers a settings page the entity search cannot return —
2.4s - ✅ Global search navigation shortcuts › navigates to the page behind a shortcut —
2.4s - ✅ 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.4s - ✅ Global search navigation shortcuts › withholds a shortcut the user has no permission to reach —
2.5s
global-search-navigation.spec.ts
- ✅ Global search navigation › does not query the backend for a single character —
2.8s - ✅ 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.3s - ✅ Global search navigation › opens the loan behind a loan result —
2.7s - ✅ Global search navigation › opens the savings account behind a savings result —
2.5s - ✅ Global search navigation › clears the query and closes the dropdown after a selection —
2.1s - ✅ Global search navigation › closes the dropdown when focus leaves without a selection —
2.2s - ✅ Global search navigation › shows nothing rather than an empty dropdown when there are no matches —
3.0s
group-detail.spec.ts
- ✅ Group detail › custom field tabs expose the app keyboard and panel contract at 1280px —
4.3s - ✅ Group detail › custom field tabs expose the app keyboard and panel contract at 390px —
4.4s - ✅ Group detail › asks for the associations, and shows every member rather than only the active ones —
3.7s - ✅ Group detail › closes a group with the reason id and a Fineract-formatted date —
5.2s - ✅ Group detail › does not offer a client who is already a member, and associates the one it does —
4.4s - ✅ Group detail › unassigns a committee role by the assignment id, not the role id —
4.6s - ✅ Group detail › offers a retry when the group cannot be loaded —
3.5s - ✅ Group detail › says so when no closure reason has been defined —
4.5s
guidance-tour.spec.ts
- ✅ the guided tour › highlights the System Status card, not the sidebar, on the dashboard tour —
2.6s - ✅ the guided tour › presents the card as a dialog named and described by its own copy —
2.1s - ✅ the guided tour › announces the step counter as a polite live region —
2.2s - ✅ the guided tour › closes on Escape and hands focus back to the Guide button —
1.7s - ✅ the guided tour › names an unmatched route after itself instead of handing it the dashboard tour —
3.4s - ⏭️ the guided tour at a phone viewport › opens from the overflow menu as a full-width bottom sheet —
1.6s
keyboard-shortcuts.spec.ts
- ✅ Alt+C jumps straight to Create Client from anywhere —
2.4s - ✅ Alt+G jumps to Create Group —
2.3s - ✅ Alt+E jumps to Create Center —
1.9s - ✅ 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.7s - ✅ 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.5s - ✅ report mailing jobs › reads rows out of the paged envelope the endpoint returns —
3.9s - ✅ report mailing jobs › shows a failure state when the request errors —
3.5s
list-pagination.spec.ts
- ✅ List pagination › advances through pages and back again —
4.1s - ✅ List pagination › jumps to the last page —
3.9s - ✅ List pagination › returns to the first page when a filter changes —
4.0s - ✅ 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.7s - ✅ List pagination › keeps an account-number search broad and disables unsupported Office sorting —
4.5s - ✅ List pagination › returns to the first page when searching —
4.8s - ✅ Profile › renders the signed-in user rather than hanging on a spinner —
3.9s - ✅ Profile › changes the signed-in user password from the profile screen —
4.0s - ✅ Profile › shows an error when the profile cannot be loaded —
3.9s - ✅ List load failure › reports the failure and reloads when the user retries —
4.0s - ✅ List load failure › calendars: reports the failure and reloads when the user retries —
4.1s - ✅ List load failure › accounting rules: reports the failure and reloads when the user retries —
3.8s
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 —
4.3s - ✅ Delinquency pause and resume on a regular loan › pauses delinquency for a period, from the business date —
4.5s - ✅ Delinquency pause and resume on a regular loan › will not take a pause that ends before, or when, it starts —
3.6s - ✅ Delinquency pause and resume on a regular loan › sends nothing when the pause dialog is cancelled —
4.7s - ✅ Delinquency pause and resume on a regular loan › shows the platform’s own reason when it refuses a pause, and stays usable —
4.0s - ✅ Delinquency pause and resume on a regular loan › resumes a pause that is in effect, dated the business date and with no end date —
3.9s - ✅ Delinquency pause and resume on a regular loan › stops offering resume once the pause has been ended —
4.6s - ✅ Delinquency pause and resume on a regular loan › does not offer resume when no pause is in effect —
3.4s - ✅ Delinquency pause and resume on a regular loan › offers neither action without the permission to create a delinquency action —
3.3s - ✅ Delinquency pause and resume on a regular loan › offers the permitted user the actions that permission opens, and no others —
3.7s - ✅ Delinquency pause and resume on a regular loan › offers neither action on a loan that is not active —
3.8s
loan-portfolio-summary.spec.ts
- ✅ Loan Portfolio Summary › searching sends entities: loans and shows the grouped results —
3.2s - ✅ Loan Portfolio Summary › Edit Parameters returns from the results view to the filter form —
3.7s - ✅ Loan Portfolio Summary › checking the outstanding-amount filter sends the between min/max values —
3.6s - ✅ Loan Portfolio Summary › switching to a single-value comparison condition sends one value —
3.8s
loan-product-down-payment.spec.ts
- ✅ Loan product down payment and tranches › down payment is offered only for a progressive product —
4.7s - ✅ Loan product down payment and tranches › the percentage and auto-repayment appear only once down payment is on —
4.5s - ✅ Loan product down payment and tranches › multi-tranche disbursement reveals its tranche count, on either engine —
3.8s - ✅ 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.6s - ✅ Loan product down payment and tranches › income recognition is offered only for a progressive product —
4.2s - ✅ Loan product down payment and tranches › the capitalisation details appear only once it is on —
4.8s - ✅ Loan product down payment and tranches › submits the income recognition settings it was given —
4.6s - ✅ Loan product down payment and tranches › does not send income recognition on a cumulative product —
5.4s - ✅ 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.7s - ✅ Loan product down payment and tranches › submits the interest recalculation settings it was given —
3.6s - ✅ Loan product down payment and tranches › does not send recalculation settings once it is switched back off —
3.9s
charge-refund.spec.ts
- ✅ refunds the remaining balance of a collected loan charge —
4.9s
client-accounts.spec.ts
- ✅ loan account rows show the principal returned by the accounts endpoint —
2.3s - ✅ empty account tabs offer the matching creation action —
4.2s
client-load-error.spec.ts
- ✅ shows a not-found state and returns to the list, without an error toast —
2.4s - ✅ offers a retry for a transient failure, and recovers on success —
2.5s
contract-termination.spec.ts
- ✅ terminates and undoes a progressive loan contract —
6.2s
loan-schedule-type-gating.spec.ts
- ✅ Loan schedule type gating › a cumulative loan offers neither progressive-only tab, and fetches neither —
2.4s - ✅ Loan schedule type gating › a progressive loan shows only the capabilities it actually has —
2.3s - ✅ Loan schedule type gating › fetches buy-down fees for a progressive loan that has no external id —
2.5s - ✅ Loan schedule type gating › a progressive loan with both capabilities shows both —
2.2s - ✅ Loan schedule type gating › a charged-off loan says so and offers the reversal instead —
2.4s - ✅ Loan schedule type gating › a healthy loan offers charge-off and no marker —
2.5s
loan-servicing-gaps.spec.ts
- ✅ Loan servicing gaps › edits an interest pause through PUT while preserving its existing dates —
2.6s - ✅ Loan servicing gaps › undo approval sends an empty body, without the locale the platform refuses —
3.1s - ✅ Loan servicing gaps › undo approval carries the reason when one was given —
3.3s - ✅ Loan servicing gaps › undo approval is offered only while the loan is approved —
2.3s - ✅ Loan servicing gaps › the delinquency tab shows the summary the loan carries and the tags it fetches —
2.4s - ✅ Loan servicing gaps › the data-only tabs stay hidden when the loan carries nothing for them —
2.3s - ✅ Loan servicing gaps › each data-only tab appears and renders once the loan carries its data —
2.5s - ✅ Loan servicing gaps › disburse to savings sends the date and amount, with the platform date format —
3.0s - ✅ Loan servicing gaps › disburse to savings is offered only on an approved loan —
2.4s - ✅ Loan servicing gaps › unassign loan officer sends the date, and appears only when one is assigned —
3.1s - ✅ Loan servicing gaps › unassign loan officer is hidden on a loan with no officer —
2.4s - ✅ Loan servicing gaps › undo last disbursal appears only on a multi-disbursal loan, and sends an empty body —
3.5s - ✅ Loan servicing gaps › undo last disbursal is hidden on a single-disbursal loan —
2.3s - ✅ Loan servicing gaps › close as rescheduled is offered on an active loan —
2.3s - ✅ Loan servicing gaps › revising the amounts is offered on an approved loan —
2.5s - ✅ Loan servicing gaps › revising the amounts is hidden before approval —
2.4s - ✅ Loan servicing gaps › revising the approved amount sends the new amount and locale —
3.3s - ✅ Loan servicing gaps › revising the available disbursement amount sends the new amount, including zero —
3.3s
logout-reason-notice.spec.ts
- ✅ explains an inactivity sign-out —
1.2s - ✅ explains an expired session, with different wording —
1.1s - ✅ stays silent when the user came to sign in of their own accord —
165ms - ✅ stays silent for a reason it does not recognise, rather than showing a blank notice —
190ms
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.1s - ✅ identity-provider route on the login page › does not offer the route when the flag is false —
1.5s - ✅ identity-provider route on the login page › does not offer the route when the flag is "true" —
1.4s - ✅ identity-provider route on the login page › does not offer the route when the flag is 1 —
1.1s - ✅ identity-provider route on the login page › offers the route above the password form, which stays in place —
1.1s - ✅ identity-provider route on the login page › says plainly that it is not available yet, and goes nowhere —
1.1s - ✅ identity-provider route on the login page › username and password still sign in when the route is offered —
1.4s - ✅ identity-provider route on the login page › is not offered while a second factor is being asked for —
1.5s
rbac-feature-flag.spec.ts
- ✅ RBAC permission gating (rbacEnabled = true) › a limited user does not see permission-gated nav groups —
1.2s - ✅ RBAC permission gating (rbacEnabled = true) › a user with READ_USER sees only the Security entries that permission covers —
1.2s - ✅ RBAC permission gating (rbacEnabled = true) › the Security group fills in as the user is granted each of its permissions —
1.2s - ✅ RBAC permission gating (rbacEnabled = true) › a superuser (ALL_FUNCTIONS) sees all permission-gated groups —
1.4s - ✅ RBAC institution-feature gating (rbacEnabled = true) › universal institution shows Groups, Centers and Collection Sheet —
1.5s - ✅ RBAC institution-feature gating (rbacEnabled = true) › commercial bank (cb) hides all group-lending features —
1.3s - ✅ RBAC institution-feature gating (rbacEnabled = true) › credit union (cu) shows Groups but hides Centers and Collection Sheet —
1.3s - ✅ rbacEnabled = false › restores the pre-RBAC behaviour of showing everything —
1.3s - ✅ deployment navigation overrides › removes the entries the deployment names by id, leaving the rest alone —
1.3s - ✅ deployment navigation overrides › ignores a labelKey where an id is required —
1.5s - ✅ deployment navigation overrides › removes them even where RBAC is off —
1.3s
rbac-route-protection.spec.ts
- ✅ route authorization › a superuser reaches every sampled route and sees the full navigation —
10.4s - ✅ route authorization › a single-module user is confined to that module —
7.6s - ✅ route authorization › a read-only user gets the lists and not the forms —
9.2s - ✅ route authorization › a user with an empty permission list is refused everywhere and the app still works —
7.5s - ✅ route authorization › a session carrying no permissions field is treated as carrying none —
4.2s - ✅ route authorization › an unrecognised permission code grants nothing —
4.5s - ✅ route authorization › an unauthenticated visitor is asked to sign in, not told they are forbidden —
4.8s - ✅ route authorization › a deployment with RBAC turned off behaves as it did before the guard —
6.2s - ✅ the Access Denied page › says what happened, under a single heading —
2.7s - ✅ the Access Denied page › moves focus to the heading, since the user did not ask to come here —
2.8s - ✅ the Access Denied page › announces itself politely —
2.8s - ✅ the Access Denied page › names the permissions the screen wanted, so the user can ask for them —
2.7s - ✅ the Access Denied page › offers a way back that the user is allowed to take —
2.8s - ✅ the Access Denied page › is reachable by keyboard alone —
2.9s - ✅ permission feedback › a visible nav entry says what the user can do in that module —
1.2s - ✅ permission feedback › a nav entry carries no hint when there is nothing specific to say —
1.3s - ✅ navigation and routes agree › a hidden menu entry is also refused by URL, and a shown one is not —
4.5s - ✅ navigation and routes agree › the create button is withheld from a user whose create route would refuse them —
2.8s
report-enhancements.spec.ts
- ✅ Report Enhancements, Pagination, and Help Tour › should run report, show paginated data, and download CSV —
3.4s - ✅ Report Enhancements, Pagination, and Help Tour › should trigger guidance help tour and navigate steps —
2.7s
reporting.spec.ts
- ✅ Reporting › should display list of reports —
1.5s - ✅ 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 —
2.4s - ✅ Scheduler Jobs bulk run › Select All checks every job, and running confirms then triggers each one —
2.9s - ✅ Scheduler Jobs bulk run › declining the confirmation runs nothing —
3.1s
sidebar-active-state.spec.ts
- ✅ Sidebar active route matching › does not mark a parent sidebar link active on nested routes —
58.8s
two-factor-authentication.spec.ts
- ✅ two-step verification › asks for a code and lets the user in once it is accepted —
1.3s - ✅ two-step verification › sends the token on every later request —
1.4s - ✅ two-step verification › keeps the user on the step when the code is wrong, and says why —
1.2s - ✅ two-step verification › accepts a correct code after a wrong one —
1.6s - ✅ two-step verification › offers the choice when there is more than one channel —
1.1s - ✅ two-step verification › says so when the account has no channel configured —
1.1s - ✅ two-step verification › returns to the choice when the code could not be sent —
1.2s - ✅ two-step verification › does not let a half-finished session reach the application —
2.7s - ✅ 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.3s
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 —
3.5s - ✅ Working Capital loan delinquency, breach and near-breach actions, and originators › shows breach action history and submits a new one —
4.1s - ✅ Working Capital loan delinquency, breach and near-breach actions, and originators › shows near-breach action history and submits a new one —
3.5s - ✅ Working Capital loan delinquency, breach and near-breach actions, and originators › attaches and detaches a loan originator —
3.0s - ✅ Working Capital loan delinquency, breach and near-breach actions, and originators › adds a new charge and waives an existing one —
3.6s - ✅ Working Capital loan delinquency, breach and near-breach actions, and originators › shows rate-change history, amortization schedule, and delinquency range tags —
2.7s - ✅ Working Capital loan delinquency, breach and near-breach actions, and originators › marks the loan as fraud, applies a discount, and changes the payment rate —
4.3s - ✅ Working Capital loan transactions, loss actions and modification › credits the borrower through a goodwill credit —
2.9s - ✅ Working Capital loan transactions, loss actions and modification › refunds a merchant payout —
3.0s - ✅ Working Capital loan transactions, loss actions and modification › refunds a credit balance only on an overpaid loan —
3.0s - ✅ Working Capital loan transactions, loss actions and modification › charges off an active loan —
2.9s - ✅ Working Capital loan transactions, loss actions and modification › swaps charge-off for its undo once the loan is charged off —
2.6s - ✅ Working Capital loan transactions, loss actions and modification › writes off an active loan —
2.9s - ✅ Working Capital loan transactions, loss actions and modification › offers recovery and undo on a written-off loan, but not a second write-off —
2.5s - ✅ Working Capital loan transactions, loss actions and modification › withholds undo write-off once a recovery has been collected —
2.6s - ✅ Working Capital loan transactions, loss actions and modification › modifies a submitted application through the edit route —
3.6s - ✅ Working Capital loan transactions, loss actions and modification › disables the actions a read-only role may not perform —
2.3s
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 |
58.8s |
| Runtime accessibility › banner and dashboard content have no blocking violations | accessibility.spec.ts |
15.0s |
| route authorization › a superuser reaches every sampled route and sees the full navigation | rbac-route-protection.spec.ts |
10.4s |
| route authorization › a read-only user gets the lists and not the forms | rbac-route-protection.spec.ts |
9.2s |
| route authorization › a single-module user is confined to that module | rbac-route-protection.spec.ts |
7.6s |
| route authorization › a user with an empty permission list is refused everywhere and the app still works | rbac-route-protection.spec.ts |
7.5s |
| Date pickers on revisited forms › floating rate form keeps its pickers usable on every visit | date-picker-revisit.spec.ts |
6.8s |
| Client form date pickers › stay usable on a second visit to the create form | client-date-picker-revisit.spec.ts |
6.7s |
| route authorization › a deployment with RBAC turned off behaves as it did before the guard | rbac-route-protection.spec.ts |
6.2s |
| terminates and undoes a progressive loan contract | contract-termination.spec.ts |
6.2s |
📼 Download the HTML report, videos and traces — see the playwright-report-mocked artifact.
Generated by run 39037788668 from 635e249. The run executed a fork branch, so treat its contents as unverified.
Contributor
E2E — real Fineract🎭 E2E Tests✅ All green — 154 passed · 0 failed · 0 skipped · 2 flaky, across 45 spec files in 9m 18s.
|
| Spec | ✅ | ❌ | ⏭️ | 🔒 | Time |
|---|---|---|---|---|---|
| backend.setup.ts | 3 | 0 | 0 | 0 | 5.0s |
| accounting-closure-backend.spec.ts | 2 | 0 | 0 | 0 | 16.5s |
| batch-api-operations.spec.ts | 5 | 0 | 0 | 0 | 31.4s |
| center-servicing.spec.ts | 2 | 0 | 0 | 0 | 17.7s |
| client-legal-form-search.spec.ts | 1 | 0 | 0 | 0 | 4.4s |
| client-transfer.spec.ts | 4 | 0 | 0 | 0 | 46.8s |
| collection-sheet.spec.ts | 1 | 0 | 0 | 0 | 6.6s |
| deposit-account-servicing.spec.ts | 3 | 0 | 0 | 0 | 26.3s |
| deposit-product-configuration.spec.ts | 3 | 0 | 0 | 0 | 15.2s |
| form-layout-reflow.spec.ts | 6 | 0 | 0 | 0 | 32.7s |
| group-membership.spec.ts | 3 | 0 | 0 | 0 | 48.2s |
| loan-account-actions.spec.ts | 3 | 0 | 0 | 0 | 23.5s |
| loan-approved-amount-revision.spec.ts | 3 | 0 | 0 | 0 | 18.6s |
| loan-charge-off.spec.ts | 2 | 0 | 0 | 0 | 19.7s |
| loan-flows-non-admin-roles.spec.ts | 8 | 0 | 0 | 0 | 1m 38s |
| loan-product-accounting.spec.ts | 1 | 0 | 0 | 0 | 31.4s |
| loan-repayment-gating.spec.ts | 2 | 0 | 0 | 0 | 8.6s |
| loan-servicing.spec.ts | 2 | 0 | 0 | 0 | 18.8s |
| login.spec.ts | 4 | 0 | 0 | 0 | 4.5s |
| oidc-login-backend.spec.ts | 2 | 0 | 0 | 0 | 3.8s |
| parity-screens.spec.ts | 8 | 0 | 0 | 0 | 32.3s |
| rbac-backend-restricted-user.spec.ts | 7 | 0 | 0 | 0 | 27.9s |
| rbac-dead-end-controls.spec.ts | 7 | 0 | 0 | 0 | 24.5s |
| rbac-disabled-flag-backend.spec.ts | 6 | 0 | 0 | 0 | 19.4s |
| rbac-multi-permission.spec.ts | 9 | 0 | 0 | 0 | 44.5s |
| rbac-office-scoped-user.spec.ts | 6 | 0 | 0 | 0 | 20.9s |
| rbac-permissionless-user.spec.ts | 4 | 0 | 0 | 0 | 16.4s |
| bulk-import-entity-types.spec.ts | 1 | 0 | 0 | 0 | 7.1s |
| delinquency-configuration.spec.ts | 2 | 0 | 0 | 0 | 12.6s |
| full-demo.spec.ts | 1 | 0 | 0 | 0 | 45.4s |
| interest-rate-charts.spec.ts | 1 | 0 | 0 | 0 | 5.5s |
| loan-lifecycle.spec.ts | 4 | 0 | 0 | 0 | 1m 32s |
| loan-schedule-type.spec.ts | 3 | 0 | 0 | 0 | 22.6s |
| report-mailing-job.spec.ts | 3 | 0 | 0 | 0 | 14.4s |
| report-parameter-backend.spec.ts | 4 | 0 | 0 | 0 | 18.0s |
| savings-flows-non-admin-roles.spec.ts | 7 | 0 | 0 | 0 | 1m 11s |
| savings-transaction-correction.spec.ts | 1 | 0 | 0 | 0 | 4.8s |
| savings-transaction-gating.spec.ts | 2 | 0 | 0 | 0 | 4.4s |
| share-account-servicing.spec.ts | 2 | 0 | 0 | 0 | 15.4s |
| share-product-accounting.spec.ts | 1 | 0 | 0 | 0 | 18.9s |
| teller-cash-management.spec.ts | 2 | 0 | 0 | 0 | 27.8s |
| working-capital-loan-actions-backend.spec.ts | 3 | 0 | 0 | 0 | 14.4s |
| working-capital-product-accounting-backend.spec.ts | 2 | 0 | 0 | 0 | 16.5s |
| working-capital-rbac-backend.spec.ts | 2 | 0 | 0 | 0 | 5.1s |
| working-capital-servicing-backend.spec.ts | 6 | 0 | 0 | 0 | 25.2s |
All 154 tests — click to expand
backend.setup.ts
- ✅ seed backend reference data —
2.4s - ✅ seed backend reference data —
1.3s - ✅ seed backend reference data —
1.3s
accounting-closure-backend.spec.ts
- ✅ Accounting closures against Fineract › a closed period reads as Closed, and the platform refuses a posting inside it —
11.0s(retried 1×) - ✅ Accounting closures against Fineract › the form keeps the user on the page and names the reason when Fineract refuses —
5.5s
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 —
5.7s - ✅ Batch API Operations against Fineract › shows a parse error instead of submitting when the batch input is not valid JSON —
6.8s - ✅ Batch API enclosingTransaction semantics against Fineract › rolls back the earlier steps when enclosingTransaction is true and a later step fails —
8.9s(retried 1×) - ✅ Batch API enclosingTransaction semantics against Fineract › does not roll back the earlier steps when enclosingTransaction is false and a later step fails —
5.0s - ✅ Batch API Operations on a mobile viewport against Fineract › the sample batch scenario is reachable and works by touch at mobile width —
4.9s
center-servicing.spec.ts
- ✅ Center servicing › a center is activated, staffed and given a group —
12.2s - ✅ Center servicing › notes are recorded against the center —
5.5s
client-legal-form-search.spec.ts
- ✅ Client list: legal form filtering › an entity client appears in the main client list —
4.4s
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 —
10.1s - ✅ Client staff assignment › an officer can be assigned and then removed —
11.5s
collection-sheet.spec.ts
- ✅ Collection Sheet › scopes staff to the office, sends the choice, and reports an empty sheet —
6.6s
deposit-account-servicing.spec.ts
- ✅ Term deposit account servicing › an account is approved, activated and closed before maturity —
11.4s - ✅ Term deposit account servicing › a deposit is recorded, listed, and reversed without leaving the list —
8.8s - ✅ Term deposit account servicing › an application can be rejected instead of approved —
6.0s
deposit-product-configuration.spec.ts
- ✅ Deposit product configuration › a fixed deposit product survives being edited —
4.9s - ✅ Deposit product configuration › a recurring deposit product can be created at all —
4.6s - ✅ Deposit product configuration › a savings product carries its accounting configuration —
5.7s
form-layout-reflow.spec.ts
- ✅ form layout at the narrow viewport › Create GL Account gives every field a usable width at 320px —
4.8s - ✅ form layout at the narrow viewport › Create Loan gives every field a usable width at 320px —
4.7s - ✅ form layout at the narrow viewport › Create Office gives every field a usable width at 320px —
4.8s - ✅ form layout at the narrow viewport › Create Staff gives every field a usable width at 320px —
4.5s - ✅ form layout at the narrow viewport › no page-level horizontal scroll at 320px —
9.2s - ✅ form layout at the wide viewport › Create GL Account still uses more than one column at 1280px —
4.6s
group-membership.spec.ts
- ✅ Group membership and lifecycle › a group is activated, staffed, given members and a committee, then emptied —
20.4s - ✅ Group membership and lifecycle › notes are recorded against the group and can be removed again —
8.4s - ✅ Group membership and lifecycle › an empty group is closed with a reason, and a group with members is refused —
19.4s
loan-account-actions.spec.ts
- ✅ Loan account lifecycle actions › new action menu items appear only for active loans —
6.7s - ✅ Loan account lifecycle actions › undo disbursal shows a confirm dialog and reverts the loan to Approved —
9.0s - ✅ Loan account lifecycle actions › write off requires confirmation and moves the loan out of Active status —
7.8s
loan-approved-amount-revision.spec.ts
- ✅ Loan approved and available-disbursement amount revision › revises the approved amount on an active, partially-disbursed loan —
6.2s - ✅ Loan approved and available-disbursement amount revision › revises the available disbursement amount, which also changes the approved amount —
6.2s - ✅ Loan approved and available-disbursement amount revision › shows the platform’s own refusal, not a generic validation message —
6.2s
loan-charge-off.spec.ts
- ✅ Loan servicing commands › charges a loan off through the UI and reverses it —
10.6s - ✅ Loan servicing commands › records a goodwill credit through the shared transaction form —
9.1s
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 —
35.6s - ✅ 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 —
14.9s - ✅ 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 —
5.9s - ✅ 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 —
4.9s - ✅ 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 —
7.6s - ✅ 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 —
7.5s - ✅ 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 —
5.2s - ✅ a loan taken through four separated duties, every account built in the UI › a repayment duty reaches its own form, and records a repayment —
15.9s
loan-product-accounting.spec.ts
- ✅ Loan product accounting › a cash-accounting product is configured, round-trips on edit, and posts to the ledger —
31.4s
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 —
8.3s - ✅ Repayment is offered only where the platform allows it › the platform refuses a repayment on a loan awaiting approval —
242ms
loan-servicing.spec.ts
- ✅ Loan servicing: notes and transaction adjustment › notes can be added and removed, with a confirm dialog on delete —
8.2s - ✅ Loan servicing: notes and transaction adjustment › a repayment transaction can be viewed and adjusted with a corrected amount —
10.5s
login.spec.ts
- ✅ Login › login page displays correctly —
1.1s - ✅ Login › login form has required fields —
1.1s - ✅ Login › submit button is disabled when form is empty —
1.1s - ✅ Login › submit button is enabled when form is filled —
1.2s
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.3s - ✅ identity-provider route against a real Fineract › a real password sign-in still gets a session with the route offered —
2.5s
parity-screens.spec.ts
- ✅ Screens added for platform parity › a manual journal entry can be read whole and reversed —
4.2s - ✅ Screens added for platform parity › an entry that is already reversed is not offered again —
3.5s - ✅ Screens added for platform parity › a report definition can be created, edited and deleted; a core one cannot —
4.4s - ✅ Screens added for platform parity › a core report opens read-only with only its in-use setting —
3.5s - ✅ Screens added for platform parity › a pending loan is approved from the queue, in a batch —
4.5s - ✅ Screens added for platform parity › a fixed deposit is listed as a deposit, not as a savings account —
3.6s - ✅ Screens added for platform parity › an office has a screen, and it carries its custom fields —
3.3s - ✅ Screens added for platform parity › a savings account carries notes, and the note survives a reload —
5.2s
rbac-backend-restricted-user.spec.ts
- ✅ a genuinely restricted Fineract user › holds exactly the permissions their role was granted —
172ms - ✅ a genuinely restricted Fineract user › reaches the screen their permission covers —
3.7s - ✅ a genuinely restricted Fineract user › is refused a screen their permission does not cover, by URL and by the backend —
3.9s - ✅ a genuinely restricted Fineract user › is refused a write screen they can read the list for, and the write itself —
5.4s - ✅ a genuinely restricted Fineract user › is not offered the actions it would be refused for —
3.4s - ✅ a genuinely restricted Fineract user › is shown an action it cannot take, disabled and saying what it needs —
4.6s - ✅ a genuinely restricted Fineract user › the superuser the rest of the suite uses is unaffected —
6.8s
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 —
3.5s - ✅ a client's account tables › keep the link for a user who holds READ_LOAN —
3.7s - ✅ the office transactions list › withholds Create from a reader, and the route refuses it too —
4.1s - ✅ the office transactions list › offers Create to an administrator —
3.3s - ✅ the office transactions list › refuses the list at the door for the code the platform does not check —
3.1s - ✅ a group's member list › names the member without linking when the reader cannot open clients —
3.4s - ✅ a group's member list › keeps the link for a reader who holds READ_CLIENT —
3.4s
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 —
2.1s - ✅ rbacEnabled: false, with a user who holds only READ_CLIENT › is admitted by the route guard to a screen their role does not cover —
5.3s - ✅ rbacEnabled: false, with a user who holds only READ_CLIENT › is still refused by Fineract, which the flag does not reach —
410ms - ✅ 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 —
4.2s - ✅ rbacEnabled: false, with a user who holds only READ_CLIENT › gets the same treatment on a second refused list, not a one-screen fix —
3.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 —
3.7s
rbac-multi-permission.spec.ts
- ✅ a route declaring more than one permission code (OR semantics) › is admitted by either declared code alone —
3.6s - ✅ a route declaring more than one permission code (OR semantics) › is admitted by the other declared code alone —
3.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 —
3.7s - ✅ ALL_FUNCTIONS_READ, against the real Fineract permission catalogue › reaches read screens across modules it holds no specific code for —
7.0s - ✅ ALL_FUNCTIONS_READ, against the real Fineract permission catalogue › is refused every write screen, and the writes themselves —
5.3s - ✅ a restricted session across a real page reload › keeps the same permission boundary after reloading, not just after a fresh login —
7.9s - ✅ 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 —
4.7s - ✅ Security module writes (users, roles), against the real backend › reaches the list screens but is refused the write screens —
8.5s - ✅ Security module writes (users, roles), against the real backend › is refused creating a user and modifying a role, by the backend itself —
199ms
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 —
291ms - ✅ an account scoped to a branch office › is shown only its own office in the client list, and told which office it is in —
3.8s - ✅ an account scoped to a branch office › sees a shorter list than an identically-permissioned head-office account —
3.7s - ✅ an account scoped to a branch office › is refused another office’s client by the platform, and told so once —
4.1s - ✅ an account scoped to a branch office › can still open the record that is in its own office —
3.6s - ✅ an account scoped to a branch office › is not offered an edit it would be refused for on the Offices screen —
5.4s
rbac-permissionless-user.spec.ts
- ✅ an account whose role grants nothing › is authenticated by Fineract and authorized by it for nothing —
504ms - ✅ an account whose role grants nothing › is signed in and landed on a screen rather than stranded at the login form —
3.7s - ✅ an account whose role grants nothing › is offered no permission-gated module, and refused each one by URL and by Fineract —
8.5s - ✅ an account whose role grants nothing › is left a navigation whose entries actually work —
3.7s
bulk-import-entity-types.spec.ts
- ✅ every offered entity type is one the platform accepts —
7.1s
delinquency-configuration.spec.ts
- ✅ creates a delinquency range, then edits it —
6.4s - ✅ creates a delinquency bucket from the ranges the template offers —
6.2s
full-demo.spec.ts
- ✅ Full feature demo recording › walk through loan schedule type, lifecycle, custom fields, collateral, and disbursement —
45.4s
interest-rate-charts.spec.ts
- ✅ lists charts without a server error —
5.5s
loan-lifecycle.spec.ts
- ✅ Loan lifecycle: creation, approval, disbursement › create, approve, and disburse a Cumulative loan —
23.0s - ✅ Loan lifecycle: creation, approval, disbursement › create, approve, and disburse a Progressive loan —
24.3s - ✅ Loan lifecycle: creation, approval, disbursement › an approved loan can be returned to pending approval —
22.7s - ✅ Loan lifecycle: creation, approval, disbursement › the delinquency tab reads a real loan, and the empty data tabs stay hidden —
21.7s
loan-schedule-type.spec.ts
- ✅ Loan Schedule Type (Cumulative vs Progressive) › loan products list shows a schedule type chip per product —
5.7s - ✅ Loan Schedule Type (Cumulative vs Progressive) › create a Progressive loan product end-to-end and verify it round-trips —
9.9s - ✅ Loan Schedule Type (Cumulative vs Progressive) › loan creation shows the schedule type badge for a Progressive product —
7.1s
report-mailing-job.spec.ts
- ✅ report mailing job creation › is no longer refused for a missing parameter —
4.5s - ✅ report mailing job creation › the payload carries the locale and the schedule —
4.1s - ✅ report mailing job creation at the narrow viewport › every field is reachable and the job still saves at 320px —
5.8s
report-parameter-backend.spec.ts
- ✅ Dynamic report parameters against Fineract › keeps the parameter form available when a report has cascading lookups —
3.4s - ✅ Dynamic report parameters against Fineract › changing Office changes the Client Listing row set —
5.1s - ✅ Cascading report parameters against Fineract › sends the parent value to the child lookup and clears the child when it changes —
5.8s - ✅ Chart reports against Fineract › renders a chart report as a chart rather than a table —
3.7s
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 —
35.1s - ✅ 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 —
6.6s - ✅ 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 —
4.3s - ✅ a savings account taken through four separated duties, every account built in the UI › the activator activates, and cannot take a deposit —
4.3s - ✅ 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 —
4.0s - ✅ 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 —
11.8s - ✅ 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 —
4.7s
savings-transaction-correction.spec.ts
- ✅ Savings transaction correction › a deposit is reversed and a hold is released —
4.8s
savings-transaction-gating.spec.ts
- ✅ Savings transactions are offered only on an active account › withheld while awaiting approval, offered once active —
4.3s - ✅ Savings transactions are offered only on an active account › the platform refuses a deposit on an account awaiting approval —
145ms
share-account-servicing.spec.ts
- ✅ Share account servicing › an account is approved, activated, traded and closed —
11.3s - ✅ Share account servicing › an application can be rejected —
4.2s
share-product-accounting.spec.ts
- ✅ Share product accounting › a share product is mapped to equity and round-trips on edit —
18.9s
teller-cash-management.spec.ts
- ✅ Teller cash management › a cashier is listed, receives an allocation, and settles cash back —
19.2s - ✅ Teller cash management › settling more than the cashier holds is refused and the form stays usable —
8.7s
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 —
5.1s - ✅ Working Capital loan actions, against a real Fineract › credits the borrower with a goodwill credit, and the balance falls —
4.1s - ✅ Working Capital loan actions, against a real Fineract › writes the loan off, which closes it and opens the recovery path —
5.2s
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 —
13.2s - ✅ Working Capital product accounting, on the platform › prefills a configured product and re-saves it without blanking anything —
3.3s
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 —
3.6s - ✅ Working Capital command permissions, on the platform › UPDATE_WORKINGCAPITALLOAN authorises none of them —
1.5s
working-capital-servicing-backend.spec.ts
- ✅ transaction corrections › undoes a repayment, and the platform marks it reversed —
4.1s - ✅ transaction corrections › offers no correction on the disbursement, which the platform refuses by type —
3.1s - ✅ transaction corrections › adjusts a repayment, which reverses it and books the new amount —
3.7s - ✅ charge adjustment › adjusts a charge, and the outstanding amount follows —
3.5s - ✅ custom datatables › adds, edits and deletes a row of a multi-row table on the loan —
5.4s - ✅ custom datatables › creates a loan that a create-time check would otherwise refuse —
5.4s
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 |
45.4s |
| 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 |
35.6s |
| 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 |
35.1s |
| Loan product accounting › a cash-accounting product is configured, round-trips on edit, and posts to the ledger | loan-product-accounting.spec.ts |
31.4s |
| Loan lifecycle: creation, approval, disbursement › create, approve, and disburse a Progressive loan | loan-lifecycle.spec.ts |
24.3s |
| Loan lifecycle: creation, approval, disbursement › create, approve, and disburse a Cumulative loan | loan-lifecycle.spec.ts |
23.0s |
| Loan lifecycle: creation, approval, disbursement › an approved loan can be returned to pending approval | loan-lifecycle.spec.ts |
22.7s |
| Loan lifecycle: creation, approval, disbursement › the delinquency tab reads a real loan, and the empty data tabs stay hidden | loan-lifecycle.spec.ts |
21.7s |
| Group membership and lifecycle › a group is activated, staffed, given members and a committee, then emptied | group-membership.spec.ts |
20.4s |
| Group membership and lifecycle › an empty group is closed with a reason, and a group with members is refused | group-membership.spec.ts |
19.4s |
📼 Download the HTML report, videos and traces — see the playwright-report-backend artifact.
Generated by run 39037788668 from 635e249. The run executed a fork branch, so treat its contents as unverified.
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
1 participant
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.
Closes #773, closes #774, closes #775, closes #776.
What and why
The last four open Working Capital issues, after #770–#772 and #777 landed in #800. Each is a
gap between what the module's API exposes and what this UI could reach.
Transactions could not be opened, undone or adjusted (#773)
The transactions tab was a read-only table: a mistaken repayment could not be reversed from this
application at all, and nothing showed how a transaction was allocated between principal, fees
and penalties.
A row now opens a detail panel carrying the allocation, the external id and the reversal state,
with the three corrections the module supports. Which correction is offered depends on the
transaction type, because the platform refuses the rest:
WorkingCapitalLoanWritePlatformServiceImplaccepts undo forWAIVE_CHARGES,REPAYMENT,GOODWILL_CREDIT,CHARGE_ADJUSTMENTandPAYOUT_REFUND, and adjust for the same list withoutthe waiver — a waiver has no amount to re-state. Measured as well as read: undo of a disbursement
is refused by type, undo of a repayment and of a charge adjustment succeed, undo of an
already-reversed transaction is refused, and adjust reverses the original and books a
replacement. A discount fee carries no boolean flag on its type enum — there is one per type and
none for this one — so it is recognised by
loanTransactionType.discountFeeand takesdiscountFeeAdjustmentrather thanadjust.Reversed rows are struck through and carry a text marker, because strike-through alone reads
to a screen reader as money that moved.
With maker-checker on, Fineract answers 200 with a
commandIdand noresourceId: the reversalis queued and nothing has happened yet. The panel says so rather than re-reading and showing the
transaction unchanged with no explanation.
Charges could not be opened or adjusted, and the discount fee could not be posted (#774)
Charges could be added and waived. A charge entered wrongly could only be waived in full, and the
amounts paid, waived and outstanding were invisible. A charge row now opens a panel with all of
them plus Adjust, which takes an amount and nothing else — an empty body answers
validation.msg.workingCapitalLoanChargeAdjustment.amount.cannot.be.blank, and the platformdates the adjustment itself. It is prefilled with what is outstanding, which is both the usual
figure and the platform's cap.
An adjustment books a Charge Adjustment transaction, so the panel, the list, the transactions
tab and the loan header are all re-read after it. A waiver does too, and only the charge list was
being refreshed before — fixed here because the panel made it visible.
discountFeejoins the action route, offered on an active loan that has no discount yet:Fineract refuses a second one, and a loan priced with a discount at disbursement reads back
carrying it. Changing an agreed discount stays the
PUT /discountsub-resource behind "Applydiscount" — a different operation with a different code. Its amount is entered rather than
offered, because its template carries the currency and the classification options and no amount.
A product could be saved with a posting rule and no GL accounts (#775)
The form offered
accountingRuleand nothing else, so an accrual product had no accounts mappedand nothing it booked could post. Worse, the rule itself could not be saved: the select bound
each option's
code, the dottedwcAccountingRuleType.nonespelling, and the platform acceptsonly the name —
so any product saved after touching that select was refused. The form now uses the shared
accounting section, which binds
id.Nineteen slots, twelve mandatory, enumerated from the platform the way the other five families
were — post the rule with no mapping ids and read the 400.
AccountingMappingFieldgainsrequired, defaulting to true, because every slot of those five families is mandatory under therules that name it; the Working Capital product is the first with optional ones (the charge-off,
fraud and goodwill slots).
Two differences from the term-loan list look like omissions and are not. There is no interest
slot — this product earns a discount fee, and
incomeFromDiscountFeeAccountIdis the mandatoryslot in its place — and there is a deferred income liability, because the fee is recognised
over the loan's life. The module also has only two rules,
NONEandACC_DEF_REV_AM, so theshared model and section are generalised from a numeric rule to
number | string; the other fivefamilies call them unchanged.
Charge-off and write-off reason mappings are new UI, and route a loss to an expense account by
why it happened. The trap they absorb: the request keys disagree
(
chargeOffReasonCodeValueIdagainstwriteOffReasonCodeValueId) while both read back underreasonCodeValue. Payment allocation reuses the existing editor with its future-installmentrule and credit-allocation half turned off — this family has neither, and the parameter is
refused.
The issue asks for a clear message where a user holds
UPDATE_WORKINGCAPITALLOANPRODUCTbut notREAD_GLACCOUNT, on the premise that the picker loads/glaccounts. It does not: the options comefrom the product template, and a user holding only the two product codes gets all four option
lists back — measured. There is no call to be refused. The real empty case is a tenant with no
accounts of a class, which the section already states per group.
Custom datatables had nowhere to live (#776)
EntityTablesdeclaresWC_LOANandWC_LOAN_PRODUCT, so an institution can attach datatablesto both, and this UI could neither show nor enter that data. Loans get a Custom fields tab;
the product form gets a custom fields section on edit, since a row is keyed by the product.
The shared
EntityDatatablesComponentgains three things, which reach beyond Working Capital —clients, groups, centres, offices, loans and deposit accounts render the same component:
here: a table they cannot read has no rows to show. It also stops the component fetching rows
that can only answer 403.
missing code named.
listing carries no
multiRowflag, so the shape is the discriminator: a multi-row table'sprimary key is its own
idand the entity key rides alongside, while a single-row table'sprimary key is the entity key — which decides whether a row is addressed by id or by entity.
Both were measured by registering one of each.
Create-time checks are honoured, not reported. With a datatable registered as a CREATE check,
POST /working-capital-loansanswers 403 "Please fill in the data table [x] before creating thisworking capital loan", and the row cannot be added afterwards because the create request carries
the rows inline. The application form reads the checks that apply, collects each table's fields
through the existing entry dialog in a new collect-only mode, and sends them as
datatables: [{registeredTableName, data}]. Submit is held back while one is outstanding, ratherthan letting the user fill a long form and collect a 403.
Permissions
Each new control carries its own code, and the pairing was measured by the probe #691 and #777
established — a role holding exactly one code, the command sent with an empty body:
undo(transaction)UNDO_WORKINGCAPITALLOANTRANSACTIONadjust(transaction)ADJUST_WORKINGCAPITALLOANTRANSACTIONdiscountFeeDISCOUNTFEE_WORKINGCAPITALLOANdiscountFeeAdjustmentDISCOUNTFEEADJUSTMENT_WORKINGCAPITALLOANadjustment(charge)ADJUSTMENT_WORKINGCAPITALLOANCHARGE{READ,CREATE,UPDATE,DELETE}_<table>UPDATE_WORKINGCAPITALLOANauthorises none of the 22 commands the diagonal now covers.Two things that fell out of the probe and are worth recording.
ADJUST_WORKINGCAPITALLOANTRANSACTIONwas missing from
scripts/permission-codes.json, so the snapshot is refreshed from the liveplatform: 707 codes against the recorded 720, which had drifted in both directions. And the probe
itself had to get stricter — it treated any 403 as "not authorised", and the platform also answers
403 for a domain rule violation, which made
WAIVE_WORKINGCAPITALLOANCHARGElook unauthorised ona charge an earlier spec had waived. It now reads the globalisation code.
Why the detail views are panels rather than routes
#773 and #774 propose detail routes. A new routed component cannot be written today without
naming Ionic and the generated client directly, which ADR 0005 and ADR 0006 forbid outside
src/app/uiand the API adapters — and the form primitives those ADRs plan do not exist yet, sothere is nothing to build an amount or a date field from.
eslint-suppressions.jsonmay onlyshrink, so the detail lives in the already-suppressed loan screen that owns the tab. The loan
route is read-gated, which is what the issues ask the detail routes to be, and each action still
carries its own code.
Verification
npm test— 2215 unit tests pass across 299 files, up from 2156. New coverage: whichcorrections each transaction type is offered, the undo and adjust payloads, the maker-checker
answer, the charge adjustment payload and refresh, the discount-fee gate and command, the
accounting payload per rule and its prefill (including the reason tables' key renaming), the
per-table datatable permissions, the one-row/many-row discrimination, and the create-check
collection.
npx playwright test --project=backend e2e/working-capital-*-backend.spec.ts— 14 pass in46s against
apache/fineract:latest, across four specs. Two are new:working-capital-servicing-backend.spec.ts(undo, the disbursement's refusal by type, adjustreversing and replacing, a charge adjustment appearing as a transaction, a datatable row added,
edited and deleted, and a loan created that a CREATE check would otherwise refuse) and
working-capital-product-accounting-backend.spec.ts(the twelve accounts configured through theform and read back, and a configured product re-saved without losing anything).
npx playwright test --project=mocked e2e/working-capital-loan-actions.spec.ts— 17 pass,unchanged.
npx playwright test --project=mocked e2e/rbac-feature-flag.spec.ts e2e/rbac-route-protection.spec.ts— 27 pass, exercising the changed permission paths across the rest of the application.
eslint(no new suppressions),prettier --checkandtypecheck:e2epass. Hindi stays at 100% coverage.
Two defects in the existing e2e seeding came out of this and are fixed: the product short name was
built from the leading characters of a base-36 timestamp, which every run in the same minute
shares, so two runs a minute apart collided; and a teardown that threw inside a
finallywasreporting a timeout in the test body as a failed DELETE.
One note on the output: configuring the GL selects raises the interval-sampling
NG0100onng-untouchedthat issue #572 documents, which the fixture classifies as a known artifact and doesnot enforce. It comes from
NgControlStatuson a programmatically setngModel.Screenshots
Not applicable — no new screens. The loan screen gains a Custom fields tab and two detail panels
inside tabs it already had; the product form gains accounting, reason-mapping and allocation
sections.
Checklist
src/app/api/;api-surface.jsonwas regeneratedwith
check-api-surface.mjs --write.generated client, which is why the detail views are panels; see the section above.
enandhi).relevant — two new backend specs, and the existing RBAC probe extended.
before this change.
AI assistance