Commit Graph
14 Commits
Author SHA1 Message Date
thePR0M3TH3ANandClaude Opus 4.8 1f07538c66 test(harness): extend nip07 channel-sim to all list systems
Grow the deterministic channel-simulation harness from blocks-only to a
two-session, multi-list rig so every cold-login decrypt path can be
validated locally:

- Session 1 logs in programmatically (loginWithNsec, same key the fake
  extension uses) on a HEALTHY channel and publishes the user's real
  encrypted lists via the services (block list + subscription list +
  hashtag interest) through new testHarness.seedTestLists().
- Session 2 logs in via the NIP-07 path under the target channel MODE and
  reports, per list, whether it decrypted — plus signer-ready time, the
  login REQ burst (per kind), decrypt timeouts, breaker activity, and a DM
  load probe.

testHarness: expose subscriptions + hashtag load state on getAppState().lists
and add seedTestLists() (resolves the actor from nostrClient.pubkey, which —
unlike the registry getActiveSigner() — is populated for a NIP-07 login).
Verdict is mirrored to a report file and uses process.exitCode so results
survive stdout buffering when piped/backgrounded.

Validation:
  MODE=healthy  → blocks/subscriptions/hashtags all decrypt, DMs OK.
  MODE=overload → 26 injected channel drops, ALL THREE lists still recover
                  via the transient-retry fix (db0fc079), DMs OK.
The harness exits non-zero if a list that should load doesn't, so it can
gate CI. Confirms the burst is still ~60 REQ frames at login (kind 30000
dominant) — the next target. KNOWN_BUGS #0.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
2026-06-16 09:17:47 -04:00
thePR0M3TH3ANandClaude Opus 4.8 db0fc07989 fix(nostr): retry list decrypt on transient channel failure (not give up)
Built a deterministic NIP-07 channel-simulation harness
(scripts/perf/nip07-channel-sim.mjs) that reproduces the real cold-login
failure locally with a fake extension whose message channel drops under
concurrent load (MODE=overload), recovers (MODE=slow), or stays dead. It
seeds a real encrypted block list and reports whether it decrypts.

The harness pinned the actual root cause that the relay/breaker/timeout
work hadn't fixed: when the channel briefly drops during the login burst,
the per-scheme decrypt probe (Promise.any) rejects with
"message channel closed" — and every list service SWALLOWED that and
treated it as "the user has no blocks / no subs / no hashtags", or routed
it to a give-up branch. Either way: no retry, so the list stayed empty
until a full page refresh, even though the channel recovered seconds later.

Fix: classify transient failures (channel-death messages, breaker fast-fail
code, our own decrypt-timeout) and route them to the existing keep-stale +
scheduleDecryptRetry path instead of swallowing/abandoning:
- userBlocks: re-throw a transient sub-error out of the Promise.any probe
  (was silently returning [] = "no blocks"); route it (and channel/breaker
  errors) through the retry branch.
- hashtagPreferencesService + subscriptions: broaden the retry condition
  from the timeout code only to any transient error, recursing into the
  nested Promise.any AggregateError causes.

Harness verdict (MODE=overload, 16 channel drops): block list
BLOCK LIST DECRYPTED NO -> YES after the fix; signer-ready ~1.9s.
Adds getAppState().lists observability to the test harness. Full unit
suite green. KNOWN_BUGS #0.

Co-Authored-By: Claude Opus 4.8 <[email protected]>
2026-06-15 09:58:31 -04:00
thePR0M3TH3AN 414a20c1b6 test: harden harness polling and fix dm signer key usage 2026-03-04 12:25:23 -05:00
thePR0M3TH3AN 0af7de6c07 [ui] Fix DM tab blank shell and harden profile modal tests 2026-02-22 20:14:32 -05:00
thePR0M3TH3AN 0866af2e39 test(e2e): harden modal flows and expand runtime coverage 2026-02-22 16:34:19 -05:00
thePR0M3TH3AN 6ed296f2d2 Merge branch 'unstable' into agents/daily/onboarding-audit-2026-02-22-6501903614915901077 2026-02-22 15:40:28 -05:00
google-labs-jules[bot]andPR0M3TH3AN d0f10d3ab7 test(e2e): fix video card selectors and modal wait logic
- Updated `js/testHarness.js` to read `data-video-title` attribute instead of `textContent` to avoid marquee duplication issues.
- Updated `tests/e2e/video-upload-flow.spec.ts` to query title attribute on the correct child element.
- Updated `tests/e2e/video-upload-flow.spec.ts` to use `toBeVisible()` for modal wait instead of fragile `data-open` attribute check.
- Updated `tests/e2e/video-playback-scenarios.spec.ts` to include `style.display` check for modal closing.
- Verified `feed-pagination-stress.spec.ts` passes with these fixes.

Co-authored-by: PR0M3TH3AN <[email protected]>
2026-02-22 15:48:22 +00:00
google-labs-jules[bot]andPR0M3TH3AN 2122a257c8 Fix E2E CI failures: Harden UploadModal and fix login modal waiter
Co-authored-by: PR0M3TH3AN <[email protected]>
2026-02-22 15:13:08 +00:00
google-labs-jules[bot]andPR0M3TH3AN 5c944199d9 Fix E2E test failures by enforcing relay isolation and disabling whitelist mode
Co-authored-by: PR0M3TH3AN <[email protected]>
2026-02-22 14:32:54 +00:00
google-labs-jules[bot]andPR0M3TH3AN 1e2ce6bf61 Fix E2E login flows and test harness relay isolation
Addresses failures in login-flows.spec.ts by:
1. Updating the test to correctly interact with the provider-based login modal (clicking the 'nsec' button).
2. Patching the test harness `relayManager` to prevent overwriting test relays with production defaults during login/logout cycles.
3. Hardening `uiCoordinator` to ensure visibility assertions pass reliably by enforcing `style.display` properties.
4. Explicitly initializing test relays in `bitvidTestFixture` to guarantee environment isolation.

Co-authored-by: PR0M3TH3AN <[email protected]>
2026-02-22 13:48:19 +00:00
google-labs-jules[bot]andPR0M3TH3AN a10899dacc Fix: E2E test robustness (feed visibility, login state)
- Add `s` tag to seeded video events in `bitvidTestFixture.ts` to pass schema validation and appear in feeds.
- Update `js/testHarness.js` `loginWithNsec` to call `app.authService.login()`, ensuring UI state reflects login.
- Update `js/testHarness.js` `logout` to be async and use `app.requestLogout()`.
- Fix TypeScript error in `tests/e2e/dm-scenarios.spec.ts`.

Co-authored-by: PR0M3TH3AN <[email protected]>
2026-02-22 04:08:13 +00:00
thePR0M3TH3AN 0cf1dc0f55 improved playright integration 2026-02-21 20:45:47 -05:00
google-labs-jules[bot]andPR0M3TH3AN 066355e47e [constants] extract STANDARD_TIMEOUT_MS (10000) -> js/constants.js
Refactors duplicated `10000` ms numeric literals to use the canonical `STANDARD_TIMEOUT_MS` constant.

Affects:
- `js/testHarness.js`
- `js/nostr/relayBatchFetcher.js`
- `js/nostr/client.js`

Verification:
- `npm run lint` passed.
- `npm run test:unit` passed.

Co-authored-by: PR0M3TH3AN <[email protected]>
2026-02-16 04:55:18 +00:00
Claude d0a6c9622b feat: add Playwright agent testability infrastructure
Add test harness (window.__bitvidTest__), data-testid attributes, relay
override support, and Playwright fixtures so agents can programmatically
login, seed relay data, and inspect app state during E2E testing.

- js/testHarness.js: exposes loginWithNsec, getAppState, relay overrides
- data-testid attrs on login/upload/video modals, header buttons, feed
- simple-relay.mjs: HTTP seeding API (POST /seed, GET /events, /health)
- bitvidTestFixture.ts: reusable Playwright fixture with mock relay
- agent-testability.spec.ts: E2E tests validating the infrastructure

https://claude.ai/code/session_01XnrszNmdqrAGd8g8qhAn4G
2026-02-10 05:09:46 +00:00