molecule-ai/molecule-core
52
0
Fork 2
Code Issues 184 Pull Requests 54 Actions 1 Packages Projects Releases Wiki Activity

test(e2e-chat): desktop activity-log assertion always skips on current layout #2796

New Issue
Closed
opened 2026-06-14 00:39:04 +00:00 by agent-researcher · 0 comments
agent-researcher commented 2026-06-14 00:39:04 +00:00
Member
Copy Link
Copy Source

MECHANISM: canvas/e2e/chat-desktop.spec.ts:120-138 contains an E2E assertion named activity log appears during send, but it first checks for [data-testid='activity-log'] and calls test.skip(true, "activity-log not part of this layout") when absent. Current desktop chat surfaces use ChatTab / AgentCommsPanel and repo-wide grep finds no producer for that data-testid, so the activity-log assertion is recorded as a skip instead of exercising send-time activity visibility.

EVIDENCE: audit on main e946bca969895763affc20f68a8f2675249af32b found the unconditional runtime skip path at canvas/e2e/chat-desktop.spec.ts:132-135; blame points to 10b7f8a99 (2026-06-04 false-green fix). Concrete skipped-log text is activity-log not part of this layout. Related grep found references in comments/tests only, not a rendered [data-testid='activity-log'] element in canvas/src/components/tabs/ChatTab.tsx or AgentCommsPanel.tsx.

RECOMMENDED FIX SHAPE: Canvas/frontend owner should either move this assertion to the surface that actually renders activity rows (for example Agent Comms/activity feed with a stable test id) or remove/replace the stale desktop-chat activity-log check with an active assertion that is expected in the current layout. Do not leave a normal-path test.skip(true) in the main E2E Chat lane; if optional layout coverage is still desired, split it into an explicitly scoped optional spec.

MECHANISM: `canvas/e2e/chat-desktop.spec.ts:120-138` contains an E2E assertion named `activity log appears during send`, but it first checks for `[data-testid='activity-log']` and calls `test.skip(true, "activity-log not part of this layout")` when absent. Current desktop chat surfaces use `ChatTab` / `AgentCommsPanel` and repo-wide grep finds no producer for that `data-testid`, so the activity-log assertion is recorded as a skip instead of exercising send-time activity visibility. EVIDENCE: audit on main `e946bca969895763affc20f68a8f2675249af32b` found the unconditional runtime skip path at `canvas/e2e/chat-desktop.spec.ts:132-135`; blame points to `10b7f8a99` (2026-06-04 false-green fix). Concrete skipped-log text is `activity-log not part of this layout`. Related grep found references in comments/tests only, not a rendered `[data-testid='activity-log']` element in `canvas/src/components/tabs/ChatTab.tsx` or `AgentCommsPanel.tsx`. RECOMMENDED FIX SHAPE: Canvas/frontend owner should either move this assertion to the surface that actually renders activity rows (for example Agent Comms/activity feed with a stable test id) or remove/replace the stale desktop-chat activity-log check with an active assertion that is expected in the current layout. Do not leave a normal-path `test.skip(true)` in the main E2E Chat lane; if optional layout coverage is still desired, split it into an explicitly scoped optional spec.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/ci
CI/CD pipeline issues
 do-not-auto-merge
Opt out of autonomous merge-queue merging
 kind/infrastructure
Infrastructure-related issues
 merge-queue
Ready for serialized Gitea merge queue
 merge-queue-hold
Temporarily hold PR in merge queue
 platform/go
Go platform test issues
 release-blocker
Blocks the staging→main promotion / a release
 release-test
security
test-label-sre
tier:high
High risk per dev-sop §SOP-6 — ceo only, 24h cooldown
 tier:low
Low risk per dev-sop §SOP-6 — engineers/managers/ceo can approve
 tier:medium
Medium risk per dev-sop §SOP-6 — managers/ceo can approve
 triage-test
test
 wip
Work in progress — do not auto-merge
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agent-dev-a agent-dev-b agent-pm agent-researcher agent-reviewer agent-reviewer-1 agent-reviewer-cr2 app-fe (Molecule AI · app-fe) app-lead (Molecule AI · app-lead) app-qa (Molecule AI · app-qa) claude-ceo-assistant claude-ci-reader claude-status-reaper core-be (Molecule AI · core-be) core-devops (Molecule AI · core-devops) core-fe (Molecule AI · core-fe) core-lead (Molecule AI · core-lead) core-offsec (Molecule AI · core-offsec) core-qa (Molecule AI · core-qa) core-security (Molecule AI · core-security) core-uiux (Molecule AI · core-uiux) cp-be (Molecule AI · cp-be) cp-lead (Molecule AI · cp-lead) cp-qa (Molecule AI · cp-qa) cp-security (Molecule AI · cp-security) cui (Zhanlin Cui) dev-lead (Molecule AI · dev-lead) devops-engineer documentation-specialist (Molecule AI · documentation-specialist) fullstack-engineer (Molecule AI · fullstack-engineer) godwin hongming hongming-ceo-delegated hongming-codex-laptop hongming-kimi-laptop hongming-pc2 infra-lead (Molecule AI · infra-lead) infra-runtime-be (Molecule AI · infra-runtime-be) infra-sre (Molecule AI · infra-sre) integration-tester (Molecule AI · integration-tester) mc-drift-bot molecule-code-reviewer plugin-dev (Molecule AI · plugin-dev) pm publish-runtime-bot pypi-publisher (Molecule AI PyPI Publisher (RFC#596)) release-manager (Molecule AI · release-manager) sdk-dev (Molecule AI · sdk-dev) sdk-lead (Molecule AI · sdk-lead) sop-drift-bot sop-tier-bot (SOP Tier-Check Bot) technical-writer (Molecule AI · technical-writer) triage-operator (Molecule AI · triage-operator)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: molecule-ai/molecule-core#2796
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?