dotnet-uno-testing

Test Uno Platform apps across WASM, Desktop, iOS, and Android with Playwright.

71|10|Updated Feb 11, 2026

Search Tags:#testing #cross-platform #playwright #wasm #appium #uno platform

Ready to run

npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-uno-testing-wshaddix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dotnet-uno-testing
Source: https://github.com/wshaddix/dotnet-skills/tree/main/skills/dotnet-uno-testing
Command: npx skills add https://github.com/wshaddix/dotnet-skills --skill dotnet-uno-testing-wshaddix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive strategy and tooling for testing Uno Platform applications across their diverse runtime heads (WASM, Desktop, Mobile), ensuring consistent behavior and robust UIs.

Core Features & Use Cases

Cross-Platform Testing: Develop tests that run consistently across WASM, Desktop, iOS, and Android.
Playwright for WASM: Utilize Playwright for efficient browser automation of Uno WASM applications.
Platform-Specific Strategies: Guidance on handling UI differences and platform-specific features in tests.
Use Case: You've built a cross-platform app with Uno Platform and need to ensure the login screen functions identically on the web (WASM) and on an Android emulator. This skill helps you set up Playwright tests for WASM and provides patterns for adapting them or writing separate tests for Android.

Quick Start

Use the dotnet-uno-testing skill to write Playwright tests for your Uno Platform WASM application.

Frequently Asked Questions about dotnet-uno-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I test Uno Platform apps across WASM, iOS, and Android?▼

Cross-platform testing for Uno Platform applications involves using Playwright for WASM browser automation and Appium for mobile platforms. You maintain selector consistency using AutomationProperties.AutomationId to validate UI behavior across WASM, Desktop, iOS, and Android heads.

Can I use Playwright for Uno Platform WASM testing?▼

Yes, Playwright is specifically utilized for efficient browser automation of Uno Platform WASM applications. It allows you to validate web runtime behavior and adapt tests or write separate platform-specific tests for other heads like Android.

What is the best way to handle UI differences when testing cross-platform Uno apps?▼

The best way to handle UI differences in cross-platform Uno apps is to employ platform-specific testing strategies. You maintain cross-platform selector consistency using AutomationProperties.AutomationId while adapting tests for platform-specific features.

Do I need AutomationProperties.AutomationId for consistent cross-platform test selectors?▼

Yes, using AutomationProperties.AutomationId is the recommended strategy for achieving cross-platform selector consistency. It allows your tests to reliably locate UI elements across diverse runtime heads including WASM, Desktop, iOS, and Android.

What are the limitations of testing Uno Platform WASM vs mobile heads?▼

Testing Uno Platform WASM relies on Playwright for browser automation, while mobile heads require different strategies using Appium. Limitations arise from platform-specific features and UI differences that necessitate adapting tests or writing separate test cases for diverse deployment targets.