Aman-Mittal opened a new issue, #401: URL: https://github.com/apache/fineract-backoffice-ui/issues/401
Part of #395. ## Problem `e2e/utils/seed-api.ts` has well-tested building blocks for creating offices, clients, loans, savings and so on, but each spec composes only the narrow fixture it needs and tears down around itself. There is no way to say "give me a backend that looks like a working MFI". Anyone doing manual work against a fresh stack — release-candidate sanity testing (#377), a demo, a screenshot pass, reproducing a bug report — lands on an empty tenant and hand-creates records through the UI before they can test anything. That is slow, and it is inconsistent between people, so "works on a populated tenant" means something different each time. ## Expected A single command that populates a freshly provisioned Fineract with a representative dataset — an office, staff, a centre, a group, an active loan, a loan pending approval, a savings account, a fixed deposit, a share account, a manual journal entry, reports — and prints what it created. ## Notes Two constraints matter: - It must compose the existing `seed-api.ts` helpers rather than introduce a second seeding implementation to keep in step. - Nothing in it is an assertion, so it must never run as a side effect of `--project=backend` in CI. That argues for its own Playwright project invoked by name, and for not depending on the `setup` project, so it works against a backend that has had nothing else run against it. Documented in `CONTRIBUTING.md` next to the existing e2e backend instructions. -- 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]
