gpui-test

gpui-test is a command for Claude Code from geoffjay/claude-plugins. It costs 20 tokens per session (2,691 once invoked), scanned A, original, MIT.

A test generator for GPUI components, which are the parts of a GPUI user interface. It creates tests for component logic, application state, and user interactions.

In plain words
What is it for?
Use it with a component file to generate unit and integration tests for views, models, state management, rendering-related logic, and user actions.
Why use it?
It removes the need to design every test from scratch after writing a component. It also helps check that initialization, state changes, event handlers, and interactions behave as intended.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: positional $N argument.

Good fit Use it with a component file to generate unit and integration tests for views, models, state management, rendering-related logic, and user actions.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/geoffjay/claude-plugins/gpui-test
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/geoffjay/claude-plugins

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for gpui-test

README.md
[![agentmods](https://agentmods.dev/badge/commands/geoffjay/claude-plugins/gpui-test/github.svg)](https://agentmods.dev/commands/geoffjay/claude-plugins/gpui-test)
Your own site
<a href="https://agentmods.dev/commands/geoffjay/claude-plugins/gpui-test"><img src="https://agentmods.dev/badge/commands/geoffjay/claude-plugins/gpui-test/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for gpui-test

Your own site · 80×15
<a href="https://agentmods.dev/commands/geoffjay/claude-plugins/gpui-test"><img src="https://agentmods.dev/badge/commands/geoffjay/claude-plugins/gpui-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,691 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.02691
Opus 5.5 $0.00008 $0.01076
Sonnet 5.5 $0.00004 $0.00538
Haiku 4.5 $0.00002 $0.00269

Measured 1mo ago against content hash 8d45d4043426, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gpui-test scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/rust-gpui-developer/commands/gpui-test.md · 492 lines

How it starts

The opening of the file, as written. The whole thing — 492 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GPUI Test Generation

Generate comprehensive tests for GPUI components including unit tests, integration tests, state management tests, and user interaction tests.

Arguments

  • $1: Component path (required) - Path to the component file to generate tests for

Workflow

1. Analyze Component Structure

  • Read the component file
  • Identify component type (View, Model, Element)
  • Extract component struct and fields
  • Identify render method and UI structure
  • Find state management patterns
  • Locate event handlers and actions
  • Identify dependencies and injected services

2. Generate Unit Tests

Create unit tests for component logic:

Component Initialization Tests
#[cfg(test)]
mod tests {
    use super::*;
    use gpui::*;

    #[gpui::test]
    fn test_component_initialization() {
        App::test(|cx| {
            let state = cx.new_model(|_| AppState::default());
            let view = cx.new_view(|cx| MyComponent::new(state.clone(), cx));

            assert!(view.is_some());
        });
    }

    #[gpui::test]
    fn test_initial_state() {
        App::test(|cx| {
            let state = cx.new_model(|_| AppState {
                count: 0,
                items: vec![],
            });
            let view = cx.new_view(|cx| MyComponent::new(state.clone(), cx));

            view.update(cx, |view, cx| {
                let state = view.state.read(cx);
                assert_eq!(state.count, 0);
                assert_eq!(state.items.len(), 0);
            });
        });
    }
}
State Management Tests
#[gpui::test]
fn test_state_updates() {
    App::test(|cx| {
        let state = cx.new_model(|_| AppState { count: 0 });
        let view = cx.new_view(|cx| Counter::new(state.clone(), cx));

        // Update state
        state.update(cx, |state, cx| {
            state.count = 5;
            cx.notify();
        });

        // Verify view reflects change
        view.update(cx, |view, cx| {
            let state = view.state.read(cx);
            assert_eq!(state.count, 5);
        });
    });
}

#[gpui::test]
fn test_subscription_updates() {
    App::test(|cx| {
        let state = cx.new_model(|_| AppState { count: 0 });
        let view = cx.new_view(|cx| Counter::new(state.clone(), cx));

        let initial_render_count = view.render_count();

        // Update should trigger rerender via subscription
        state.update(cx, |state, cx| {
            state.count += 1;
            cx.notify();
        });

        assert_eq!(view.render_count(), initial_render_count + 1);
    });
}

Read the full file on GitHub · 492 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 492 lines · 20 tokens per session scan A 8d45d4043426

Subscribe to this mod's changes

gpui-test is a command published in the GitHub repository geoffjay/claude-plugins (8 stars, last pushed 11mo ago), licensed MIT. It adds 20 tokens to every session and 2,691 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.