skills/copilotkit__copilotkit
1
0
Fork 0
mirror of https://github.com/CopilotKit/CopilotKit.git synced 2026-09-14 16:26:20 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
codex/fac-202-shared-state-rendering
copilotkit__copilotkit/showcase/integrations/langgraph-python/qa/chat-slots.md
T
Tyler Slaton 59eb245a1c fix(showcase/langgraph-python): align e2e specs + QAs with current demos 
The specs and QA markdowns had drifted from the demos they describe.
This commit brings every test contract into line with the actual demo
source — eliminating false-greens, false-fails, and stale assertions.

False-fail spec assertions (would fail every run):
- `agentic-chat.spec.ts` — rewrote from the old `change_background` /
  `weather-card` / `useAgentContext` flow that no longer exists. New
  spec exercises the vanilla `<CopilotChat>` + three suggestion pills
  contract the simplified demo actually exposes.
- `gen-ui-tool-based.spec.ts` — asserted on UI text ("Use the sidebar
  to generate charts", "Chart Generator") that doesn't exist; switched
  to suggestion-pill assertions and scoped the SVG check to inside the
  assistant-message bubble (was matching CopilotChat's send-button
  SVG).
- `agent-config.spec.ts` — asserted heading "Agent Config Object" but
  the demo has "Agent Config".
- `multimodal.spec.ts` — asserted a non-existent "Multimodal
  attachments" heading; switched to the `multimodal-demo-root` testid.
- `chat-slots.spec.ts` — asserted `[data-testid="custom-assistant-
  message"]` and the bare text "slot" — neither exists. The actual
  signal is `data-slot-label="MessageView.AssistantMessage"` from the
  SlotMarker wrapper.
- `reasoning-default.spec.ts` — asserted `[data-testid="copilot-
  reasoning-message"]` and `[data-message-role="reasoning"]`; neither
  is emitted by `CopilotChatReasoningMessage`. Switched to the text-
  based "Thinking…/Thought for…" header label.

False-green spec assertions (passed for the wrong reason):
- `shared-state-read.spec.ts` — was a complete false-green: asserted
  on "Sales Pipeline", "Total Pipeline", "Active Deals" but the demo
  has been a Recipe Editor for some time. Rewrote against the
  recipe-card / ingredients-container / instructions-container testids.
- 11 specs (agent-config, beautiful-chat, frontend-tools-async,
  gen-ui-tool-based, gen-ui-agent, gen-ui-interrupt, hitl-in-chat,
  hitl-in-app, multimodal, readonly-state-agent-context, voice) used
  `[data-role="assistant"]` to gate "agent responded" — but the v2
  react-core bundle never emits that attribute (it ships
  `data-testid="copilot-assistant-message"`). Mechanical sweep to the
  correct testid.
- Deleted `shared-state-write.spec.ts` (route consolidated into
  `shared-state-read-write` earlier on this branch — spec targeted a
  removed demo) and `renderer-selector.spec.ts` (asserted on a radio-
  pill UI that no longer exists; the four "Declarative UI" variants
  are now separate manifest demos).

QA drift:
- `qa/gen-ui-tool-based.md` documented a "Haiku Generator" demo with
  haiku-card / japanese-line / english-line / haiku-image testids — a
  demo that doesn't exist anywhere on this branch. Rewrote to match
  the chart-rendering demo's actual testids and pill prompts.
- `qa/chat-slots.md` referenced "Custom Slot" pill / "Welcome to the
  Slots demo" heading / "This welcome card is rendered via the
  welcomeScreen slot." body text — all of which the slot-wrappers
  refactor on this branch removed. Updated to match the
  `custom-welcome-message` sub-slot that's actually rendered. Also
  fixed max-w-4xl → max-w-5xl to match the page.
- `qa/shared-state-read.md` said default instruction is "Preheat oven
  to 350 F" but the source has "Preheat oven to 350°F (175°C)".
- `qa/agentic-chat.md` rewrote to match the simplified vanilla-chat
  demo (the previous QA documented `change_background` / `WeatherCard`
  flows that no longer exist).
- `qa/reasoning-default.md` cited `kind: "testing"` in feature-
  registry.json for the `reasoning-default` entry; the registry entry
  has no `kind` field. Rewrote without the false cross-file claim.
- Deleted 4 orphan QA files for demos that don't exist:
  `agentic-chat-reasoning.md`, `hitl.md`, `hitl-in-chat-booking.md`,
  `shared-state-write.md`.
- Renamed `qa/reasoning-default-render.md` → `qa/reasoning-default.md`
  to match the manifest cell name.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-10 15:16:42 -07:00

4.0 KiB
Raw Permalink Blame History

QA: Chat Customization (Slots) — LangGraph (Python)

Prerequisites

  • Demo is deployed and accessible at /demos/chat-slots on the dashboard host
  • Agent backend is healthy (/api/health or /api/copilotkit GET); OPENAI_API_KEY is set on Railway; LANGGRAPH_DEPLOYMENT_URL points at a LangGraph deployment exposing the neutral sample_agent graph (registered to the chat-slots agent name)
  • Note: this demo DOES include data-testid attributes on every custom slot. Use them as the primary selectors. The underlying agent is the neutral "helpful, concise assistant" (no frontend tools, no agent tools) — this demo exercises frontend slot customization only.

Test Steps

1. Basic Functionality

  • Navigate to /demos/chat-slots; verify the page renders a centered chat surface (max-width 5xl, full viewport height) within 3s
  • Verify the custom welcome screen is visible (data-testid="custom-welcome-screen"), replacing the default welcome
  • Verify the nested welcomeMessage sub-slot renders inside the welcome screen (data-testid="custom-welcome-message") with body text reading "Hover any region to see its slot path · click the badge to copy"
  • Verify the welcome card wraps the default chat input element and a suggestionView row beneath it (both passed in as props by CopilotChatView)

2. Feature-Specific Checks

Welcome Screen Slot (welcomeScreen)

  • Confirm the welcome card displays a hoverable SlotMarker badge (the gradient indigo/violet ring) — visually distinct from the default CopilotChat welcome
  • Confirm NO default CopilotChat welcome heading is rendered (the custom card fully replaces it)

Suggestions (useConfigureSuggestions)

  • Verify two suggestion pills render in the suggestionView slot beneath the input with verbatim titles:
    • "Write a sonnet"
    • "Tell me a joke"
  • Click "Tell me a joke"; verify it sends the message "Tell me a short joke." and an assistant text response appears within 10s

Disclaimer Slot (input.disclaimer) — visible after first message

  • After sending the first message, verify the custom disclaimer renders below the chat input (data-testid="custom-disclaimer") containing:
    • a small badge reading "slot" (indigo background, lowercase bold)
    • body text "Custom disclaimer injected via input.disclaimer." (the phrase input.disclaimer is in monospace)
  • Verify the default CopilotChat disclaimer text (if any) is NOT present — the custom disclaimer replaces it

Assistant Message Slot (messageView.assistantMessage)

  • After the assistant response arrives, verify the assistant message is wrapped in the custom container (data-testid="custom-assistant-message") with:
    • an indigo-tinted card background (bg-indigo-50/60 in light mode)
    • an indigo border (border-indigo-200)
    • a small absolute-positioned "slot" badge at the top-left corner (indigo-600 background, white uppercase bold text)
  • Verify the user message bubble is NOT wrapped in the custom container (user messages use the default styling)
  • Send a second prompt ("Write a one-line sonnet"); verify the second assistant response is also wrapped in the custom-assistant-message container

3. Error Handling

  • Attempt to send an empty message; verify it is a no-op (no user bubble, no network request)
  • Send a ~500-character message; verify it wraps within the max-w-5xl container without horizontal scroll or layout break; the custom assistant-message card grows to fit the response
  • Verify DevTools → Console shows no uncaught errors or missing-prop warnings during any flow above

Expected Results

  • Chat surface renders within 3 seconds with the custom welcome card visible
  • Assistant text response within 10 seconds; wrapped in the custom assistant-message slot on every turn
  • All three custom slots (welcomeScreen, input.disclaimer, messageView.assistantMessage) replace their defaults and are visually distinguishable via their "slot" badges / gradient styling
  • No UI layout breaks, no uncaught console errors
Reference in New Issue View Git Blame Copy Permalink