gpui-test

Name: gpui-test
Availability: InStock
Author: zerx-lab

Test GPUI components and async operations with #[gpui::test].

62|1|Updated Feb 5, 2026

Search Tags:#testing #ui #components #async #gpui #visual-test #cargo-test

Ready to run

npx skills add https://github.com/zerx-lab/rmx --skill gpui-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gpui-test
Source: https://github.com/zerx-lab/rmx/tree/main/.opencode/skills/gpui-test
Command: npx skills add https://github.com/zerx-lab/rmx --skill gpui-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GPUI test framework enables deterministic, repeatable validation of UI components and async operations.

Core Features & Use Cases

Deterministic unit and integration tests for GPUI components using the #[gpui::test] attribute.
Support for TestAppContext (no-window tests) and VisualTestContext (window-dependent tests) to cover both headless and UI scenarios.
Patterns for async operations, timers, and distributed testing across multiple app contexts.

Quick Start

Write a simple test using #[gpui::test] with TestAppContext and run cargo test. For example, create a test that initializes a component and asserts its initial state, then run cargo test to verify results.

Frequently Asked Questions about gpui-test

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

FAQPage Schema

How do I write deterministic tests for GPUI components and async operations?▼

You can write deterministic tests for GPUI components by using the #[gpui::test] attribute with TestAppContext for headless tests or VisualTestContext for window-dependent UI tests, then run cargo test to validate results.

What is the difference between TestAppContext and VisualTestContext in GPUI testing?▼

TestAppContext is used for headless, no-window unit tests, while VisualTestContext is designed for window-dependent visual rendering scenarios. Both enable deterministic validation of components within the GPUI test framework.

Can I run async tests with timers and multiple app contexts in GPUI?▼

Yes, the GPUI test framework supports asynchronous tests, property testing patterns, and utilities for timers, windows, and distributed testing across multiple app contexts to ensure repeatable validation.

Does the GPUI test framework support visual rendering tests for UI components?▼

Yes, the framework supports visual rendering scenarios through VisualTestContext, allowing you to perform deterministic and repeatable validation of window-dependent UI components and focused elements.

How do I get started with unit testing a GPUI component's initial state?▼

To start, write a test using the #[gpui::test] attribute with TestAppContext, initialize your component, assert its initial state, and run cargo test to verify the deterministic results.

What is the best way to validate focused components and windows in GPUI tests?▼

The best way is to use VisualTestContext within the #[gpui::test] framework, which provides specific utilities for testing windows and focused components to ensure deterministic and repeatable UI validation.