Skip to content

fix(smoke): pause the conversation clock at a future instant #8336

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
LIHUA919 wants to merge 3 commits into
base: main
Choose a base branch
from
Open

fix(smoke): pause the conversation clock at a future instant #8336

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2f9788a
fix(smoke): pause the conversation clock at a future instant
LIHUA919 Nov 8, 2026
c0f701f
fix(smoke): freeze the conversation clock from a controlled origin
LIHUA919 Nov 8, 2026
985e6c4
fix(smoke): pin the conversation Date before advancing its timers
LIHUA919 Nov 8, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 11 additions & 4 deletions examples/personal-workspace-browser/conversation-activity.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,11 +46,17 @@ export const conversationActivityScenario = {
const turn = await send("请检查当前任务状态，并说明下一步。");
await page.getByRole("status", {name: "正在回复", exact: true}).waitFor();
const pending = page.locator(".personal-message").filter({ has: page.getByRole("button", { name: "中断本轮", exact: true }) });
await page.clock.install();
// Pin Date to a fixed instant first, then advance timers without a
// running wall clock, and pause. Any finite future pause target leaves a
// scheduling race — the clock keeps running between commands, so a
// delayed pause can again aim into the past. With the Date pinned the
// comparisons use one deterministic instant regardless of command
// latency; the system time is restored before the scenario continues.
const clockStart = Date.UTC(2030, 0, 1);
await page.clock.install({time: clockStart});
await page.clock.setFixedTime(clockStart);
await page.clock.fastForward(25000);
// Compare the same instant across views; clock.install alone keeps
// advancing and can cross a second boundary while navigation completes.
await page.clock.pauseAt(await page.evaluate(() => Date.now()));
await page.clock.pauseAt(clockStart);
await pending.locator(".personal-message-quiet").waitFor();
const elapsedBefore = await pending.locator(".personal-message-elapsed").textContent();
await page.getByRole("navigation", { name: "管家视图" }).getByRole("button", { name: "总览", exact: true }).click();
Expand All @@ -60,6 +66,7 @@ export const conversationActivityScenario = {
assert.equal(await page.getByRole("status", {name: "正在回复", exact: true}).count(), 1, "Activity stays on the Chat entry");
await page.getByRole("navigation", { name: "管家视图" }).getByRole("button", { name: "对话", exact: true }).click();
assert.equal(await pending.locator(".personal-message-elapsed").textContent(), elapsedBefore);
await page.clock.setSystemTime(Date.now());
await page.clock.resume();
const adjustments = [];
let legacyMigrationAttempts = 0;
Expand Down
Loading