mirror of
https://github.com/Zproger/Aurum.git
synced 2026-10-13 02:56:39 +07:00
8e46726b4d
backend/tests/: 33 pytest tests against a real Postgres database (aurum_test, created/migrated/dropped per run) exercised through the actual HTTP API — not sqlite, not mocks, and the real `aurum` database is never opened (app lifespan is skipped, get_session is overridden per test). Covers transaction category-kind validation, year/month/date-range filtering and pagination, dashboard summary arithmetic, budget status, cash flow, and the /transactions/years picker. e2e/: 6 Playwright specs driving a real browser against a fully separate throwaway docker-compose stack (run.sh: separate project name, database, port, and volume, torn down with `down -v` on exit) — regression coverage for the Recent Transactions month bug, the Card grid-overflow bug, the frozen-year bug, the Net Worth default range, and the Dashboard-> Transactions deep link, all fixed earlier this session. Also synced the backend's APP_VERSION constant (stale at 0.15.2, embedded in exported backups) with the frontend version.
51 lines
1.7 KiB
Markdown
51 lines
1.7 KiB
Markdown
# E2E tests
|
|
|
|
Playwright driving a real browser against a real, fully isolated Aurum
|
|
stack — not the self-hosted instance you actually use day to day. These
|
|
tests create and read real data over the real HTTP API and real rendered
|
|
UI, which is the only way to actually catch things like a CSS layout
|
|
overflow or a filter that's silently ignored — a backend-only test suite
|
|
can't see either.
|
|
|
|
## Isolation
|
|
|
|
`run.sh` brings up a *second*, throwaway stack alongside your real one:
|
|
|
|
| | real instance | e2e stack |
|
|
|---|---|---|
|
|
| compose project | `aurum` (default) | `aurum-e2e` |
|
|
| Postgres database | `aurum` | `aurum_e2e` |
|
|
| web port | 3000 | 3100 |
|
|
|
|
Different project name means different containers, network, and — crucially
|
|
— a different named Postgres volume, so the e2e Postgres data directory is
|
|
physically separate from `aurum_pgdata`. `run.sh` always tears the e2e stack
|
|
down with `docker compose down -v` on exit (even on failure/Ctrl-C), so no
|
|
test data is left behind and your real instance is never touched, restarted,
|
|
or read from.
|
|
|
|
## Running
|
|
|
|
```bash
|
|
cd e2e
|
|
./run.sh
|
|
```
|
|
|
|
Pass extra Playwright CLI args through, e.g. to run one file or open the
|
|
trace viewer on failure:
|
|
|
|
```bash
|
|
./run.sh tests/year-switcher.spec.ts
|
|
./run.sh --headed
|
|
```
|
|
|
|
## Adding a test
|
|
|
|
- Seed data via the `request` fixture and the helpers in `tests/helpers.ts`
|
|
(hits `/api/...` directly — fast and doesn't depend on clicking through a
|
|
form). Then drive the actual page for the behavior under test.
|
|
- Tests run with `workers: 1` against one shared backend/DB within a single
|
|
`run.sh` invocation, so give each spec's seeded data a distinct year/month
|
|
(or otherwise non-overlapping scope) rather than relying on a clean slate
|
|
between spec files.
|