Files
copilotkit__copilotkit/showcase/integrations/langgraph-python/tests/e2e/hitl-in-chat.spec.ts
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

153 lines
6.2 KiB
TypeScript

import { test, expect } from "@playwright/test";
test.describe("HITL in chat — booking flow", () => {
test.beforeEach(async ({ page }) => {
await page.goto("/demos/hitl-in-chat");
});
test("page loads with chat input", async ({ page }) => {
await expect(page.getByPlaceholder("Type a message")).toBeVisible();
});
// Regression: the broad `userMessage: "Alice"` fixture in
// showcase/aimock/feature-parity.json was intercepting this suggestion and
// returning a generic "Nice to meet you, Alice! ... Tokyo" greeting, so the
// book_call HITL flow never fired. The fixture pair added in the same PR
// as this test (full-sentence userMessage match, ordered before the broad
// Alice match) routes the suggestion to a `book_call` toolCall, which is
// what makes the time-picker card render.
test("'Schedule a 1:1 with Alice' suggestion renders the time-picker", async ({
page,
}) => {
const input = page.getByPlaceholder("Type a message");
await input.fill("Schedule a 1:1 with Alice next week to review Q2 goals.");
await input.press("Enter");
const card = page.locator('[data-testid="time-picker-card"]');
await expect(card).toBeVisible({ timeout: 60000 });
// The Tokyo greeting starts with "Nice to meet you, Alice" — if any
// assistant message contains that, the broad Alice fixture won and the
// fix has regressed.
await expect(page.getByText(/Nice to meet you, Alice/i)).toHaveCount(0);
// The card should advertise the booking and the attendee parsed by the
// fixture's toolCall arguments.
await expect(card.getByText(/With Alice/i)).toBeVisible();
// At least one selectable time slot is present.
const slots = page.locator('[data-testid="time-picker-slot"]');
expect(await slots.count()).toBeGreaterThan(0);
});
test("picking a time slot resolves the HITL with a confirmation", async ({
page,
}) => {
const input = page.getByPlaceholder("Type a message");
await input.fill("Schedule a 1:1 with Alice next week to review Q2 goals.");
await input.press("Enter");
const slot = page.locator('[data-testid="time-picker-slot"]').first();
await expect(slot).toBeVisible({ timeout: 60000 });
await slot.click();
// The picked-state card replaces the slot grid.
await expect(
page.locator('[data-testid="time-picker-picked"]'),
).toBeVisible({ timeout: 10000 });
// Agent's follow-up confirmation arrives next.
await expect(
page
.locator('[data-testid="copilot-assistant-message"]')
.filter({ hasText: /Booked.*Alice/i })
.first(),
).toBeVisible({ timeout: 30000 });
});
// The other suggestion in the demo. Same HITL flow, different
// attendee/topic. Pinned here so a missing/regressed aimock fixture for
// this suggestion (or a wiring regression in this integration's
// useHumanInTheLoop binding) fails CI loudly instead of silently falling
// through to "the agent rambled at me with no toolCall."
test("'Book a call with sales' suggestion runs the HITL flow end-to-end", async ({
page,
}) => {
const input = page.getByPlaceholder("Type a message");
await input.fill(
"Please book an intro call with the sales team to discuss pricing.",
);
await input.press("Enter");
const card = page.locator('[data-testid="time-picker-card"]');
await expect(card).toBeVisible({ timeout: 60000 });
await expect(card.getByText(/Sales team/i)).toBeVisible();
const slot = page.locator('[data-testid="time-picker-slot"]').first();
await slot.click();
await expect(
page.locator('[data-testid="time-picker-picked"]'),
).toBeVisible({ timeout: 10000 });
await expect(
page
.locator('[data-testid="copilot-assistant-message"]')
.filter({ hasText: /Booked.*sales team/i })
.first(),
).toBeVisible({ timeout: 30000 });
});
// Regression: the second booking flow in a single chat session used to
// skip the picker entirely and jump straight to "Booked ..." text. Cause
// was the aimock confirmation fixture being keyed on `hasToolResult: true`
// — once the first flow finished, the conversation had a tool message in
// history, so on the second user message the confirmation fixture matched
// before the toolCall fixture (which required `hasToolResult: false`) had
// a chance to fire. Fix re-keyed confirmation fixtures on `toolCallId`
// (matches only when the LAST message is a tool result with that id) and
// dropped the `hasToolResult: false` constraint on the toolCall fixtures.
// This test explicitly walks both flows in one page session — if the
// multi-flow regression returns, the second time-picker never renders and
// this test fails at step 2.
test("both suggestions render the picker when run back-to-back without refresh", async ({
page,
}) => {
const input = page.getByPlaceholder("Type a message");
const card = page.locator('[data-testid="time-picker-card"]');
// Flow 1: Alice
await input.fill("Schedule a 1:1 with Alice next week to review Q2 goals.");
await input.press("Enter");
await expect(card.first()).toBeVisible({ timeout: 60000 });
await page.locator('[data-testid="time-picker-slot"]').first().click();
await expect(
page
.locator('[data-testid="copilot-assistant-message"]')
.filter({ hasText: /Booked.*Alice/i })
.first(),
).toBeVisible({ timeout: 30000 });
// Flow 2: sales — same page, no refresh.
await input.fill(
"Please book an intro call with the sales team to discuss pricing.",
);
await input.press("Enter");
// A SECOND picker card must appear. If the regression returns, no new
// card renders and the agent jumps straight to confirmation text.
await expect(card).toHaveCount(2, { timeout: 60000 });
await expect(card.last().getByText(/Sales team/i)).toBeVisible();
// Pick a slot in the new card and verify the sales-specific
// confirmation arrives.
await page.locator('[data-testid="time-picker-slot"]').last().click();
await expect(
page
.locator('[data-testid="copilot-assistant-message"]')
.filter({ hasText: /Booked.*sales team/i })
.first(),
).toBeVisible({ timeout: 30000 });
});
});