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.
62 lines
1.5 KiB
Plaintext
62 lines
1.5 KiB
Plaintext
# Build artifacts
|
|
target/
|
|
|
|
# Dependency / tooling directories — NEVER needed in the build context.
|
|
# These dominate the context by file count (frontend/node_modules alone is
|
|
# ~11k tiny files); shipping them makes the Testcontainers build (which tars
|
|
# the context in pure JS, matching every path against this file) crawl and can
|
|
# blow past the e2e stack-setup timeout. The frontend stage runs its own
|
|
# `npm ci`, so host node_modules is both unused and would clobber it via the
|
|
# later `COPY frontend/ ./`. .devenv/.direnv are the Nix dev shell.
|
|
**/node_modules/
|
|
.devenv/
|
|
.direnv/
|
|
|
|
# Generated SPA output — the image builds the SPA fresh in the `frontend` stage
|
|
# and pulls it via `COPY --from=frontend /static-dist`; the host copy is unused.
|
|
static-dist/
|
|
frontend/build/
|
|
dist/
|
|
|
|
# Standalone wasm sub-workspaces — not a path dependency of the server crate
|
|
# (see Cargo.toml), so `cargo build` in the image never reads them.
|
|
wasm/
|
|
|
|
# Git
|
|
.git/
|
|
.gitignore
|
|
|
|
# IDE
|
|
.vscode/
|
|
.idea/
|
|
*.swp
|
|
*.swo
|
|
|
|
# Docker
|
|
Dockerfile
|
|
Dockerfile.rootless
|
|
docker-compose.yml
|
|
rootless-compose.yml
|
|
|
|
# Runtime data (mapped via volumes)
|
|
storage/
|
|
|
|
# Documentation
|
|
docs/
|
|
*.md
|
|
LICENSE
|
|
CODEOWNERS
|
|
|
|
# Project assets and tooling not needed by the build
|
|
# (the Dockerfile only COPYs src, migrations, templates, build.rs,
|
|
# Cargo.*, and entrypoint.sh; everything else is dead weight in the context)
|
|
images/
|
|
charts/
|
|
tools/
|
|
tests/
|
|
|
|
# Miscellaneous
|
|
.github/
|
|
.env
|
|
*.bak
|