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
+94
View File
@@ -0,0 +1,94 @@
name: Tests
on:
pull_request:
jobs:
unit:
# act_runner mounts /var/run/docker.sock into every container job, so a fork PR reaches
# the Docker daemon on the runner host. Both jobs need the same guard.
if: github.event.pull_request.head.repo.full_name == github.repository
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '22'
- name: Install dependencies
run: npm ci
- name: Run unit tests
run: npm run test:unit
e2e:
# A fork PR controls both the test files and these steps, so only same-repository
# PRs can be trusted with the E2E_PASSWORD secret.
if: github.event.pull_request.head.repo.full_name == github.repository
runs-on: ubuntu-latest
# Needs the DOCKER-USER exception on the runner host: ruv.wtf is a macvlan interface on a
# container there, so the reply to a bridge-networked job arrives on that container's bridge
# and Docker's inter-bridge isolation drops it. The exception is host-wide, so it also covers
# fork PR jobs, and the bridge name is Docker-generated: recreating the caddy container
# renames it and the test fails closed.
env:
# Dedicated test account on the homeserver, not a personal one.
E2E_HOMESERVER: ruv.wtf
E2E_USER: giteaci
# Repo secret: E2E_PASSWORD. The test fails with a clear message when it is missing.
E2E_PASSWORD: ${{ secrets.E2E_PASSWORD }}
steps:
# .gitmodules uses a relative URL, so the runner resolves it against origin.
- name: Checkout repository
uses: actions/checkout@v4
with:
submodules: true
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '22'
- name: Install dependencies
run: npm ci
# The E2E run drives the vite dev server, so cinny's dependencies are needed too.
- name: Install dependencies (cinny)
working-directory: ./cinny
run: npm ci
# Electron needs system libraries the runner image does not ship. Do not narrow this to
# chromium: Playwright's chromium dep set covers its own bundled browser, not Electron,
# and drops libgtk-3-0t64, libegl1, libegl-mesa0, libgles2, libsecret-1-0, libxtst6 and
# libxss1, which Electron needs to launch. Narrowing it fails with "Process failed to
# launch!".
- name: Install system libraries for Electron
run: npx playwright install-deps
# The container runner image has no xvfb and no fresh apt lists. The host runner already
# has xvfb, so the guard skips the install there; both share the ubuntu-latest label, so
# which one runs is not fixed.
- name: Ensure a display for Electron
run: command -v xvfb-run >/dev/null || (sudo apt-get update && sudo apt-get install -y xvfb)
# The login form only renders after the auth-flows request succeeds, so an
# unreachable homeserver shows up as a 30s locator timeout. Fail fast instead, on
# connect failure or a non-2xx status.
- name: Homeserver reachable from the runner
run: curl -sSf --max-time 20 -o /dev/null -w '%{http_code}\n' "https://$E2E_HOMESERVER/.well-known/matrix/client"
- name: Run login E2E
run: xvfb-run -a npm run test:e2e
# Gitea implements the v3 artifact protocol; v4 rejects it as GHES.
- name: Upload test artifacts
if: failure()
uses: actions/upload-artifact@v3
with:
name: e2e-artifacts
path: |
test-results
playwright-report