Skip to content

Commit 7e319b0

Browse files
matt2eclaude
andcommitted
test(workflows): drop stale timing figures from the change-event comment
The interaction count and CI duration already live in the previous commit message and would go stale with the next test or runner change; keep only the durable rationale. Co-Authored-By: Claude Fable 5.1 <[email protected]> Signed-off-by: Matt Toohey <[email protected]>
1 parent a85736b commit 7e319b0

1 file changed

Lines changed: 2 additions & 3 deletions

File tree

‎src/bundled/workflows/WorkflowsPage.test.tsx‎

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -362,9 +362,8 @@ it("discards form-only state on same-revision review and re-arms the next draft'
362362
);
363363
await user.click(screen.getByRole("combobox", { name: "Add condition" }));
364364
await user.click(await screen.findByRole("option", { name: "Author" }));
365-
// Set the value in one change event: two draft cycles already cost ~75
366-
// jsdom interactions and ran ~4.6 s on CI against the 5 s default timeout,
367-
// and per-keystroke entry is pinned by the `guards canonical…` siblings.
365+
// One change event keeps this two-cycle test inside the default timeout;
366+
// keystroke entry is pinned by the `guards canonical…` siblings.
368367
fireEvent.change(screen.getByRole("textbox", { name: "Value" }), {
369368
target: { value },
370369
});

0 commit comments

Comments
 (0)