Repository navigation
docs(e2e): select configured Playwright projects - #741
Conversation
🔄 What this change talks toNo application TypeScript files changed, so there is nothing to draw. Generated by run 38686697615 from |
E2E — mocked backend🎭 E2E Tests✅ All green — 412 passed · 0 failed · 1 skipped, across 40 spec files in 8m 23s. By spec file
All 413 tests — click to expand
Slowest 10 — what the shard counts should be tuned against
📼 Download the HTML report, videos and traces — see the Generated by run 38686697683 from |
E2E — real Fineract🎭 E2E Tests✅ All green — 141 passed · 0 failed · 0 skipped · 1 flaky, across 41 spec files in 9m 31s.
|
| Spec | ✅ | ❌ | ⏭️ | 🔒 | Time |
|---|---|---|---|---|---|
| backend.setup.ts | 3 | 0 | 0 | 0 | 6.1s |
| accounting-closure-backend.spec.ts | 2 | 0 | 0 | 0 | 14.6s |
| batch-api-operations.spec.ts | 5 | 0 | 0 | 0 | 29.9s |
| center-servicing.spec.ts | 2 | 0 | 0 | 0 | 17.5s |
| client-legal-form-search.spec.ts | 1 | 0 | 0 | 0 | 5.3s |
| client-transfer.spec.ts | 4 | 0 | 0 | 0 | 46.8s |
| collection-sheet.spec.ts | 1 | 0 | 0 | 0 | 6.3s |
| deposit-account-servicing.spec.ts | 3 | 0 | 0 | 0 | 26.2s |
| deposit-product-configuration.spec.ts | 3 | 0 | 0 | 0 | 16.4s |
| form-layout-reflow.spec.ts | 6 | 0 | 0 | 0 | 31.5s |
| group-membership.spec.ts | 3 | 0 | 0 | 0 | 47.0s |
| loan-account-actions.spec.ts | 3 | 0 | 0 | 0 | 23.9s |
| loan-approved-amount-revision.spec.ts | 3 | 0 | 0 | 0 | 19.3s |
| loan-charge-off.spec.ts | 2 | 0 | 0 | 0 | 20.1s |
| loan-flows-non-admin-roles.spec.ts | 8 | 0 | 0 | 0 | 1m 43s |
| loan-product-accounting.spec.ts | 1 | 0 | 0 | 0 | 32.9s |
| loan-repayment-gating.spec.ts | 2 | 0 | 0 | 0 | 9.9s |
| loan-servicing.spec.ts | 2 | 0 | 0 | 0 | 19.1s |
| login.spec.ts | 4 | 0 | 0 | 0 | 6.7s |
| oidc-login-backend.spec.ts | 2 | 0 | 0 | 0 | 4.8s |
| parity-screens.spec.ts | 8 | 0 | 0 | 0 | 44.8s |
| rbac-backend-restricted-user.spec.ts | 7 | 0 | 0 | 0 | 35.6s |
| rbac-dead-end-controls.spec.ts | 7 | 0 | 0 | 0 | 36.7s |
| rbac-disabled-flag-backend.spec.ts | 6 | 0 | 0 | 0 | 26.6s |
| rbac-multi-permission.spec.ts | 9 | 0 | 0 | 0 | 58.7s |
| bulk-import-entity-types.spec.ts | 1 | 0 | 0 | 0 | 10.1s |
| delinquency-configuration.spec.ts | 2 | 0 | 0 | 0 | 19.1s |
| full-demo.spec.ts | 1 | 0 | 0 | 0 | 58.3s |
| interest-rate-charts.spec.ts | 1 | 0 | 0 | 0 | 7.9s |
| loan-lifecycle.spec.ts | 4 | 0 | 0 | 0 | 1m 57s |
| loan-schedule-type.spec.ts | 3 | 0 | 0 | 0 | 33.5s |
| rbac-office-scoped-user.spec.ts | 6 | 0 | 0 | 0 | 27.7s |
| rbac-permissionless-user.spec.ts | 4 | 0 | 0 | 0 | 20.5s |
| report-mailing-job.spec.ts | 3 | 0 | 0 | 0 | 18.4s |
| report-parameter-backend.spec.ts | 4 | 0 | 0 | 0 | 22.4s |
| savings-flows-non-admin-roles.spec.ts | 7 | 0 | 0 | 0 | 1m 34s |
| savings-transaction-correction.spec.ts | 1 | 0 | 0 | 0 | 6.6s |
| savings-transaction-gating.spec.ts | 2 | 0 | 0 | 0 | 6.5s |
| share-account-servicing.spec.ts | 2 | 0 | 0 | 0 | 17.8s |
| share-product-accounting.spec.ts | 1 | 0 | 0 | 0 | 24.3s |
| teller-cash-management.spec.ts | 2 | 0 | 0 | 0 | 36.0s |
All 141 tests — click to expand
backend.setup.ts
- ✅ seed backend reference data —
2.1s - ✅ seed backend reference data —
1.9s - ✅ seed backend reference data —
2.1s
accounting-closure-backend.spec.ts
- ✅ Accounting closures against Fineract › a closed period reads as Closed, and the platform refuses a posting inside it —
7.9s - ✅ Accounting closures against Fineract › the form keeps the user on the page and names the reason when Fineract refuses —
6.7s
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.2s - ✅ Batch API Operations against Fineract › shows a parse error instead of submitting when the batch input is not valid JSON —
6.5s - ✅ Batch API enclosingTransaction semantics against Fineract › rolls back the earlier steps when enclosingTransaction is true and a later step fails —
8.7s(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.6s
center-servicing.spec.ts
- ✅ Center servicing › a center is activated, staffed and given a group —
12.5s - ✅ Center servicing › notes are recorded against the center —
5.1s
client-legal-form-search.spec.ts
- ✅ Client list: legal form filtering › an entity client appears in the main client list —
5.3s
client-transfer.spec.ts
- ✅ Client transfer between offices › a proposed transfer is held until the destination accepts, and then the client moves —
11.9s - ✅ 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.5s - ✅ Client staff assignment › an officer can be assigned and then removed —
11.3s
collection-sheet.spec.ts
- ✅ Collection Sheet › scopes staff to the office, sends the choice, and reports an empty sheet —
6.3s
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 —
9.0s - ✅ Term deposit account servicing › an application can be rejected instead of approved —
6.2s
deposit-product-configuration.spec.ts
- ✅ Deposit product configuration › a fixed deposit product survives being edited —
5.6s - ✅ Deposit product configuration › a recurring deposit product can be created at all —
4.7s - ✅ Deposit product configuration › a savings product carries its accounting configuration —
6.1s
form-layout-reflow.spec.ts
- ✅ form layout at the narrow viewport › Create GL Account gives every field a usable width at 320px —
4.2s - ✅ 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.5s - ✅ form layout at the narrow viewport › Create Staff gives every field a usable width at 320px —
4.6s - ✅ 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.3s
group-membership.spec.ts
- ✅ Group membership and lifecycle › a group is activated, staffed, given members and a committee, then emptied —
20.1s - ✅ 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.7s
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 —
8.2s
loan-approved-amount-revision.spec.ts
- ✅ Loan approved and available-disbursement amount revision › revises the approved amount on an active, partially-disbursed loan —
6.9s - ✅ Loan approved and available-disbursement amount revision › revises the available disbursement amount, which also changes the approved amount —
6.8s - ✅ Loan approved and available-disbursement amount revision › shows the platform’s own refusal, not a generic validation message —
5.6s
loan-charge-off.spec.ts
- ✅ Loan servicing commands › charges a loan off through the UI and reverses it —
11.0s - ✅ 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 —
40.7s - ✅ 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.8s - ✅ 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.6s - ✅ 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.3s - ✅ 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 —
6.9s - ✅ 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 —
4.8s - ✅ a loan taken through four separated duties, every account built in the UI › a repayment duty reaches its own form, and records a repayment —
17.7s
loan-product-accounting.spec.ts
- ✅ Loan product accounting › a cash-accounting product is configured, round-trips on edit, and posts to the ledger —
32.9s
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 —
9.5s - ✅ Repayment is offered only where the platform allows it › the platform refuses a repayment on a loan awaiting approval —
406ms
loan-servicing.spec.ts
- ✅ Loan servicing: notes and transaction adjustment › notes can be added and removed, with a confirm dialog on delete —
8.9s - ✅ Loan servicing: notes and transaction adjustment › a repayment transaction can be viewed and adjusted with a corrected amount —
10.2s
login.spec.ts
- ✅ Login › login page displays correctly —
1.4s - ✅ Login › login form has required fields —
1.4s - ✅ Login › submit button is disabled when form is empty —
1.6s - ✅ Login › submit button is enabled when form is filled —
2.3s
oidc-login-backend.spec.ts
- ✅ identity-provider route against a real Fineract › is offered beside the password form, and pressing it sends nothing to Fineract —
1.8s - ✅ identity-provider route against a real Fineract › a real password sign-in still gets a session with the route offered —
3.0s
parity-screens.spec.ts
- ✅ Screens added for platform parity › a manual journal entry can be read whole and reversed —
6.3s - ✅ Screens added for platform parity › an entry that is already reversed is not offered again —
4.6s - ✅ Screens added for platform parity › a report definition can be created, edited and deleted; a core one cannot —
5.7s - ✅ Screens added for platform parity › a core report opens read-only with only its in-use setting —
4.5s - ✅ Screens added for platform parity › a pending loan is approved from the queue, in a batch —
6.5s - ✅ Screens added for platform parity › a fixed deposit is listed as a deposit, not as a savings account —
4.9s - ✅ Screens added for platform parity › an office has a screen, and it carries its custom fields —
5.7s - ✅ Screens added for platform parity › a savings account carries notes, and the note survives a reload —
6.6s
rbac-backend-restricted-user.spec.ts
- ✅ a genuinely restricted Fineract user › holds exactly the permissions their role was granted —
211ms - ✅ a genuinely restricted Fineract user › reaches the screen their permission covers —
4.8s - ✅ a genuinely restricted Fineract user › is refused a screen their permission does not cover, by URL and by the backend —
4.7s - ✅ a genuinely restricted Fineract user › is refused a write screen they can read the list for, and the write itself —
6.6s - ✅ a genuinely restricted Fineract user › is not offered the actions it would be refused for —
4.5s - ✅ a genuinely restricted Fineract user › is shown an action it cannot take, disabled and saying what it needs —
5.9s - ✅ a genuinely restricted Fineract user › the superuser the rest of the suite uses is unaffected —
9.0s
rbac-dead-end-controls.spec.ts
- ✅ a client's account tables › withhold the link, but not the number, from a user who cannot open the account —
5.0s - ✅ a client's account tables › keep the link for a user who holds READ_LOAN —
6.4s - ✅ the office transactions list › withholds Create from a reader, and the route refuses it too —
6.1s - ✅ the office transactions list › offers Create to an administrator —
4.6s - ✅ the office transactions list › refuses the list at the door for the code the platform does not check —
4.3s - ✅ a group's member list › names the member without linking when the reader cannot open clients —
4.9s - ✅ a group's member list › keeps the link for a reader who holds READ_CLIENT —
5.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 —
3.4s - ✅ rbacEnabled: false, with a user who holds only READ_CLIENT › is admitted by the route guard to a screen their role does not cover —
6.9s - ✅ rbacEnabled: false, with a user who holds only READ_CLIENT › is still refused by Fineract, which the flag does not reach —
592ms - ✅ 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 —
5.3s - ✅ rbacEnabled: false, with a user who holds only READ_CLIENT › gets the same treatment on a second refused list, not a one-screen fix —
4.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 —
5.5s
rbac-multi-permission.spec.ts
- ✅ a route declaring more than one permission code (OR semantics) › is admitted by either declared code alone —
5.1s - ✅ a route declaring more than one permission code (OR semantics) › is admitted by the other declared code alone —
4.9s - ✅ a route declaring more than one permission code (OR semantics) › is refused when holding neither declared code, by the router and by the backend —
5.4s - ✅ ALL_FUNCTIONS_READ, against the real Fineract permission catalogue › reaches read screens across modules it holds no specific code for —
9.4s - ✅ ALL_FUNCTIONS_READ, against the real Fineract permission catalogue › is refused every write screen, and the writes themselves —
7.4s - ✅ a restricted session across a real page reload › keeps the same permission boundary after reloading, not just after a fresh login —
10.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 —
5.4s - ✅ Security module writes (users, roles), against the real backend › reaches the list screens but is refused the write screens —
10.5s - ✅ Security module writes (users, roles), against the real backend › is refused creating a user and modifying a role, by the backend itself —
284ms
bulk-import-entity-types.spec.ts
- ✅ every offered entity type is one the platform accepts —
10.1s
delinquency-configuration.spec.ts
- ✅ creates a delinquency range, then edits it —
9.9s - ✅ creates a delinquency bucket from the ranges the template offers —
9.1s
full-demo.spec.ts
- ✅ Full feature demo recording › walk through loan schedule type, lifecycle, custom fields, collateral, and disbursement —
58.3s
interest-rate-charts.spec.ts
- ✅ lists charts without a server error —
7.9s
loan-lifecycle.spec.ts
- ✅ Loan lifecycle: creation, approval, disbursement › create, approve, and disburse a Cumulative loan —
30.2s - ✅ Loan lifecycle: creation, approval, disbursement › create, approve, and disburse a Progressive loan —
31.3s - ✅ Loan lifecycle: creation, approval, disbursement › an approved loan can be returned to pending approval —
28.8s - ✅ Loan lifecycle: creation, approval, disbursement › the delinquency tab reads a real loan, and the empty data tabs stay hidden —
26.5s
loan-schedule-type.spec.ts
- ✅ Loan Schedule Type (Cumulative vs Progressive) › loan products list shows a schedule type chip per product —
9.0s - ✅ Loan Schedule Type (Cumulative vs Progressive) › create a Progressive loan product end-to-end and verify it round-trips —
14.4s - ✅ Loan Schedule Type (Cumulative vs Progressive) › loan creation shows the schedule type badge for a Progressive product —
10.2s
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 —
450ms - ✅ an account scoped to a branch office › is shown only its own office in the client list, and told which office it is in —
5.2s - ✅ an account scoped to a branch office › sees a shorter list than an identically-permissioned head-office account —
4.8s - ✅ an account scoped to a branch office › is refused another office’s client by the platform, and told so once —
5.2s - ✅ an account scoped to a branch office › can still open the record that is in its own office —
4.8s - ✅ an account scoped to a branch office › is not offered an edit it would be refused for on the Offices screen —
7.1s
rbac-permissionless-user.spec.ts
- ✅ an account whose role grants nothing › is authenticated by Fineract and authorized by it for nothing —
699ms - ✅ an account whose role grants nothing › is signed in and landed on a screen rather than stranded at the login form —
4.7s - ✅ an account whose role grants nothing › is offered no permission-gated module, and refused each one by URL and by Fineract —
10.4s - ✅ an account whose role grants nothing › is left a navigation whose entries actually work —
4.7s
report-mailing-job.spec.ts
- ✅ report mailing job creation › is no longer refused for a missing parameter —
5.7s - ✅ report mailing job creation › the payload carries the locale and the schedule —
5.3s - ✅ report mailing job creation at the narrow viewport › every field is reachable and the job still saves at 320px —
7.3s
report-parameter-backend.spec.ts
- ✅ Dynamic report parameters against Fineract › keeps the parameter form available when a report has cascading lookups —
4.5s - ✅ Dynamic report parameters against Fineract › changing Office changes the Client Listing row set —
6.6s - ✅ Cascading report parameters against Fineract › sends the parent value to the child lookup and clears the child when it changes —
6.8s - ✅ Chart reports against Fineract › renders a chart report as a chart rather than a table —
4.5s
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 —
42.0s - ✅ a savings account taken through four separated duties, every account built in the UI › the officer books the application and is not offered approval of it —
8.7s - ✅ 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 —
6.5s - ✅ a savings account taken through four separated duties, every account built in the UI › the activator activates, and cannot take a deposit —
6.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.8s - ✅ 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 —
18.3s - ✅ 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 —
6.6s
savings-transaction-correction.spec.ts
- ✅ Savings transaction correction › a deposit is reversed and a hold is released —
6.6s
savings-transaction-gating.spec.ts
- ✅ Savings transactions are offered only on an active account › withheld while awaiting approval, offered once active —
6.3s - ✅ Savings transactions are offered only on an active account › the platform refuses a deposit on an account awaiting approval —
211ms
share-account-servicing.spec.ts
- ✅ Share account servicing › an account is approved, activated, traded and closed —
12.1s - ✅ Share account servicing › an application can be rejected —
5.7s
share-product-accounting.spec.ts
- ✅ Share product accounting › a share product is mapped to equity and round-trips on edit —
24.3s
teller-cash-management.spec.ts
- ✅ Teller cash management › a cashier is listed, receives an allocation, and settles cash back —
24.4s - ✅ Teller cash management › settling more than the cashier holds is refused and the form stays usable —
11.7s
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 |
58.3s |
| 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 |
42.0s |
| a loan taken through four separated duties, every account built in the UI › an administrator builds the four roles and accounts through the forms | loan-flows-non-admin-roles.spec.ts |
40.7s |
| Loan product accounting › a cash-accounting product is configured, round-trips on edit, and posts to the ledger | loan-product-accounting.spec.ts |
32.9s |
| Loan lifecycle: creation, approval, disbursement › create, approve, and disburse a Progressive loan | loan-lifecycle.spec.ts |
31.3s |
| Loan lifecycle: creation, approval, disbursement › create, approve, and disburse a Cumulative loan | loan-lifecycle.spec.ts |
30.2s |
| Loan lifecycle: creation, approval, disbursement › an approved loan can be returned to pending approval | loan-lifecycle.spec.ts |
28.8s |
| Loan lifecycle: creation, approval, disbursement › the delinquency tab reads a real loan, and the empty data tabs stay hidden | loan-lifecycle.spec.ts |
26.5s |
| Teller cash management › a cashier is listed, receives an allocation, and settles cash back | teller-cash-management.spec.ts |
24.4s |
| Share product accounting › a share product is mapped to equity and round-trips on edit | share-product-accounting.spec.ts |
24.3s |
📼 Download the HTML report, videos and traces — see the playwright-report-backend artifact.
Generated by run 38686697683 from 147ee55. The run executed a fork branch, so treat its contents as unverified.
Following the focused E2E example currently fails with
Project(s) "chromium" not found. Use the configuredmockedproject in the run examples and distinguish the backend, mobile, two-factor and demo-seeding prerequisites. An unfiltered Playwright run selects all of those projects.Replace the stale suite counts with a
--listdiscovery command and a link to the current CI shard/report documentation.Related #664 (local E2E contributor workflow).
Validation:
--list: exit 1, nonexistent project.--list: exit 0, 1 test in 1 file; mobile discovery: exit 0, 30 tests in 4 files.npm ci,npm run lint,npm run format:check,npm run i18n:check,npm run check:icons,npm run check:a11y-names,npm run api:surface, andbash scripts/check-license.shpassed.npm test -- --watch=false: 299 files / 2112 tests passed.npm run buildpassed, with the existing header stylesheet budget warning.npm run ga:check: 0 blocking failures, 0 undetermined; the existing adapter migration backlog remains advisory.This documentation change was verified through test discovery; browser journeys and backend tests were not executed. The commit is signed.