Cover Workplace conversations, tasks, and notifications

[gbaudrit]

Technical category

Testing

Area

Workplace

Problem

The Workplace host is started by the Playwright fixture, but PR #170 does not exercise its home/dashboard, Entry start, conversation, task, task details, notification, responsive navigation, or real-time update paths.

Impact

The end-user application can regress independently from the Console and API. Without browser journeys, a release may successfully configure resources but fail at the point where users submit and follow work. This is a core outcome with manual/API workarounds, so priority P2 applies.

Expected outcome

Reusable Workplace page objects and journeys validate Entry discovery and submission, conversation continuity, deterministic streaming output, task progress/details, notifications, recent conversations, and responsive navigation against isolated local hosts.

Scope

• Workplace root, Workspace home, dashboard aliases, conversation routes, Entry start, task list/details, and notifications.
• Prompt and form Entry presentation variants supported by current UI.
• Deterministic interaction submission and observable completion.
• SignalR-driven progress/update behavior where exposed.
• Recent conversation navigation, locale/theme behavior, and desktop/mobile layouts.
• Explicit Console fixture preparation for required Workspace, Flow, Entry, and deterministic agents.

Out of scope

Live LLM quality, voice capture, large file upload stress, multi-browser matrix beyond the configured browser, and unsupported mobile-native clients.

Dependencies

• Parent: Provide reusable Playwright journeys for UX tests and communication captures #283.
• Initial reusable automation: PR feat(testing): add reusable Playwright browser journeys #170.
• Executable Playwright coverage catalog.
• Flow authoring/execution fixtures required for complete scenarios.

Implementation guidance

Separate Console preparation fixtures from Workplace user journeys. Playwright may prepare, validate, and reset deterministic state; communication recording remains a distinct consumer of the same checkpoints.

Alternatives considered

Console-only Entry publication tests were rejected because they do not validate the independent Workplace host, SignalR updates, end-user routing, or responsive experience.

Acceptance criteria

• Every current Workplace route and alias has deterministic rendering coverage.
• Prompt and form Entry submissions complete through the browser against deterministic AI.
• Conversation, task, task-detail, and notification transitions are asserted through observable states.
• Recent conversation navigation and Workspace routing are covered.
• Representative desktop and mobile viewports pass.
• Journeys and checkpoints are reusable by external capture without duplicated selectors.

Tests and validation

Run TypeScript compilation, affected Workplace Playwright suites, full browser smoke, relevant Workplace/.NET tests, full .NET validation, documentation build, and desktop/mobile executable smoke.

Additional context

This is a squashable child increment targeting the Playwright coverage integration branch.

Attachments

None.

Preliminary checks

• I searched for an existing issue covering this work.