Bradley Nelson
e3823ce470
Add an end-to-end and unit test suite for the SvelteKit frontend:
- Playwright e2e specs (tests/e2e/spa) with a throwaway container stack,
codegen scenarios, and an Istanbul-based coverage report pipeline.
- Vitest unit tests across API endpoints, components, stores and composables.
- `data-testid` hooks on interactive elements (AppShell, FileViewer,
ShareDialog, search, photos, files breadcrumbs, login/Nextcloud flows,
public share pages) so the e2e suite can target them deterministically.
- Serve the SPA app-shell CSP from a <meta> policy (svelte.config.js) plus a
middleware that skips the CSP header on HTML; move the Nextcloud Login Flow
v2 grant page to the SvelteKit /nextcloud/login route.
- `just front-codegen` recipe and start-server-spa.sh harness.
Make the test environment robust and consistent:
- Install a deterministic in-memory localStorage/sessionStorage in the Vitest
setup so storage behaves identically across Node versions (Node 26 ships a
native Web Storage global that otherwise shadows jsdom's).
- Pin devenv to Node 26 + PostgreSQL 18 and pin every CI job to Node 26.3.0
so the dev shell and CI run the same toolchain versions.
Repair the API/WebDAV (hurl) suite, which had drifted from the backend:
- Migrate the removed `/api/folders/{id}/listing` endpoint to `/resources`
(cursor-paginated `{items:[{resource_type,resource}]}` shape) across the
batch-copy, grants, nested-group, and WebDAV NC tests + the dav_helpers
wipe routine.
- Stop photos_etag from uploading the dedup-tracked fixture so the dedup
blob-lifecycle test can own its content-addressed blob exclusively.
- dedup_create now asserts the idempotent same-content re-upload (201 +
existing file id) instead of the stale 409 expectation.
Generated coverage reports, nyc output and the e2e server runtime data dir
are gitignored rather than committed.
59 lines
2.3 KiB
TypeScript
59 lines
2.3 KiB
TypeScript
import { defineConfig, devices } from '@playwright/test';
|
|
import * as os from 'os';
|
|
|
|
/**
|
|
* Testcontainers e2e config (Option D): every worker boots its own isolated
|
|
* DB + OxiCloud app container (Svelte SPA baked in) via the worker-scoped
|
|
* `stack` fixture in `scenarios/helpers.ts`.
|
|
*
|
|
* Differences from `playwright.config.ts` (legacy single-server flow):
|
|
* - No `webServer` — the app is a container started per worker.
|
|
* - No `globalSetup` — each worker seeds its own admin in the fixture.
|
|
* - No `use.baseURL` — the fixture supplies a per-worker random port.
|
|
* - `fullyParallel` + N workers — stacks are fully isolated, so parallel.
|
|
*
|
|
* Run with: OXICLOUD_E2E_CONTAINERS=1 playwright test -c playwright.containers.config.ts
|
|
* Set $OXICLOUD_IMAGE to a prebuilt tag to skip the per-run Dockerfile build.
|
|
*/
|
|
export default defineConfig({
|
|
testDir: './scenarios',
|
|
// The recorder harnesses in scenarios/codegen/ call page.pause() and are run
|
|
// only via `just front-codegen` (playwright.codegen.config.ts) — never as
|
|
// part of the e2e suite.
|
|
testIgnore: ['**/codegen/**'],
|
|
fullyParallel: true,
|
|
forbidOnly: !!process.env.CI,
|
|
retries: 0,
|
|
// One DB + one app container per worker — cap so we don't exhaust Docker.
|
|
workers: process.env.CI ? 2 : Math.max(1, Math.floor(os.cpus().length / 4)),
|
|
// Real container app is slower than a local cargo process; give actions room.
|
|
timeout: 60_000,
|
|
reporter: process.env.CI ? [['line'], ['github'], ['html']] : [['list'], ['html']],
|
|
|
|
use: {
|
|
trace: 'on-first-retry',
|
|
headless: true,
|
|
screenshot: 'only-on-failure',
|
|
// Tile/file rows expose a `data-testid` of the item name (kept only in e2e
|
|
// builds via VITE_E2E); makes getByTestId + codegen prefer stable selectors.
|
|
testIdAttribute: 'data-testid',
|
|
// On NixOS (and other distros where Playwright's downloaded chromium can't
|
|
// run due to the generic dynamic linker), point at a system/Nix chromium
|
|
// via PW_CHROMIUM_PATH. Unset → use Playwright's bundled browser (CI).
|
|
launchOptions: process.env.PW_CHROMIUM_PATH
|
|
? { executablePath: process.env.PW_CHROMIUM_PATH }
|
|
: {},
|
|
},
|
|
|
|
expect: {
|
|
toHaveScreenshot: { maxDiffPixelRatio: 0.01 },
|
|
},
|
|
|
|
projects: [
|
|
{
|
|
name: 'chromium',
|
|
use: { ...devices['Desktop Chrome'] },
|
|
},
|
|
],
|
|
});
|