You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test: migrate the deferred small suites to the shared mock factories
Follow-up to the §4.4.2 fixture extraction: migrate the five small
deferred suites onto test/helpers/cli-test-fixtures.ts where the mock
shapes match, with zero test-semantics change (274/274 across the five
migrated suites plus the five canary suites already migrated, identical
counts and failure lists before and after via stash comparison).
- index-retry: the storage vi.mock now delegates to storageModuleMock
with the suite's bespoke stub overrides kept inline (no test asserts
on them). Left inline: accounts.js/config.js (divergent shapes,
deliberately not force-unified), fetch-helpers, request-transformer,
wait-utils, recovery, update-notice and the plugin tool shim (no
helper counterparts).
- accounts-edge: storage mocks unified via pickMocks(createStorageMocks)
+ storageModuleMock; codex-cli writer via createCodexCliWriterMocks +
codexCliWriterModuleMock. Left inline: codex-cli state (this suite
needs the actual module spread so isCodexCliSyncEnabled and friends
stay real, diverging from the helper's full-replacement shape),
codex-cli sync and rotation (no helper counterparts), and the local
storage fixture builders (no activeIndexByFamily plus past timestamps,
deliberately different from accountStorageV3Fixture).
- accounts-load-from-disk: storage module shape delegates to
storageModuleMock; codex-cli state/writer shapes delegate to the
shared factories created inside the vi.mock factories. The vi.fn
instances stay in vi.hoisted because the suite imports the accounts
module statically, so the hoisted factories run before module-level
consts would initialize. Left inline: codex-cli sync (no helper).
- issue-474-pin-end-to-end: storage module shape delegates to
storageModuleMock; instances stay in vi.hoisted for the same
static-import reason. The fully typed createStorage builder stays
local (the minimal as-never fixture builder would weaken its typing).
- dashboard-display-panel: select mock unified via createUiPromptMocks +
uiSelectModuleMock; the panel module is now imported lazily inside the
tests (the canonical fixture pattern) so the module-level mock group
stays hoisting-safe. Left inline: ui/runtime getUiRuntimeOptions (no
helper counterpart).
https://claude.ai/code/session_01XNtnkLbBiXZxfQQYLMpucB
0 commit comments