Aman-Mittal opened a new issue, #192: URL: https://github.com/apache/fineract-consumer-facing/issues/192
The project's two e2e layers each leave the same gap: nothing checks that the app works with the real BFF. - **Playwright specs** (`frontend/playwright/tests`) stub every BFF response with `page.route`. They show the app works against what we expect the BFF to return, not against the BFF. - **Cucumber** exercises the BFF API directly, without the app. Nothing drives the real app through the real BFF into Fineract, so a mismatch between the two goes unnoticed. For example, #190 (loan withdrawal fails with 400) passed every existing test. **Proposal:** a second Playwright suite that runs against the `docker-compose.e2e.yml` stack with nothing mocked. Each test builds its own consumer as the product does: 1. Staff create the client and accounts in Fineract over its REST API. 2. The consumer self-registers in the app with an emailed OTP. 3. The consumer signs in with password and emailed second factor, with OTPs read from Mailpit. The journeys should cover: - registration and multi-factor sign-in, plus failure paths; - password reset and password change; - accounts (savings and loans); - beneficiaries; - transfers, including beneficiary limits; - loan application and repayment; - profile, settings and the audit trail. Money movements should be asserted in Fineract, not only on screen. CI should run the suite in the existing Playwright job. -- 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]
