Capybara vs Uno Platform

What Capybara is

Capybara is an MIT-licensed Ruby library and acceptance-testing DSL that simulates user interaction with web applications. It supplies finders, matchers, actions, sessions and automatic waiting while delegating actual execution to drivers such as the fast RackTest default or browser-capable Selenium. It is not itself a browser, test runner or assertion framework, and test fidelity, JavaScript support, isolation and concurrency behavior depend on the chosen driver and surrounding stack.

What Uno Platform is

Uno Platform is an Apache-2.0-licensed .NET UI framework for building applications from a shared C# and XAML or C# Markup codebase across Windows, Android, iOS, WebAssembly, macOS and Linux. Its open-source runtime is complemented by account-based Studio tooling such as Hot Reload and Hot Design. Actual target coverage depends on the development host, IDE, .NET workloads, platform SDKs and renderer, so single-codebase does not mean identical tooling or behavior everywhere.

What Capybara is built to do

Navigation and actions

Visits pages, fills fields, clicks controls, attaches files and manipulates supported browser state.

Finders and matchers

Queries accessible labels, text, CSS and XPath with configurable matching behavior.

Automatic waiting

Retries eligible queries and expectations while asynchronous content settles.

Interchangeable drivers

Routes the DSL through RackTest, Selenium or compatible external drivers with different capabilities.

What Uno Platform is built to do

Shared .NET UI

Uses C# with XAML or C# Markup to share application and interface code across targets.

WebAssembly target

Runs supported .NET UI applications in modern desktop and mobile browsers.

Skia desktop

Targets desktop environments on Windows, macOS and supported Linux configurations.

Studio tooling

Adds account-based Hot Reload and Hot Design workflows where the compatibility matrix permits.

Choose Capybara if

• Ruby application journeys expressed through user-visible behavior
• Test suites that mix fast non-JavaScript coverage with selected real-browser scenarios
• Teams prepared to manage browser drivers, test data and asynchronous behavior

Skip Capybara if

• The test stack is not Ruby-based and gains no value from a Ruby DSL
• You expect the default RackTest driver to execute JavaScript or test a remote URL
• The suite lacks a strategy for database isolation, browser dependencies and flaky-state diagnosis

Choose Uno Platform if

• C# teams extending WinUI-style skills beyond Windows
• Products whose required hosts and targets appear in the supported environment matrix
• Applications that can test and tune each platform rather than assume pixel-identical behavior

Skip Uno Platform if

• A required target or debugging workflow is unsupported from the team's development hosts
• The product depends heavily on native controls or APIs not proven through Uno abstractions
• You cannot maintain platform SDKs, .NET workloads and target-specific QA

Capybara: pros & cons

• User-oriented DSL: Tests express visits, form actions, element queries and expectations close to browser behavior.
• Automatic synchronization: Finders and matchers wait up to configured limits for asynchronous page state.
• Driver portability: The same high-level API can run against RackTest, Selenium and compatible third-party drivers.
• Framework integration: Official guidance covers use with RSpec, Minitest and other Ruby test setups.
• Default driver has no JavaScript: RackTest is fast but cannot validate client-side behavior or interact with remote applications.
• Browser tests cost more: Selenium-style drivers add browser binaries, timing variability and infrastructure overhead.
• Thread and data isolation: Transactional database strategies may not share state with a separately threaded application server.
• Ambiguous selectors can fail: Capybara intentionally raises on multiple matches unless the query is made specific.

Uno Platform: pros & cons

• Broad target matrix: One .NET solution can target Windows, Android, iOS, browsers, macOS and Linux.
• Familiar Microsoft UI model: C#, XAML and WinUI-aligned APIs reduce conceptual switching for .NET UI teams.
• Open-source core: The Uno repository is available under Apache License 2.0.
• Multiple IDE choices: Official setup paths cover Visual Studio, VS Code and JetBrains Rider.
• Host-dependent targets: iOS requires a current Mac/Xcode path, while WinAppSDK development is unavailable from macOS and Linux hosts.
• Compatibility matrix: IDE, host OS, target, .NET version and renderer combinations do not all offer the same build or debugging support.
• Upgrade work: Migration notes include removed target frameworks, tooling updates and platform-specific API changes.
• Studio boundaries: Hot Design requires sign-in, supported project versions and XAML; it excludes C# Markup and currently has target limitations.