maui integration-tests.instructions.md

Guidance for .NET MAUI integration tests, which build and run complete MAUI projects from templates to check that parts work together. The tests use NUnit and run on Azure DevOps build machines.

In plain words
What is it for?
Use it to add, configure, run, or troubleshoot end-to-end MAUI integration tests across Windows, macOS, Android, and iOS.
Why use it?
It clarifies where platform tests run, how iOS lanes are compared, and how failed attempts are retried and logged.

Instructions file for GitHub Copilot

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/dotnet/maui/integration-tests
Clone the repo
git clone --depth 1 https://github.com/dotnet/maui

Made for: GitHub Copilot.

Per session 2,481 This file is loaded in full into every session.
When invoked 2,481 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.02481 $0.02481
Opus 5 $0.01241 $0.01241
Sonnet 5 $0.00496 $0.00496
Haiku 4.5 $0.00248 $0.00248

Measured yesterday against content hash 1428498a4e1c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

maui integration-tests.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 yesterday.

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/integration-tests.instructions.md · 253 lines

How it starts

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

.NET MAUI Integration Tests Guidelines

Integration tests validate end-to-end functionality by creating, building, and running .NET MAUI projects using templates and the local workload.

Test Framework

These integration tests use NUnit as the test framework.

CI Infrastructure

All integration tests run on Azure DevOps agents via the stage template eng/pipelines/arcade/stage-integration-tests.yml.

  • Windows tests: Run on Windows 1ES pools
  • macOS tests: Run on Azure Pipelines hosted images
    • General macOS tests: macOS-15 (ARM64/Apple Silicon)
    • RunOnAndroid: macOS-15 (via MacOSPool)
    • RunOniOS_*: Each iOS test runs in two separate lanes:
      • ARM64 lane (MacOSPoolArm64): macOS-15 with Apple Silicon
      • MacOSPool lane (MacOSPool): For comparison testing

Test Retry

Integration tests are configured with automatic retry on failure (retryCountOnTaskFailure: 1). If a test fails, Azure DevOps will automatically retry it once before reporting failure.

Log Preservation: Logs from each attempt are saved to separate folders (attempt-1/, attempt-2/, etc.) so that both the original run and retry logs are preserved for debugging. This uses the SYSTEM_JOBATTEMPT environment variable provided by Azure DevOps.

Individual iOS Test Lanes

iOS tests are split into individual jobs for faster debugging and parallel execution. Each test runs on both ARM64 and MacOSPool for comparison:

Test Description Timeout
RunOniOS_MauiDebug MAUI app, Debug config 45 min
RunOniOS_MauiRelease MAUI app, Release config 45 min
RunOniOS_MauiReleaseTrimFull MAUI app, Release, full trim 45 min
RunOniOS_BlazorDebug Blazor app, Debug config 45 min
RunOniOS_BlazorRelease Blazor app, Release config 45 min
RunOniOS_MauiNativeAOT MAUI app, NativeAOT 45 min

Note: RunOniOS_BlazorReleaseTrimFull is temporarily disabled due to ASP.NET Core issue #63951.

Read the full file on GitHub · 253 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. yesterday First seen · 253 lines · 2,481 tokens per session scan A 1428498a4e1c

Subscribe to this mod's changes

maui integration-tests.instructions.md is an instructions file published in the GitHub repository dotnet/maui (23,317 stars, last pushed yesterday), licensed MIT. It adds 2,481 tokens to every session, about $0.0124 per session on Opus 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.