Skip to content

aalmada/Stationary / .agents/skills/dotnet-maui

dotnet-maui

Verified

Build, architect, debug, test, and publish .NET MAUI 10 cross-platform native apps for Android, iOS, Mac Catalyst, and Windows using C#, XAML, or C# markup. USE FOR: MAUI project configuration, single-project targeting, pages, layouts, controls, XAML, MVVM, data binding, CommunityToolkit.Mvvm, dependency injection, Shell navigation, handlers, platform integration, permissions, lifecycle, accessibility, localization, performance, trimming, Appium UI tests, Android/iOS/Windows publishing. DO NOT USE FOR: ASP.NET Core web UI, Blazor-only apps, Avalonia, WPF-only, Xamarin.Forms migration without MAUI target code, or generic .NET code with no MAUI UI or platform concern.

references/testing.md

View on GitHub
# Testing

## Test Layers

| Layer | Scope | Execution Environment |
| --- | --- | --- |
| Unit | View models, services, validation, mapping, cancellation, errors | .NET test runner without MAUI UI objects |
| Integration | Storage, HTTP clients, serialization, platform abstraction contracts | Controlled test host, emulator, or device as needed |
| UI | Critical user workflows, navigation, forms, accessibility labels | Appium on target-platform emulator/simulator/device |
| Release validation | Signing, permissions, lifecycle, performance, installation | Signed Release package on physical devices |

- Unit-test presentation logic through injected interfaces, fake clocks, deterministic schedulers, and cancellation tokens. Do not construct pages to test view-model behavior.
- Make UI automation selectors stable with semantic identifiers or automation IDs; do not use visible text that changes with localization as the only selector.
- Cover initial launch, offline/error paths, interrupted permission prompts, resume/background transitions, navigation reset, and accessibility-critical interactions.
- Test physical devices in addition to emulators/simulators for permissions, sensors, notifications, memory behavior, network changes, performance, and signing.

## Sources

- [Unit testing](https://learn.microsoft.com/dotnet/maui/deployment/unit-testing?view=net-maui-10.0)
- [UI testing with Appium](https://learn.microsoft.com/dotnet/maui/deployment/ui-testing?view=net-maui-10.0)
- [Deployment and testing](https://learn.microsoft.com/dotnet/maui/deployment/?view=net-maui-10.0)
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall