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.
31 lines
1.1 KiB
TypeScript
31 lines
1.1 KiB
TypeScript
import { test, expect } from './coverage-helpers';
|
|
import { apiLogin } from '../scenarios/helpers';
|
|
|
|
/**
|
|
* Device-pairing route — submit a (bogus) device code to exercise the lookup
|
|
* path and its error/retry handling. Standalone page (no app shell).
|
|
*/
|
|
test.beforeEach(async ({ page }) => {
|
|
await apiLogin(page);
|
|
});
|
|
|
|
test('submitting an unknown device code shows the retry path', async ({ page }) => {
|
|
await page.goto('/device');
|
|
await expect(page.getByTestId('device-code-form')).toBeVisible({ timeout: 15_000 });
|
|
|
|
await page.getByTestId('device-code-input').fill('ZZZZ-ZZZZ');
|
|
await page.getByTestId('device-continue-btn').click();
|
|
|
|
// An unknown code returns to a retry/error state (or stays on the form).
|
|
await expect(
|
|
page.getByTestId('device-retry-btn').or(page.getByTestId('device-code-form')),
|
|
).toBeVisible({ timeout: 15_000 });
|
|
|
|
// If a retry button appeared, use it to return to the code form.
|
|
const retry = page.getByTestId('device-retry-btn');
|
|
if (await retry.isVisible().catch(() => false)) {
|
|
await retry.click();
|
|
await expect(page.getByTestId('device-code-form')).toBeVisible({ timeout: 15_000 });
|
|
}
|
|
});
|