dotnet-ui-testing-core

Provide core patterns for .NET UI testing across Blazor, MAUI, and Uno Platform.

10|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-ui-testing-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-ui-testing-core
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/dotnet-ui-testing-core
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill dotnet-ui-testing-core

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenges of creating reliable and maintainable UI tests for .NET applications by providing core patterns and strategies for cross-framework UI testing.

Core Features & Use Cases

  • Page Object Model (POM): Encapsulates UI structure and interactions for maintainable tests.
  • Selector Strategies: Recommends reliable methods for identifying UI elements, prioritizing data-testid and accessibility attributes.
  • Async Wait Patterns: Guides on handling non-deterministic UI updates and network requests effectively.
  • Accessibility Testing: Integrates automated accessibility checks into the testing workflow.
  • Use Case: A QA engineer can use these patterns to build a robust test suite for a .NET Blazor application, ensuring UI stability and accessibility compliance across different browsers and devices.

Quick Start

Implement the page object model for your login screen by creating a LoginPage class that extends PageObjectBase and handles user login interactions.

Frequently Asked Questions about dotnet-ui-testing-core

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

FAQPage Schema
How do I build maintainable .NET UI tests using the Page Object Model?

The Page Object Model for .NET UI testing encapsulates UI structure into classes extending PageObjectBase, creating maintainable test suites. This pattern separates UI interactions from test logic, allowing reliable element location and interaction handling across Blazor and MAUI frameworks.

What selectors should I use for reliable Blazor UI testing?

Reliable .NET UI testing selectors prioritize data-testid attributes and accessibility properties. These stable selectors prevent test breakage from DOM changes, ensuring consistent element identification across Blazor, MAUI, and Uno Platform applications during automated test execution.

How do I handle asynchronous waits in .NET UI test automation?

Asynchronous wait patterns in .NET UI testing handle non-deterministic UI updates and network requests. Implementing proper async waits ensures test stability by pausing execution until elements are ready, preventing flaky tests caused by timing issues in dynamic web applications.

Can I integrate accessibility testing into my .NET UI test automation workflow?

Accessibility testing integrates directly into .NET UI test automation workflows. This approach runs automated accessibility checks alongside functional UI tests, ensuring applications meet compliance standards while validating UI stability across different browsers and devices during test execution.

Does this .NET UI testing approach work with MAUI and Uno Platform?

This .NET UI testing approach works across Blazor, MAUI, and Uno Platform frameworks. It provides core testing patterns compatible with .NET 8.0+ environments, requiring a test project scaffolded by dotnet-add-testing to establish the initial structure for cross-framework UI validation.

Why are my UI tests flaky and how do I fix non-deterministic failures?

Flaky UI tests often stem from non-deterministic UI updates and network requests. Implementing async wait patterns and stable data-testid selectors resolves these timing issues, creating reliable test execution by ensuring elements are fully loaded before interaction.