Repository navigation
test(chat-input): run focus and caret frames in act, await queued write - #27765
Conversation
Make website/src/test/ChatInputCoverage.test.tsx stop emitting React act() warnings, and drop its row from website/integration/act-warning-baseline.json so the guard in website/integration/setup.ts checks it.
First Principles Review (Opus 5.5) — ⏭️ skippedRevision |
UX Review (Opus 5.5) — ✅ PASSUX-level review of UX-Verdict: PASS Nothing to check. The diff only changes one test file and a test baseline, so nothing reaches the screen and no screenshot is needed. [UX-REVIEWED] 545b0aa Description read[DESCRIPTION-READ] ad0ebee5f70cdcb12bd30b106bf8539caa773a40f8a06c3ec8ff53861de64e7e That sha256 names everything this verdict read: the PR description, plus the 3 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
Design Review (Opus 5.5) — ✅ PASSDesign-level review of Design-Verdict: PASS Test-only change. It removes one baseline row and swaps a timed sleep for a wait on a real signal, so there are no design-level concerns. [DESIGN-REVIEWED] 545b0aa Description read[DESCRIPTION-READ] 218e56b718e761535c8a98544c77a2ff6e5b7402d8d0a47ae1b12af8d29f85d3 That sha256 names everything this verdict read: the PR description, plus the 1 evidence file(s) the workflow collected from it and handed this review. It covers that evidence because the media strip replaces every attachment URL with the same placeholder, so an edit swapping one attachment for another would leave the description's captured text identical while what this review judged changed. Recompute it with |
Opus 5.5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
KiroCrewCaptain
left a comment
There was a problem hiding this comment.
Tier 1 auto-approve: test (2 files). Criteria: no conflict, no requested changes, security path denylist clean, design-doc gate clean, security checklist all-NO, no reviewer-lane findings, readiness signal fresh for this head SHA, declared category matches the diff. Category: test-only: runs focus and caret frames in act and waits for the queued write, and drops the file from the act-warning baseline.
Problem / Motivation
Goal:
website/src/test/ChatInputCoverage.test.tsxstops emitting React act() warnings, so its row leaveswebsite/integration/act-warning-baseline.jsonand the guard inwebsite/integration/setup.tschecks it like any file outside the list.Before this change, a run of the file emitted 36 act() warnings (late state updates in
ChatInput): a state update landed after the test's last barrier. Because the file is on the baseline, the guard kept those warnings out of the log.Why it matters
website/docs/testing.md(Rules every test keeps) treats an act() warning as a finding: the update lands after the assertions, so whether the test sees it depends on timing. The baseline is shrink-only, and each file that leaves it is held to the rule from then on.Not a goal
What changed (motivation → approach → change)
The tests now wait for the state the late update produces before they finish, so the update lands inside the test's barrier.
website/src/test/ChatInputCoverage.test.tsx:import { act, screen, fireEvent, waitFor, within } from '@testing-library/react'website/src/test/ChatInputCoverage.test.tsx:await new Promise<void>(resolve => { requestAnimationFrame(() => resolve()) })website/src/test/ChatInputCoverage.test.tsx:await waitFor(() => expect(queryClient.isMutating()).toBe(2), namedCeiling('AUTOCOMPACT_SECOND_WRITE_QUEUED', 1500))website/integration/act-warning-baseline.json: removedsrc/test/ChatInputCoverage.test.tsx.Backwards compatibility
Compatible: test-only change.
Removes nothing: a baseline row is a tolerance the guard stops needing, not a capability.
Tests
KIROCREW_ACT_STRICT=1 npx vitest run src/test/ChatInputCoverage.test.tsxfromwebsite/: 20 of 77 tests fail on act() warnings.integration/setup.refactor.determinism.test.tspasses (the baseline stays sorted, unique and existing);npx eslintis clean on the file.Manual verification
N/A: test-only change; the strict runs above are the check.
Screenshots / video
Why no screenshot: nothing renders; this change touches one test file and a test baseline only.
No issue exists; burn-down of the act() warning baseline that #17673 introduced.