ZDDC
0c48a583ad
The polyfill in shared/zddc-source.js is the seam between every tool
and zddc-server's HTTP API; if it drifts, every HTTP-mode tool breaks
together. Until now it had no direct test coverage — it was only
exercised through tool-level specs that load via file://.
Seven tests cover the documented surface:
- Public API shape on window.zddc.source matches the contract
- detectServerRoot() returns {handle:null, status:0} on file://
(the negative path most tools branch on)
- httpListing() parses arrays, propagates 403 with err.status
- HttpDirectoryHandle.values() yields HttpFile/DirectoryHandles
with correct kind+name from server-side is_dir/name fields
- HttpFileHandle.getFile() fetches, surfaces ETag, sets size
- moveFile() POSTs with X-ZDDC-Op: move, X-ZDDC-Destination, and
optional If-Match — and returns the server's new ETag
Tests host inside classifier/dist/classifier.html (the smallest tool
that bundles zddc-source.js — browse, archive, landing, form do not),
mock fetch via page.route(), and add CORS + preflight responses so
file://-origin pages can read response headers like ETag.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
105 lines
2.8 KiB
JavaScript
105 lines
2.8 KiB
JavaScript
import { defineConfig } from '@playwright/test';
|
|
|
|
export default defineConfig({
|
|
testDir: './tests',
|
|
// tokens.spec.js builds the Go binary on first run via podman + waits
|
|
// for the spawned master to listen — both can take longer than the
|
|
// default 30s on a cold cache. Other specs are file:// driven and
|
|
// unaffected by this bump.
|
|
timeout: 60000,
|
|
retries: 0,
|
|
reporter: [['line'], ['html', { open: 'never' }]],
|
|
|
|
use: {
|
|
// Chromium only -- File System Access API requires it,
|
|
// and the ZDDC tools target "any modern Chromium-based browser"
|
|
browserName: 'chromium',
|
|
screenshot: 'only-on-failure',
|
|
trace: 'retain-on-failure',
|
|
},
|
|
|
|
projects: [
|
|
{
|
|
name: 'archive',
|
|
testMatch: 'archive.spec.js',
|
|
},
|
|
{
|
|
name: 'archive-cascade',
|
|
testMatch: 'archive-cascade.spec.js',
|
|
},
|
|
{
|
|
name: 'landing',
|
|
testMatch: 'landing.spec.js',
|
|
},
|
|
{
|
|
name: 'transmittal',
|
|
testMatch: 'transmittal.spec.js',
|
|
},
|
|
{
|
|
name: 'transmittal-init',
|
|
testMatch: 'transmittal-init-check.spec.js',
|
|
},
|
|
{
|
|
name: 'transmittal-drag-drop',
|
|
testMatch: 'transmittal-drag-drop.spec.js',
|
|
},
|
|
{
|
|
name: 'classifier',
|
|
testMatch: 'classifier.spec.js',
|
|
},
|
|
{
|
|
name: 'mdedit',
|
|
testMatch: 'mdedit.spec.js',
|
|
},
|
|
{
|
|
name: 'browse',
|
|
testMatch: 'browse.spec.js',
|
|
},
|
|
{
|
|
name: 'zddc-source',
|
|
testMatch: 'zddc-source.spec.js',
|
|
},
|
|
{
|
|
name: 'zddc',
|
|
testMatch: 'zddc.spec.js',
|
|
},
|
|
{
|
|
name: 'form-safety',
|
|
testMatch: 'form-safety.spec.js',
|
|
},
|
|
{
|
|
name: 'tables',
|
|
testMatch: 'tables.spec.js',
|
|
},
|
|
{
|
|
name: 'zddc-filter',
|
|
testMatch: 'zddc-filter.spec.js',
|
|
},
|
|
{
|
|
name: 'build-label',
|
|
testMatch: 'build-label.spec.js',
|
|
},
|
|
{
|
|
name: 'schema',
|
|
testMatch: 'schema.spec.js',
|
|
},
|
|
{
|
|
// Server-backed: starts a real zddc-server master via
|
|
// tests/lib/server.mjs (which builds the binary on first run
|
|
// through the canonical podman/zddc-go:1.24 invocation), drives
|
|
// Chromium against http://127.0.0.1:<port>/.tokens, exercises
|
|
// create/list/revoke + bearer round-trip + cross-user 404 +
|
|
// XSS-guard. The binary build is cached at zddc/dist/zddc-server-
|
|
// test and invalidated by a hash of cmd/+internal/+go.{mod,sum}
|
|
// so a second run only takes the master-startup time (~1s).
|
|
// First run takes ~30s for the build.
|
|
//
|
|
// The lifecycle is per-spec via beforeAll/afterAll — Playwright's
|
|
// top-level webServer hook would fire for every project, including
|
|
// the file://-driven tool tests that don't need the server.
|
|
name: 'tokens',
|
|
testMatch: 'tokens.spec.js',
|
|
},
|
|
],
|
|
});
|
|
|