codingetandClaude
c89c478286
Uses Playwright as a library within node:test (not @playwright/test) to keep the same runner and script conventions. Browser test files use the *.browser.ts extension so the existing src/**/*.test.ts glob picks up zero browser tests, leaving the regular test suite unaffected. Key pieces: - .npmrc: PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD=1 prevents binary downloads on npm ci; browsers are installed explicitly in CI via playwright install - @webnet/browser-test-utils: new private package exporting forBrowsers() (iterates chromium + firefox, handles browser lifecycle within node:test suite/before/after) and a serveDirectory() helper (minimal http.createServer that serves a built dist/ or out/ directory so the browser can fetch ES modules via dynamic import()) - test:browser / test:browser:coverage scripts added to transport, vfs, tsconnect following the same c8 + lcov pattern as test:coverage - turbo.json: test:browser and test:browser:coverage tasks depend on build + ^build (dist/ must exist before the browser can import from it) - .gitea/workflows/test-browser.yml: CI pipeline that installs browsers with --with-deps then runs npm run test:browser Integration tests: - DataChannelTransport: real RTCPeerConnection loopback (both peers in one page context), exercises send/receive and close propagation - FsaVFS: OPFS round-trip (writeFile/readFile), stat, readdir, delete - IndexedDBState: multi-instance persistence (write via instance 1, open fresh instance 2 and verify IDB round-trip), empty-DB initialisation - FsaFileOps: write/read/stat/remove cycle and rename/listFiles over OPFS Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2 lines
35 B
Plaintext
2 lines
35 B
Plaintext
PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD=1
|