UX testing coverage

[samanthamsong]

Epic: «Chat & everyday UX feel great» (#839)
Backlog Doc ID: #36 · Priority: P2 · Area: chat & ux

Description
Expand automated UX test coverage.

Definition of done
Core UX flows are covered by automated tests.

Part of the «Chat & everyday UX feel great» tracking issue (#839).

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 26, 2026, 2:42 PM ET / 18:42 UTC.

Summary
This should stay open: current main has useful UX-adjacent unit, functional UI, and E2E coverage, but the requested broader coverage for core chat and everyday UX flows is not fully implemented or scoped tightly enough to close.

Reproducibility: not applicable. this is a test-coverage planning item, not a reproducible product bug. Current main shows existing UX-adjacent tests, but the issue does not define a failing scenario to reproduce.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Add expected vs actual behavior.

Next step
Maintainers should define the concrete UX flows and acceptable harnesses before implementation; this is not narrow enough for an autonomous repair PR yet.

Review details

Best possible solution:

Keep this as a planning child under the chat and everyday UX epic, define the specific flows and harness expectations, then split or implement focused test PRs in the tray, FunctionalUI, and E2E test projects.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this is a test-coverage planning item, not a reproducible product bug. Current main shows existing UX-adjacent tests, but the issue does not define a failing scenario to reproduce.

Is this the best way to solve the issue?

Unclear: expanding automated coverage is the right direction, but this issue is too broad for a single autonomous implementation without a maintainer-defined list of core flows and expected harnesses.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• The issue is intentionally broad; without a maintainer-owned list of core UX flows, an automated PR could add arbitrary tests while still missing the intended coverage boundary.

Codex review notes: model internal, reasoning high; reviewed against 1c377cb64b65.

Label changes

Label changes:

• add P2: This is a normal-priority automated coverage improvement for core chat and everyday UX flows, not an urgent runtime regression.
• add impact:other: The issue affects maintainer confidence in core UX behavior through automated coverage, which is meaningful but outside the specific impact taxonomy.
• add issue-rating: 🌊 off-meta tidepool: Current issue advisory state selects this label.
• add clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.
• add clawsweeper:needs-maintainer-review: Current issue advisory state selects this label.
• add clawsweeper:needs-product-decision: Current issue advisory state selects this label.

Label justifications:

• P2: This is a normal-priority automated coverage improvement for core chat and everyday UX flows, not an urgent runtime regression.
• impact:other: The issue affects maintainer confidence in core UX behavior through automated coverage, which is meaningful but outside the specific impact taxonomy.

Evidence reviewed

Acceptance criteria:

• ./build.ps1
• dotnet test ./tests/OpenClaw.Shared.Tests/OpenClaw.Shared.Tests.csproj --no-restore
• dotnet test ./tests/OpenClaw.Tray.Tests/OpenClaw.Tray.Tests.csproj --no-restore

What I checked:

• Issue scope: The issue asks to expand automated UX test coverage until core UX flows are covered, and it is linked to the open chat and everyday UX tracking issue at 🦞 Tracking: Chat & everyday UX feel great #839.
• Existing coverage inventory: The test coverage document lists substantial existing coverage, including tray UI/state, chat timeline/markdown handling, A2UI/native WinUI rendering, FunctionalUI smoke tests, and known manual-visual gaps. (docs/TEST_COVERAGE.md:20, 1c377cb64b65)
• Current tray tests link chat UX logic: The tray test project links chat timeline, chat surface, markdown, data provider, notification, and ChatPage panel-state helpers, showing partial automated coverage of UX-adjacent logic rather than complete core-flow coverage. (tests/OpenClaw.Tray.Tests/OpenClaw.Tray.Tests.csproj:20, 1c377cb64b65)
• Focused ChatPage panel coverage exists: ChatPagePanelStatesTests contains regression coverage for WebView, waiting, retry, loading, error, and placeholder panel transitions, which is useful but narrower than the requested core UX flow coverage. (tests/OpenClaw.Tray.Tests/Pages/ChatPagePanelStatesTests.cs:19, 1c377cb64b65)
• CI E2E coverage exists but is not UX-complete: CI runs an E2E setup-connect shard with setup, MXC, revocation, and network recovery tests, but that does not cover the full chat and everyday UX flow list from the tracking issue. (.github/workflows/ci.yml:292, 1c377cb64b65)
• VISION.md check: No VISION.md was present in the checkout, so there was no repository vision document available to narrow or reject this planning item. (1c377cb64b65)

Likely related people:

• RBrid: Recent merged chat work added inline exec approval flow and touched chat timeline, OpenClawChatDataProvider tests, notifications, and chat page behavior. (role: recent chat UX and test-area contributor; confidence: high; commits: 4e7982bafb86; files: src/OpenClaw.Chat/ChatTimelineReducer.cs, src/OpenClaw.Tray.WinUI/Chat/OpenClawChatDataProvider.cs, src/OpenClaw.Tray.WinUI/Pages/ChatPage.xaml.cs)
• christineyan4: The merged chat revamp changed the main chat data provider, composer, timeline, ChatPage integration, chat window, attachments, and related tests. (role: chat feature owner; confidence: high; commits: cd4acf013e38; files: src/OpenClaw.Tray.WinUI/Chat/OpenClawChatDataProvider.cs, src/OpenClaw.Tray.WinUI/Chat/OpenClawComposer.cs, src/OpenClaw.Tray.WinUI/Chat/OpenClawChatTimeline.cs)
• TurboTheTurtle: Recent multiple-attachment work changed visible chat composition, ChatPage and ChatWindow integration, and added OpenClawChatDataProvider tests. (role: recent chat contributor; confidence: medium; commits: c5aa130dbf55; files: src/OpenClaw.Tray.WinUI/Chat/OpenClawComposer.cs, src/OpenClaw.Tray.WinUI/Chat/OpenClawChatRoot.cs, src/OpenClaw.Tray.WinUI/Pages/ChatPage.xaml.cs)
• TheAngryPit: Recent merged E2E proof work expanded the E2E fixture, MXC setup tests, and CI setup-connect shard adjacent to any broader UX coverage plan. (role: recent E2E area contributor; confidence: medium; commits: e70868d82bf0; files: tests/OpenClaw.E2ETests/E2EFactAttribute.cs, tests/OpenClaw.E2ETests/Setup/E2ESetupFixture.cs, tests/OpenClaw.E2ETests/Setup/MxcSetupAndConnectTests.cs)
• shanselman: The current main commit gates MXC E2E behavior on GitHub Actions and touches the same CI/E2E surface that broader automated UX coverage may need to use. (role: recent E2E CI contributor; confidence: medium; commits: 1c377cb64b65; files: tests/OpenClaw.E2ETests/E2EFactAttribute.cs, .github/workflows/ci.yml)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.