maui: Instructions file for GitHub Copilot

.github/instructions/uitests.instructions.md

maui uitests.instructions.md is an instructions file for GitHub Copilot from dotnet/maui. It costs 7,402 tokens per session, scanned A, original, MIT.

A set of guidelines for writing automated UI tests for .NET MAUI, Microsoft's framework for building apps for mobile and desktop platforms.

In plain words
What is it for?
Use it when adding UI tests for features or reported issues, including tests that run on iOS, Android, Windows, or MacCatalyst.
Why use it?
It prevents incomplete tests by requiring both a test page in the sample app and a separate NUnit test implementation, with platform coverage considered.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file. Also seen: positional $N argument.

This is dotnet/maui's own configuration. It tells GitHub Copilot how to work on maui itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything maui configures →

About the project

.NET MAUI is a C# and XAML framework for building native mobile and desktop applications from one shared codebase. Developers use it to create apps for Android, iOS, iPadOS, macOS, and Windows. The catalogue entries provide skills, instructions, and agents for working with .NET MAUI.

dotnet/maui · 23,322 stars · on GitHub · dot.net

Reuse

Borrowing it

Nothing to install: this file belongs to dotnet/maui. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dotnet/maui/main/.github/instructions/uitests.instructions.md
Clone the repo
git clone --depth 1 https://github.com/dotnet/maui

Made for: GitHub Copilot.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for maui uitests.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/dotnet/maui/uitests/github.svg)](https://agentmods.dev/instructions/dotnet/maui/uitests)
Your own site
<a href="https://agentmods.dev/instructions/dotnet/maui/uitests"><img src="https://agentmods.dev/badge/instructions/dotnet/maui/uitests/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for maui uitests.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/dotnet/maui/uitests"><img src="https://agentmods.dev/badge/instructions/dotnet/maui/uitests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7,402 This file is loaded in full into every session.
When invoked 7,402 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.07402 $0.07402
Opus 5.5 $0.02961 $0.02961
Sonnet 5.5 $0.01480 $0.01480
Haiku 4.5 $0.00740 $0.00740

Measured 3d ago against content hash 9e37e7fba2c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

maui uitests.instructions.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/instructions/uitests.instructions.md · 782 lines

How it starts

The opening of the file, as written. The whole thing — 782 lines — stays where its author put it; the contents beside it link to each section on GitHub.

UI Testing Guidelines for .NET MAUI

Overview

This document provides specific guidance for GitHub Copilot when writing UI tests for the .NET MAUI repository.

Critical Principle: UI tests should run on all applicable platforms (iOS, Android, Windows, MacCatalyst) by default unless there is a specific technical limitation.

UI Test Structure

Two-Project Requirement

CRITICAL: Every UI test requires code in TWO separate projects:

  1. HostApp UI Test Page (src/Controls/tests/TestCases.HostApp/Issues/)

    • Create the actual UI page that demonstrates the feature or reproduces the issue
    • Prefer C# only (.cs file) unless testing XAML-specific features (bindings, templates, styles)
    • Add AutomationId attributes on interactive controls for test automation
    • Follow naming convention: IssueXXXXX.cs (C# only) or IssueXXXXX.xaml + IssueXXXXX.xaml.cs (when XAML required)
    • XXXXX should correspond to a GitHub issue number when applicable
    • Ensure the UI provides clear visual feedback for the behavior being tested
    • Class must include [Issue()] attribute with tracker, number, description, and platform
  2. NUnit Test Implementation (src/Controls/tests/TestCases.Shared.Tests/Tests/Issues/)

    • Create corresponding Appium-based NUnit tests that inherit from _IssuesUITest
    • Use the AutomationId values to locate and interact with UI elements
    • Follow naming convention: IssueXXXXX.cs (matches the HostApp page file)
    • Include one functional [Category(UITestCategories.XYZ)] attribute per test
    • CollectionView tests use [ShardedTestCategory(UITestCategories.CollectionView, shard: N)], which exposes both the CollectionView umbrella and one numbered CI shard category
    • Shell tests use [ShardedTestCategory(UITestCategories.Shell, shard: N)]; CI uses Shell1 and Shell2 on Android, iOS, Windows, and MacCatalyst, while local umbrella runs continue to use Shell
    • Omitted shard defaults to shard 1 so a new test cannot silently cease running; the rebalancing skill assigns the durable shard
    • Put ShardedTestCategory on each test method; never put it on the class
    • A fixture split across shards must initialize every shard in FixtureSetup; never use an Order(1) test as setup for later tests
    • Dedicated stages using testConfigurationArgs (for example ios_ui_tests_mono_cv1) are separate configuration coverage and are not ordinary category-matrix shard entries
    • Test should validate expected behavior through UI interactions and assertions

Read the full file on GitHub · 782 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago Changed · +1 lines · +55 tokens per session 9e37e7fba2c6
  2. 1mo ago Changed · +5 lines · +175 tokens per session f399e4e5f936
  3. 1mo ago First seen · 776 lines · 7,172 tokens per session scan A 957d718449fb

Subscribe to this mod's changes

maui uitests.instructions.md is an instructions file published in the GitHub repository dotnet/maui (23,322 stars, last pushed today), licensed MIT. It adds 7,402 tokens to every session, about $0.0296 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,581 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens