Add automated testing infrastructure (Vitest + Playwright E2E) (#110)
Build / prepare (push) Successful in 14s
Checks / checks (push) Successful in 2m5s
Build / build-windows (push) Successful in 4m43s
Build / build-linux (push) Successful in 2m37s
Build / finalize-release (push) Successful in 5s

Co-authored-by: litruv <litruv@gmail.com>
This commit was merged in pull request #110.
This commit is contained in:
2026-11-03 13:51:15 +11:00
committed by litruv
parent 2444654a58
commit 7c33ae587d
9 changed files with 1458 additions and 6 deletions
+22
View File
@@ -30,6 +30,28 @@ To build the app locally, run:
To start local dev server, run:
* `npm run dev`
## Testing
* `npm run test` - unit and E2E
* `npm run test:unit` - Vitest
* `npm run test:e2e` - Playwright driving Electron
The E2E test drives the real Electron app against the vite dev server, so it needs the
cinny dependencies installed and an X display. On a headless machine run it under xvfb:
`xvfb-run -a npm run test:e2e`.
The E2E test logs in to a live homeserver over the network, so it needs network access and a
working test account. It uses a dedicated account, never a personal one:
Variable | Default
---|---
`E2E_HOMESERVER` | `ruv.wtf`
`E2E_USER` | `giteaci`
`E2E_PASSWORD` | required, read from the environment, never committed
A failed E2E run attaches a screenshot and the main and renderer console logs to the
report. CI uploads `test-results/` and `playwright-report/` as artifacts.
## Plugin System
Paarrot includes a plugin system for extending and customising the app with JavaScript modules.