Skip to content

AGENTS.md

Latest commit

 

History

History
46 lines (33 loc) · 2.86 KB

AGENTS.md

File metadata and controls

46 lines (33 loc) · 2.86 KB

AGENTS.md

Project: DotPilot.UITests Stack: .NET 10, NUnit, Uno.UITest, browser-driven UI tests

Purpose

  • This project owns browser-driven UI coverage for DotPilot through the Uno.UITest harness.
  • It is intended for app-launch and visible-flow verification once the external test prerequisites are satisfied.

Entry Points

  • DotPilot.UITests.csproj
  • Harness/Constants.cs
  • Harness/TestBase.cs
  • ChatSessions/Flows/GivenChatSessionsShell.cs

Boundaries

  • Keep this project focused on end-to-end browser verification only.
  • Do not add app business logic or test-only production hooks here unless they are required for stable automation.
  • Treat browser-driver setup and app-launch prerequisites as part of the harness, not as assumptions inside individual tests.
  • The harness must make dotnet test DotPilot.UITests/DotPilot.UITests.csproj runnable without manual driver-path export and must fail loudly instead of silently skipping coverage.
  • Keep the harness direct and minimal; prefer the smallest deterministic setup needed to run the suite and return a real result.
  • Keep the file layout explicit: browser harness code belongs under Harness/, harness self-tests under Harness/Tests/, end-to-end slice coverage under <Slice>/, and cross-slice operator flows under Journeys/.
  • Use the official Uno MCP documentation as the source of truth for Uno.UITest browser behavior, and align selectors with the documented WebAssembly automation mapping before changing the harness.
  • Do not manually launch the app or a standalone browserwasm host while working on this project; browser-path reproduction and debugging must go through dotnet test and the real DotPilot.UITests harness only.
  • UI tests must cover each feature's interactive elements, expected behaviors, and full operator flows instead of only a top-level smoke path.
  • Agent UI coverage is mandatory: keep end-to-end tests for prompt-first agent creation, default-agent visibility, provider readiness or enable/disable interactions, and starting or resuming a chat with an agent.

Local Commands

  • test-ui: dotnet test DotPilot.UITests/DotPilot.UITests.csproj
  • test-ui-live: dotnet test DotPilot.UITests/DotPilot.UITests.csproj

Applicable Skills

  • mcaf-dotnet
  • mcaf-testing
  • mcaf-ui-ux

Local Risks Or Protected Areas

  • The harness targets a browser flow and auto-starts the net10.0-browserwasm head on a loopback URI resolved by the harness; any driver discovery or bootstrap logic must stay deterministic across local and agent environments.
  • Harness/Constants.cs and Harness/TestBase.cs define environment assumptions for every UI test; update them carefully and only when the automation target actually changes.
  • Every new UI capability should arrive with assertions for the visible controls it adds and at least one complete end-to-end flow through the affected surface.