Aman-Mittal opened a new pull request, #349: URL: https://github.com/apache/fineract-backoffice-ui/pull/349
The end-to-end suites already drive a real Fineract through the real UI, so they *are* a walkthrough of the application. `full-demo.spec.ts` was already recorded that way; this makes the same switch available to all of them. ```bash npm run e2e:stack # add --fresh for a clean volume npm run demo:record ``` `DEMO_RECORD=1` turns video on for every spec rather than only for failures, and the script sets it together with the pacing (`DEMO_BEAT_MS`) and an output directory, running the backend project single-worker so the clips come out in a sensible order. **Verified by running it:** 46 tests, **45 videos, 198 MB**, covering the loan lifecycle, groups, centers, savings and deposit servicing, product accounting, reporting, teller cash management, client transfers and login. ## Why record the suites instead of writing a demo script A demo script has nothing keeping it honest, and drifts from the application the first time a screen changes. These clips cannot drift: a flow that stopped working would fail the suite before it recorded anything. The recording is a by-product of the tests passing, which is exactly the property you want from a demo. `DOCS/DEMO.md` maps each flow to the spec that records it, and gives the `ffmpeg` incantation for stitching the clips into one file — ffmpeg is needed for that alone, not to record or to watch them. The clips have no audio and no captions. They are a record of the flows working, not a produced video; if a narrated demo is wanted, these are the raw material. -- 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]
