Repository navigation
Add a DOM test environment (happy-dom) for interaction-class web tests #207
Description
From the #206 hotfix: the repo has no DOM test env (no jsdom/happy-dom, no @testing-library/react), so render-time invariants are testable via renderToStaticMarkup but genuine interaction bugs (menu typeahead stealing keystrokes, focus traps, portals) are only catchable in live browser passes. Three of the messenger pivot's live-verification findings were in this class. Proposal: add happy-dom + a minimal interaction-test harness for apps/web, then backfill tests for GroupAssignMenu typeahead, overlay Escape/focus-return, and the identity-sheet dirty-draft flows.
Activity
shuv1337 commentedon Aug 25, 2026
Another case for the DOM env: M8's auto-start guard (#219) could only be tested as a pure predicate — a real mount-with-spy for the effect (incl. StrictMode double-invoke) needs jsdom/happy-dom. Third accumulated instance.