Account E2E Tests
Playwright scenarios for pay-on-account (PAYACCOUNT) flows in the place view: operational panel, offline behaviour, and related UI gates.
Baseline: Preloaded database (server/ddbb/datacontent.json) includes optionPayAccount and one seed account (E2E Pay Account). The pw stack reset restores deterministic baseline state before runs.
See E2E Testing (Playwright) for environment setup and how to run tests.
Tests in this guide
- account detail shows offline warning and hides settlement controls — full diagram and implementation (new tab)
account detail shows offline warning and hides settlement controls
A staff member is already inside Test Place, opens Pay accounts from the side menu, and selects the seeded account E2E Pay Account. While the app still believes it has network, the operational detail shows the normal blocks (name, client, block/unblock)—without the offline banner.
Then connectivity drops: the online probe fails and the UI switches to the same offline pattern used in reports—account-view-offline with the @place_reports_offline warning. Pending lists, proforma rows, and settlement must disappear so nobody tries to liquidate against remote ticket history without place/ticketlst. Name, client, and block/unblock controls stay available.
Where it lives: e2e/tests/account/account-offline.spec.ts — test account detail shows offline warning and hides settlement controls.