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.
50 lines
1.8 KiB
TypeScript
50 lines
1.8 KiB
TypeScript
import { test, expect } from './coverage-helpers';
|
|
import { apiLogin, apiCreateFolder } from '../scenarios/helpers';
|
|
|
|
/**
|
|
* Error-path coverage — drive the catch/error branches that the happy-path
|
|
* specs don't reach: a duplicate-folder 409 and an over-cap (413) upload.
|
|
*/
|
|
test.beforeEach(async ({ page }) => {
|
|
await apiLogin(page);
|
|
});
|
|
|
|
function uniq(p: string): string {
|
|
return `${p}-${Date.now()}-${Math.floor(Math.random() * 1e6)}`;
|
|
}
|
|
|
|
test('creating a duplicate folder surfaces an error toast', async ({ page }) => {
|
|
const parent = await apiCreateFolder(page, uniq('DupHost'));
|
|
const name = uniq('Dup');
|
|
await apiCreateFolder(page, name, parent.id); // pre-create the clashing name
|
|
|
|
await page.goto(`/files/${parent.id}`);
|
|
await expect(page.getByTestId(name)).toBeVisible({ timeout: 15_000 });
|
|
|
|
await page.getByTestId('files-new-folder-btn').click();
|
|
await page.getByTestId('dialog-host-prompt-input').fill(name);
|
|
await page.getByTestId('dialog-host-submit-btn').click();
|
|
|
|
// The 409 is caught and raised as a toast.
|
|
await expect(page.locator('[data-testid^="toaster-toast-"]').first()).toBeVisible({
|
|
timeout: 15_000,
|
|
});
|
|
});
|
|
|
|
test('an over-cap upload is handled without crashing', async ({ page }) => {
|
|
const folder = await apiCreateFolder(page, uniq('BigUp'));
|
|
await page.goto(`/files/${folder.id}`);
|
|
await expect(page.getByTestId('files-upload-file-input')).toBeAttached({ timeout: 15_000 });
|
|
|
|
// 5 MiB exceeds the 4 MiB test cap → the upload fails (413) and is caught.
|
|
const big = Buffer.alloc(5 * 1024 * 1024, 65);
|
|
await page.getByTestId('files-upload-file-input').setInputFiles({
|
|
name: 'big.bin',
|
|
mimeType: 'application/octet-stream',
|
|
buffer: big,
|
|
});
|
|
await page.waitForTimeout(2_000);
|
|
// The page stays usable (the error path ran).
|
|
await expect(page.getByTestId('files-upload-btn')).toBeVisible();
|
|
});
|