jerry/buzz
1
0
Fork 0
mirror of https://github.com/block/buzz.git synced 2026-10-29 21:41:33 +00:00
Code Issues Packages Projects Releases Wiki Activity

test(desktop): drop the import left behind by the tracer reduction

Browse Source 
Signed-off-by: Max Lampert <maxwell@squareup.com>
This commit is contained in:
Max Lampert
2026-08-26 20:05:37 -07:00
parent c299a22ea7
commit be26be0181
1 changed files with 4 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
desktop/src/features/channels/useChannelSwitchTraceMarks.test.mjs
View File

@@ -10,14 +10,13 @@ import {
CHANNEL_SWITCH_MEASURE,
beginChannelSwitchTrace,
resetChannelSwitchTrace,
settleChannelSwitchTrace,
} from "../../shared/lib/channelSwitchPerf.ts";
import { useChannelSwitchTraceMarks } from "./useChannelSwitchTraceMarks.ts";
// These tests run the hook under the real react-dom development build, whose
// StrictMode replays every effect (setup → cleanup → setup) on mount — the
// exact dev-runtime lifecycle that used to abandon a just-opened trace and
// break the Performance-panel workflow.
// StrictMode replays every effect (setup → cleanup → setup) on mount. The
// Performance-panel workflow runs on that build, so a trace opened just
// before mount has to survive the replay.
const originalDocument = globalThis.document;
const originalWindow = globalThis.window;
@@ -101,7 +100,7 @@ it("a trace survives StrictMode's effect replay and still settles", async () =>
dom.window.close();
});
it("an A→B switch's deferred abandon of A never kills B's trace", async () => {
it("an A→B switch records B, never the superseded A", async () => {
const { dom, flushFrames } = setupDom();
performance.clearMeasures?.(CHANNEL_SWITCH_MEASURE);
beginChannelSwitchTrace("chan-a");