From 86d9818abfc160dac031bb292abe28d6f28fc624 Mon Sep 17 00:00:00 2001 From: Adam Soltys Date: Wed, 7 Oct 2026 12:02:51 -0700 Subject: Browser tests: public relays answered in the page, never reached A suite run let ~90 throwaway test wallets subscribe and publish on public relays from one home address, and nos.lol and relay.damus.io banned it. tools/puppeteer.js wraps puppeteer-core: every socket to a non-local host gets an in-page stand-in relay (EVENT -> OK, REQ -> EOSE). Tests that read real content launch with { relays: 'read' } (real reads, publishes answered in place); feed-live, chat-layout and cordn-ui launch with { relays: 'live' }. LIVE_RELAYS=read|1|host,... overrides per run. profile-key-qr: measure the QR again if a repaint swapped it out. Co-Authored-By: Claude Opus 5.5 --- tools/feed-streaming-test.js | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'tools/feed-streaming-test.js') diff --git a/tools/feed-streaming-test.js b/tools/feed-streaming-test.js index 3070771..c69b1eb 100644 --- a/tools/feed-streaming-test.js +++ b/tools/feed-streaming-test.js @@ -1,7 +1,7 @@ // Signed relay events must surface before EOSE and independently of slow media. // Run: bun tools/feed-streaming-test.js import assert from 'node:assert/strict'; -import puppeteer from 'puppeteer-core'; +import puppeteer from './puppeteer.js'; import { finalizeEvent, generateSecretKey, getPublicKey } from 'nostr-tools/pure'; import { buildVerifyWorker } from '../build.js'; const sk = generateSecretKey(), author = getPublicKey(sk), now = Math.floor(Date.now() / 1000); -- cgit v1.2.3