Run oracles in a real browser (Vitest browser mode)

未關閉
#49 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
18/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
javascript, playwright
領域
testing

研究方向

Start with the imports in oracleProperty (node:async_hooks, node:fs, node:util) and with useOracleClock, then read oracle-gaps/capture-setup.mjs where ORACLE_GAPS_STATE is read through readFileSync. Running a test file under Vitest browser mode should show these failures, such as AsyncLocalStorage is not a constructor. Done means a browser-safe entry imports and runs in browser mode, and the gap check either runs there or is documented as unsupported.

由索引模型根據 Issue 內容生成。

描述

Problem

An oracle for DOM code must run in jsdom today, so its driver supplies the
browser facts that jsdom lacks: layout, scroll positions, the targets where
scroll events fire, ResizeObserver notifications, and computed styles. When
the driver's stand-in and production rest on the same wrong belief about the
browser, the oracle passes, and only a human or a real browser finds the bug.

We hit this three times in one pull request (react-headroom):

  • The stand-in notified a ResizeObserver on any size change. Chrome notifies
    a content-box observer only when the content box changes, so a header that
    changes only its padding kept a stale height.
  • The stand-in decided that a body with overflow-y: auto scrolls itself.
    With html { overflow-y: scroll } body { overflow-x: hidden }, Chrome
    computes the body's overflow-y as auto, but the body grows with its
    content and the page scrolls.
  • The stand-in gave a body the viewport's height. In Chrome, a body that does
    not scroll itself grows with the page.

We checked each fact by hand in headless Chrome. An oracle that runs in
Chrome would have checked them on every run.

What stops it at 4749f61

  1. oracleProperty imports node:async_hooks (AsyncLocalStorage for probe
    windows), node:fs (appendFileSync) and node:util (inspect,
    isDeepStrictEqual, types). In Vitest browser mode the test file fails
    to import: AsyncLocalStorage is not a constructor.
  2. The gap check's setup file (oracle-gaps/capture-setup.mjs) reads its run
    state from process.env.ORACLE_GAPS_STATE with readFileSync. In browser
    mode, setup files run in the page.

Request

  • Let oracleProperty and useOracleClock run in Vitest browser mode, for
    example with a browser-safe entry that replaces AsyncLocalStorage, fs
    and util with browser equivalents or leaves those features out.
  • Let oracle-gaps run an oracle in browser mode, or document that it cannot,
    and recommend a pattern: for example, an oracle that runs in Chrome for its
    laws, and the same oracle in jsdom for the gap check.

Workaround we considered

Keep the oracle in Node and drive a Chrome page through Playwright: the
driver sends each history to the page, which runs it against a bundle of
production and returns the observations. This needs a page bundle, a
page-side clock in place of useOracleClock, and two copies of the driver
environment. The gap check still cannot mutate the code in the page.

主要語言
JavaScript
星號
5
分支
1
平均合併
8 小時 31 分鐘
30 天內合併 PR
60

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

TanStack/oracles 的其他 Issue

查看 TanStack/oracles 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。