dotnet-uno-testing

Guide testing of Uno Platform apps across WASM, Desktop, and Mobile heads.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/rudironsoni/dotnet-agent-harness --skill dotnet-uno-testing-rudironsoni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-uno-testing
Source: https://github.com/rudironsoni/dotnet-agent-harness/tree/main/.rulesync/skills/dotnet-uno-testing
Command: npx skills add https://github.com/rudironsoni/dotnet-agent-harness --skill dotnet-uno-testing-rudironsoni

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the complexity of testing Uno Platform applications by providing strategies and code examples for validating functionality across various target platforms (heads) like WASM, Desktop, and Mobile.

Core Features & Use Cases

  • Cross-Platform Testing Strategies: Offers guidance on testing Uno Platform applications across different runtime heads (WASM, Desktop, iOS, Android).
  • Playwright for WASM: Provides detailed examples of setting up Playwright for UI automation of Uno WASM applications, including test infrastructure and sample tests.
  • Platform-Specific Code Testing: Demonstrates how to handle and test code that is unique to specific platforms using conditional compilation and separate test classes.
  • Runtime Head Validation: Outlines patterns for validating UI logic across different heads using shared test logic with platform-specific drivers.

Quick Start

Use the dotnet-uno-testing skill to set up Playwright for testing 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, Desktop, and Mobile heads?

Testing Uno Platform apps across multiple heads requires shared test logic combined with platform-specific drivers and conditional compilation to validate UI logic for WASM, Desktop, and Mobile runtimes. This strategy ensures consistent behavior validation across all targeted platforms.

Can I use Playwright for Uno Platform WASM UI automation?

Yes, you can use Playwright for Uno Platform WASM UI automation by setting up Playwright 1.40+ with .NET 8.0+ and Uno Platform 5.x+. The skill provides detailed infrastructure setup and sample tests for automating WASM application interfaces.

What .NET and Uno Platform versions are required for cross-platform testing?

Cross-platform testing requires .NET 8.0+ and Uno Platform 5.x+ at minimum. For WASM UI automation specifically, Playwright 1.40+ is also needed to execute the test infrastructure and validate functionality across runtime heads.

How do I test platform-specific code in an Uno Platform application?

To test platform-specific code in an Uno Platform application, use conditional compilation and separate test classes to isolate logic unique to specific runtime heads. This pattern allows targeted validation of platform-dependent functionality without breaking cross-platform tests.

What is the best way to validate Uno Platform runtime heads?

The best way to validate Uno Platform runtime heads is using shared test logic with platform-specific drivers. This pattern allows you to execute identical UI validation tests across WASM, Desktop, and Mobile environments while handling platform differences cleanly.

Does Uno Platform testing support WebAssembly UI automation?

Uno Platform testing supports WebAssembly UI automation through Playwright integration. With .NET 8.0+ and Uno Platform 5.x+, you can configure Playwright 1.40+ to automate and validate WASM application interfaces effectively.