Re: [PR] fix(dates): seed action dialogs from platform date service (#358) [fineract-backoffice-ui]

via GitHub Thu, 08 Oct 2026 22:45:45 -0700


github-actions[bot] commented on PR #732:
URL: 
https://github.com/apache/fineract-backoffice-ui/pull/732#issuecomment-6075101050


   <!-- e2e-report-backend -->
   ### E2E — real Fineract
   ## 🎭 E2E Tests
   
   **❌ 1 failing** — 140 passed · 1 failed · 0 skipped · 1 flaky, across 41 
spec files in 8m 49s.
   
   ### ❌ Failures
   
   - **Dynamic report parameters against Fineract › changing Office changes the 
Client Listing row set** — `report-parameter-backend.spec.ts`
     - Error: response.json: Protocol error (Network.getResponseBody): No data 
found for resource with given identifier
   
   ### ⚠️ Passed on retry
   
   Green overall, but these needed more than one attempt — the shape a flake 
takes.
   
   - **Batch API enclosingTransaction semantics against Fineract › does not 
roll back the earlier steps when enclosingTransaction is false and a later step 
fails** — `batch-api-operations.spec.ts` (1 retry/retries)
   
   ### By spec file
   
   | Spec | ✅ | ❌ | ⏭️ | 🔒 | Time |
   | --- | ---: | ---: | ---: | ---: | ---: |
   | backend.setup.ts | 3 | 0 | 0 | 0 | 5.0s |
   | accounting-closure-backend.spec.ts | 2 | 0 | 0 | 0 | 12.3s |
   | batch-api-operations.spec.ts | 5 | 0 | 0 | 0 | 29.6s |
   | center-servicing.spec.ts | 2 | 0 | 0 | 0 | 17.6s |
   | client-legal-form-search.spec.ts | 1 | 0 | 0 | 0 | 4.3s |
   | client-transfer.spec.ts | 4 | 0 | 0 | 0 | 45.4s |
   | collection-sheet.spec.ts | 1 | 0 | 0 | 0 | 5.8s |
   | deposit-account-servicing.spec.ts | 3 | 0 | 0 | 0 | 25.6s |
   | deposit-product-configuration.spec.ts | 3 | 0 | 0 | 0 | 16.0s |
   | form-layout-reflow.spec.ts | 6 | 0 | 0 | 0 | 30.0s |
   | group-membership.spec.ts | 3 | 0 | 0 | 0 | 46.6s |
   | loan-account-actions.spec.ts | 3 | 0 | 0 | 0 | 22.9s |
   | loan-approved-amount-revision.spec.ts | 3 | 0 | 0 | 0 | 19.9s |
   | loan-charge-off.spec.ts | 2 | 0 | 0 | 0 | 20.1s |
   | loan-flows-non-admin-roles.spec.ts | 8 | 0 | 0 | 0 | 1m 37s |
   | loan-product-accounting.spec.ts | 1 | 0 | 0 | 0 | 26.8s |
   | loan-repayment-gating.spec.ts | 2 | 0 | 0 | 0 | 6.8s |
   | loan-servicing.spec.ts | 2 | 0 | 0 | 0 | 13.2s |
   | login.spec.ts | 4 | 0 | 0 | 0 | 4.6s |
   | oidc-login-backend.spec.ts | 2 | 0 | 0 | 0 | 3.6s |
   | parity-screens.spec.ts | 8 | 0 | 0 | 0 | 32.1s |
   | rbac-backend-restricted-user.spec.ts | 7 | 0 | 0 | 0 | 27.9s |
   | rbac-dead-end-controls.spec.ts | 7 | 0 | 0 | 0 | 25.9s |
   | rbac-disabled-flag-backend.spec.ts | 6 | 0 | 0 | 0 | 19.9s |
   | rbac-multi-permission.spec.ts | 9 | 0 | 0 | 0 | 46.0s |
   | bulk-import-entity-types.spec.ts | 1 | 0 | 0 | 0 | 8.9s |
   | delinquency-configuration.spec.ts | 2 | 0 | 0 | 0 | 16.2s |
   | full-demo.spec.ts | 1 | 0 | 0 | 0 | 51.7s |
   | interest-rate-charts.spec.ts | 1 | 0 | 0 | 0 | 7.2s |
   | loan-lifecycle.spec.ts | 4 | 0 | 0 | 0 | 1m 45s |
   | loan-schedule-type.spec.ts | 3 | 0 | 0 | 0 | 29.2s |
   | rbac-office-scoped-user.spec.ts | 6 | 0 | 0 | 0 | 23.6s |
   | rbac-permissionless-user.spec.ts | 4 | 0 | 0 | 0 | 17.2s |
   | report-mailing-job.spec.ts | 3 | 0 | 0 | 0 | 15.7s |
   | **report-parameter-backend.spec.ts** | 3 | 1 | 0 | 0 | 18.4s |
   | savings-flows-non-admin-roles.spec.ts | 7 | 0 | 0 | 0 | 1m 17s |
   | savings-transaction-correction.spec.ts | 1 | 0 | 0 | 0 | 5.7s |
   | savings-transaction-gating.spec.ts | 2 | 0 | 0 | 0 | 5.2s |
   | share-account-servicing.spec.ts | 2 | 0 | 0 | 0 | 17.1s |
   | share-product-accounting.spec.ts | 1 | 0 | 0 | 0 | 20.9s |
   | teller-cash-management.spec.ts | 2 | 0 | 0 | 0 | 31.4s |
   
   <details>
   <summary><b>All 141 tests</b> — click to expand</summary>
   
   **`backend.setup.ts`**
   
   - ✅ seed backend reference data — `1.9s`
   - ✅ seed backend reference data — `1.5s`
   - ✅ seed backend reference data — `1.7s`
   
   **`accounting-closure-backend.spec.ts`**
   
   - ✅ Accounting closures against Fineract › a closed period reads as Closed, 
and the platform refuses a posting inside it — `6.8s`
   - ✅ Accounting closures against Fineract › the form keeps the user on the 
page and names the reason when Fineract refuses — `5.6s`
   
   **`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 — `4.8s`
   - ✅ 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 — 
`5.0s`
   - ✅ Batch API enclosingTransaction semantics against Fineract › does not 
roll back the earlier steps when enclosingTransaction is false and a later step 
fails — `8.3s` _(retried 1×)_
   - ✅ Batch API Operations on a mobile viewport against Fineract › the sample 
batch scenario is reachable and works by touch at mobile width — `4.7s`
   
   **`center-servicing.spec.ts`**
   
   - ✅ Center servicing › a center is activated, staffed and given a group — 
`12.1s`
   - ✅ 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.3s`
   
   **`client-transfer.spec.ts`**
   
   - ✅ Client transfer between offices › a proposed transfer is held until the 
destination accepts, and then the client moves — `11.3s`
   - ✅ Client transfer between offices › a rejected transfer leaves the client 
on hold, and withdrawing is the way back — `12.2s`
   - ✅ Client transfer between offices › a client can be transferred in one 
step when the user may act for both offices — `10.4s`
   - ✅ 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 — `5.8s`
   
   **`deposit-account-servicing.spec.ts`**
   
   - ✅ Term deposit account servicing › an account is approved, activated and 
closed before maturity — `11.0s`
   - ✅ Term deposit account servicing › a deposit is recorded, listed, and 
reversed without leaving the list — `8.7s`
   - ✅ Term deposit account servicing › an application can be rejected instead 
of approved — `5.9s`
   
   **`deposit-product-configuration.spec.ts`**
   
   - ✅ Deposit product configuration › a fixed deposit product survives being 
edited — `5.8s`
   - ✅ Deposit product configuration › a recurring deposit product can be 
created at all — `4.4s`
   - ✅ Deposit product configuration › a savings product carries its accounting 
configuration — `5.8s`
   
   **`form-layout-reflow.spec.ts`**
   
   - ✅ form layout at the narrow viewport › Create GL Account gives every field 
a usable width at 320px — `4.0s`
   - ✅ form layout at the narrow viewport › Create Loan gives every field a 
usable width at 320px — `4.4s`
   - ✅ form layout at the narrow viewport › Create Office gives every field a 
usable width at 320px — `4.1s`
   - ✅ form layout at the narrow viewport › Create Staff gives every field a 
usable width at 320px — `4.7s`
   - ✅ form layout at the narrow viewport › no page-level horizontal scroll at 
320px — `8.8s`
   - ✅ form layout at the wide viewport › Create GL Account still uses more 
than one column at 1280px — `4.1s`
   
   **`group-membership.spec.ts`**
   
   - ✅ Group membership and lifecycle › a group is activated, staffed, given 
members and a committee, then emptied — `19.7s`
   - ✅ Group membership and lifecycle › notes are recorded against the group 
and can be removed again — `8.3s`
   - ✅ Group membership and lifecycle › an empty group is closed with a reason, 
and a group with members is refused — `18.6s`
   
   **`loan-account-actions.spec.ts`**
   
   - ✅ Loan account lifecycle actions › new action menu items appear only for 
active loans — `7.2s`
   - ✅ Loan account lifecycle actions › undo disbursal shows a confirm dialog 
and reverts the loan to Approved — `8.4s`
   - ✅ Loan account lifecycle actions › write off requires confirmation and 
moves the loan out of Active status — `7.3s`
   
   **`loan-approved-amount-revision.spec.ts`**
   
   - ✅ Loan approved and available-disbursement amount revision › revises the 
approved amount on an active, partially-disbursed loan — `6.1s`
   - ✅ Loan approved and available-disbursement amount revision › revises the 
available disbursement amount, which also changes the approved amount — `7.3s`
   - ✅ Loan approved and available-disbursement amount revision › shows the 
platform’s own refusal, not a generic validation message — `6.6s`
   
   **`loan-charge-off.spec.ts`**
   
   - ✅ Loan servicing commands › charges a loan off through the UI and reverses 
it — `10.3s`
   - ✅ Loan servicing commands › records a goodwill credit through the shared 
transaction form — `9.8s`
   
   **`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 — 
`36.8s`
   - ✅ 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.5s`
   - ✅ 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.6s`
   - ✅ 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.5s`
   - ✅ 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.0s`
   - ✅ 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.4s`
   - ✅ 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.4s`
   - ✅ 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.5s`
   
   **`loan-product-accounting.spec.ts`**
   
   - ✅ Loan product accounting › a cash-accounting product is configured, 
round-trips on edit, and posts to the ledger — `26.8s`
   
   **`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 — `6.5s`
   - ✅ Repayment is offered only where the platform allows it › the platform 
refuses a repayment on a loan awaiting approval — `307ms`
   
   **`loan-servicing.spec.ts`**
   
   - ✅ Loan servicing: notes and transaction adjustment › notes can be added 
and removed, with a confirm dialog on delete — `6.2s`
   - ✅ Loan servicing: notes and transaction adjustment › a repayment 
transaction can be viewed and adjusted with a corrected amount — `7.0s`
   
   **`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.3s`
   - ✅ Login › submit button is enabled when form is filled — `1.1s`
   
   **`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.2s`
   - ✅ identity-provider route against a real Fineract › a real password 
sign-in still gets a session with the route offered — `2.4s`
   
   **`parity-screens.spec.ts`**
   
   - ✅ Screens added for platform parity › a manual journal entry can be read 
whole and reversed — `4.3s`
   - ✅ Screens added for platform parity › an entry that is already reversed is 
not offered again — `3.4s`
   - ✅ Screens added for platform parity › a report definition can be created, 
edited and deleted; a core one cannot — `4.1s`
   - ✅ 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 — `5.0s`
   - ✅ Screens added for platform parity › a fixed deposit is listed as a 
deposit, not as a savings account — `3.4s`
   - ✅ Screens added for platform parity › an office has a screen, and it 
carries its custom fields — `3.4s`
   - ✅ Screens added for platform parity › a savings account carries notes, and 
the note survives a reload — `5.0s`
   
   **`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.8s`
   - ✅ a genuinely restricted Fineract user › is refused a screen their 
permission does not cover, by URL and by the backend — `3.8s`
   - ✅ a genuinely restricted Fineract user › is refused a write screen they 
can read the list for, and the write itself — `5.3s`
   - ✅ a genuinely restricted Fineract user › is not offered the actions it 
would be refused for — `3.2s`
   - ✅ a genuinely restricted Fineract user › is shown an action it cannot 
take, disabled and saying what it needs — `4.4s`
   - ✅ a genuinely restricted Fineract user › the superuser the rest of the 
suite uses is unaffected — `7.2s`
   
   **`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.8s`
   - ✅ the office transactions list › withholds Create from a reader, and the 
route refuses it too — `4.2s`
   - ✅ the office transactions list › offers Create to an administrator — `3.2s`
   - ✅ the office transactions list › refuses the list at the door for the code 
the platform does not check — `3.7s`
   - ✅ a group's member list › names the member without linking when the reader 
cannot open clients — `3.7s`
   - ✅ a group's member list › keeps the link for a reader who holds 
READ_CLIENT — `3.7s`
   
   **`rbac-disabled-flag-backend.spec.ts`**
   
   - ✅ rbacEnabled: false, with a user who holds only READ_CLIENT › is shown 
the whole navigation, including modules their role does not cover — `2.3s`
   - ✅ 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.9s`
   - ✅ rbacEnabled: false, with a user who holds only READ_CLIENT › is still 
refused by Fineract, which the flag does not reach — `456ms`
   - ✅ 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 — `3.7s`
   - ✅ 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.9s`
   - ✅ 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 — `4.1s`
   - ✅ 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 — 
`4.1s`
   - ✅ ALL_FUNCTIONS_READ, against the real Fineract permission catalogue › 
reaches read screens across modules it holds no specific code for — `7.1s`
   - ✅ ALL_FUNCTIONS_READ, against the real Fineract permission catalogue › is 
refused every write screen, and the writes themselves — `5.4s`
   - ✅ a restricted session across a real page reload › keeps the same 
permission boundary after reloading, not just after a fresh login — `8.2s`
   - ✅ 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.4s`
   - ✅ Security module writes (users, roles), against the real backend › 
reaches the list screens but is refused the write screens — `8.8s`
   - ✅ Security module writes (users, roles), against the real backend › is 
refused creating a user and modifying a role, by the backend itself — `221ms`
   
   **`bulk-import-entity-types.spec.ts`**
   
   - ✅ every offered entity type is one the platform accepts — `8.9s`
   
   **`delinquency-configuration.spec.ts`**
   
   - ✅ creates a delinquency range, then edits it — `8.2s`
   - ✅ creates a delinquency bucket from the ranges the template offers — `8.0s`
   
   **`full-demo.spec.ts`**
   
   - ✅ Full feature demo recording › walk through loan schedule type, 
lifecycle, custom fields, collateral, and disbursement — `51.7s`
   
   **`interest-rate-charts.spec.ts`**
   
   - ✅ lists charts without a server error — `7.2s`
   
   **`loan-lifecycle.spec.ts`**
   
   - ✅ Loan lifecycle: creation, approval, disbursement › create, approve, and 
disburse a Cumulative loan — `27.1s`
   - ✅ Loan lifecycle: creation, approval, disbursement › create, approve, and 
disburse a Progressive loan — `27.9s`
   - ✅ Loan lifecycle: creation, approval, disbursement › an approved loan can 
be returned to pending approval — `25.9s`
   - ✅ Loan lifecycle: creation, approval, disbursement › the delinquency tab 
reads a real loan, and the empty data tabs stay hidden — `24.4s`
   
   **`loan-schedule-type.spec.ts`**
   
   - ✅ Loan Schedule Type (Cumulative vs Progressive) › loan products list 
shows a schedule type chip per product — `7.9s`
   - ✅ Loan Schedule Type (Cumulative vs Progressive) › create a Progressive 
loan product end-to-end and verify it round-trips — `12.7s`
   - ✅ Loan Schedule Type (Cumulative vs Progressive) › loan creation shows the 
schedule type badge for a Progressive product — `8.6s`
   
   **`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 — `386ms`
   - ✅ an account scoped to a branch office › is shown only its own office in 
the client list, and told which office it is in — `4.2s`
   - ✅ an account scoped to a branch office › sees a shorter list than an 
identically-permissioned head-office account — `3.9s`
   - ✅ an account scoped to a branch office › is refused another office’s 
client by the platform, and told so once — `5.0s`
   - ✅ an account scoped to a branch office › can still open the record that is 
in its own office — `3.8s`
   - ✅ an account scoped to a branch office › is not offered an edit it would 
be refused for on the Offices screen — `6.3s`
   
   **`rbac-permissionless-user.spec.ts`**
   
   - ✅ an account whose role grants nothing › is authenticated by Fineract and 
authorized by it for nothing — `628ms`
   - ✅ 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.8s`
   - ✅ an account whose role grants nothing › is left a navigation whose 
entries actually work — `4.0s`
   
   **`report-mailing-job.spec.ts`**
   
   - ✅ report mailing job creation › is no longer refused for a missing 
parameter — `4.8s`
   - ✅ report mailing job creation › the payload carries the locale and the 
schedule — `4.5s`
   - ✅ report mailing job creation at the narrow viewport › every field is 
reachable and the job still saves at 320px — `6.4s`
   
   **`report-parameter-backend.spec.ts`**
   
   - ✅ Dynamic report parameters against Fineract › keeps the parameter form 
available when a report has cascading lookups — `3.5s`
   - ❌ Dynamic report parameters against Fineract › changing Office changes the 
Client Listing row set — `4.7s` _(retried 2×)_
   - ✅ Cascading report parameters against Fineract › sends the parent value to 
the child lookup and clears the child when it changes — `6.2s`
   - ✅ Chart reports against Fineract › renders a chart report as a chart 
rather than a table — `3.9s`
   
   **`savings-flows-non-admin-roles.spec.ts`**
   
   - ✅ a savings account taken through four separated duties, every account 
built in the UI › an administrator builds the five roles and accounts through 
the forms — `36.3s`
   - ✅ 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 — `7.0s`
   - ✅ 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 — `5.3s`
   - ✅ a savings account taken through four separated duties, every account 
built in the UI › the activator activates, and cannot take a deposit — `5.0s`
   - ✅ 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 — `5.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 — `13.1s`
   - ✅ 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 — `5.1s`
   
   **`savings-transaction-correction.spec.ts`**
   
   - ✅ Savings transaction correction › a deposit is reversed and a hold is 
released — `5.7s`
   
   **`savings-transaction-gating.spec.ts`**
   
   - ✅ Savings transactions are offered only on an active account › withheld 
while awaiting approval, offered once active — `5.0s`
   - ✅ Savings transactions are offered only on an active account › the 
platform refuses a deposit on an account awaiting approval — `213ms`
   
   **`share-account-servicing.spec.ts`**
   
   - ✅ Share account servicing › an account is approved, activated, traded and 
closed — `11.9s`
   - ✅ Share account servicing › an application can be rejected — `5.3s`
   
   **`share-product-accounting.spec.ts`**
   
   - ✅ Share product accounting › a share product is mapped to equity and 
round-trips on edit — `20.9s`
   
   **`teller-cash-management.spec.ts`**
   
   - ✅ Teller cash management › a cashier is listed, receives an allocation, 
and settles cash back — `21.2s`
   - ✅ Teller cash management › settling more than the cashier holds is refused 
and the form stays usable — `10.2s`
   
   </details>
   
   <details>
   <summary><b>Slowest 10</b> — what the shard counts should be tuned 
against</summary>
   
   | Test | Spec | Time |
   | --- | --- | ---: |
   | Full feature demo recording › walk through loan schedule type, lifecycle, 
custom fields, collateral, and disbursement | `full-demo.spec.ts` | 51.7s |
   | a loan taken through four separated duties, every account built in the UI 
› an administrator builds the four roles and accounts through the forms | 
`loan-flows-non-admin-roles.spec.ts` | 36.8s |
   | 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` | 36.3s |
   | Loan lifecycle: creation, approval, disbursement › create, approve, and 
disburse a Progressive loan | `loan-lifecycle.spec.ts` | 27.9s |
   | Loan lifecycle: creation, approval, disbursement › create, approve, and 
disburse a Cumulative loan | `loan-lifecycle.spec.ts` | 27.1s |
   | Loan product accounting › a cash-accounting product is configured, 
round-trips on edit, and posts to the ledger | 
`loan-product-accounting.spec.ts` | 26.8s |
   | Loan lifecycle: creation, approval, disbursement › an approved loan can be 
returned to pending approval | `loan-lifecycle.spec.ts` | 25.9s |
   | Loan lifecycle: creation, approval, disbursement › the delinquency tab 
reads a real loan, and the empty data tabs stay hidden | 
`loan-lifecycle.spec.ts` | 24.4s |
   | Teller cash management › a cashier is listed, receives an allocation, and 
settles cash back | `teller-cash-management.spec.ts` | 21.2s |
   | Share product accounting › a share product is mapped to equity and 
round-trips on edit | `share-product-accounting.spec.ts` | 20.9s |
   
   </details>
   
   
   📼 [Download the HTML report, videos and 
traces](https://github.com/apache/fineract-backoffice-ui/actions/runs/37827244801)
 — see the `playwright-report-backend` artifact.
   
   <sub>Generated by [run 
37827244801](https://github.com/apache/fineract-backoffice-ui/actions/runs/37827244801)
 from `478c32b`. The run executed a fork branch, so treat its contents as 
unverified.</sub>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Re: [PR] fix(dates): seed action dialogs from platform date service (#358) [fineract-backoffice-ui]

Reply via email to